News for hackers. Stuff that matters.
Re:What we know about the xz Utils backdoor that almost infe... by gumby on Monday April 01, 2024 @08:27AM (#39893404)
> 1a. As a consequence of (1) autogenerated artifacts should always be committed.

I philosophically and fundamentally hate this suggestion, but have to agree with it. It's going to make porting harder, but is sadly a cost worth paying.

> dependencies are maintenance burden and a security risk, this needs to be weighted against the functionality they bring in

Tough call. A major library is more likely to be bug fixed and tuned than something you write (which is a good reason to use them which is what makes them attractive as an attack vector). Getting this right requires taste and experience. The comment says "depending on large libraries for small amounts of functionality [is bad but thought to be good]". What constitutes "small amount" vs large requires experience. Certainly cases of this tip my bias towards re-implement vs re-use.

Re:What we know about the xz Utils backdoor that almost infe... by Kuinox on Monday April 01, 2024 @09:14AM (#39893822)
Why would it make porting harder ?
Re:What we know about the xz Utils backdoor that almost infe... by gumby on Monday April 01, 2024 @04:56PM (#39899234)
Often the autogenerated things are dependent on the machine they are running on.
Re:What we know about the xz Utils backdoor that almost infe... by Kuinox on Monday April 01, 2024 @08:19PM (#39901006)
So a big reproducible build issue.
Re:What we know about the xz Utils backdoor that almost infe... by gumby on Tuesday April 02, 2024 @01:35AM (#39902700)
Well it really sucks if you build a system but the autogenerated file is for a different CPU.