News for hackers. Stuff that matters.

A comment on Backdoor in upstream xz/liblzma leading to SSH server compromise. Parent comment

Re:Backdoor in upstream xz/liblzma leading to SSH server com... by jwilk on Saturday March 30, 2024 @07:28AM (#39873830)
What do you mean?
[ Parent | on HN ]
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by everybackdoor on Saturday March 30, 2024 @09:32AM (#39874698)
Look at the newest commits, do you see anything suspicious:

https://git.alpinelinux.org/aports/log/main/gettext

libunistring could also be affected as that has also been pushed there

[ Parent | on HN ]
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by jwilk on Saturday March 30, 2024 @12:08PM (#39876145)
> do you see anything suspicious

No.

> libunistring could also be affected as that has also been pushed there

What do you mean by "that"?

[ Parent | on HN ]
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by whoopdedo on Saturday March 30, 2024 @10:41AM (#39875338)
Seeing so many commits that are "skip failing test" is a very strong code smell.
[ Parent | on HN ]
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by gray_-_wolf on Monday April 01, 2024 @07:40AM (#39893056)
Yes, but it is often a sad reality of trying to run projects mainly written for glibc on musl. Not many people write portable C these days.
[ Parent | on HN ]
Re:Backdoor in upstream xz/liblzma leading to SSH server com... by account42 on Tuesday April 02, 2024 @07:40AM (#39904581)
It's still the wrong way to go about things. Tests are there for a reason, meaning if they fail you should try to understand them to the point where you can fix the problem (broken test or actual bug) instead of just wantonly distabling tests until you get a green light.
[ Parent | on HN ]