|
|
Log in / Subscribe / Register

The TAB report on the UMN affair

The TAB report on the UMN affair

Posted May 6, 2021 9:24 UTC (Thu) by dottedmag (subscriber, #18590)
In reply to: The TAB report on the UMN affair by dvrabel
Parent article: The TAB report on the UMN affair

No kidding?

If I find a suspicious set of commits submitted into a project I work on, then “raising possible incidents with the TAB” will be the last thing on my mind. First ones:

- Immediately revert everything suspicious, even by association, until cleared;
- Notify anyone you can who might have used the code that it may contain backdoors.

The first and only priority of any project is its users, not a committee somewhere. Risking users’ security for the sake of appeasing some bureaucrats from universities is not.


to post comments

The TAB report on the UMN affair

Posted May 6, 2021 11:08 UTC (Thu) by Homer512 (subscriber, #85295) [Link] (2 responses)

What exactly are you referring to? Banning further patches and reviewing all old ones so that they may be reverted was Greg's first reaction. But you can't just blindly revert 400 patches made since 2018.

The TAB report on the UMN affair

Posted May 6, 2021 11:21 UTC (Thu) by dottedmag (subscriber, #18590) [Link] (1 responses)

Well, yes, you can. That's prudent at the signs of foul play.

The TAB report on the UMN affair

Posted May 6, 2021 13:28 UTC (Thu) by gspr (subscriber, #91542) [Link]

Certainly not blindly. It may require a lot of work.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds