Re:Backdoor in upstream xz/liblzma leading to SSH server com...
by davexunit on Friday March 29, 2024 @01:57PM
(#39867042)
JiaT75 also has commits in wasmtime according to https://hachyderm.io/@joeyh/112180082372196735
[ Parent
| on HN ]
Re:Backdoor in upstream xz/liblzma leading to SSH server com...
by mintplant on Friday March 29, 2024 @02:19PM
(#39867283)
Just a documentation change, fortunately:
https://github.com/bytecodealliance/wasmtime/commits?author=...
They've submitted little documentation tweaks to other projects, too; for example:
https://learn.microsoft.com/en-us/cpp/overview/whats-new-cpp...
I don't know whether this is a formerly-legitimate open source contributor who went rogue, or a deep-cover persona spreading innocuous-looking documentation changes around to other projects as a smokescreen.
Re:Backdoor in upstream xz/liblzma leading to SSH server com...
by bombcar on Friday March 29, 2024 @04:25PM
(#39868617)
Minor documentation change PRs is a well known tactic used to make your GitHub profile look better (especially to potential employers).
He could be doing the same thing for other reasons; nobody really digs into anything very deep so I could see someone handing over co-maintenance to a project based on a decent looking Github graph and some reasonability.
Re:Backdoor in upstream xz/liblzma leading to SSH server com...
by mysidia on Friday March 29, 2024 @05:17PM
(#39869116)
Consider the possibility those type of submissions were part of the adversary's strategy in order to make their account appear more legitimate rather than appearing out of nowhere wanting to become the maintainer of some project.
Re:Backdoor in upstream xz/liblzma leading to SSH server com...
by pinko on Friday March 29, 2024 @02:15PM
(#39867238)
per https://hachyderm.io/@bjorn3/112180226784517099, "The only contribution by them to Wasmtime is a doc change. No actual code or binary blobs have been changed by them."