Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by schelling42 on Monday June 21, 2021 @05:33AM
(#27577614)
How do you know it hasn't been done already? (with a more silent payload than ransomware) /s
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by Tabular-Iceberg on Monday June 21, 2021 @07:05AM
(#27578050)
What does the /s mean in this context?
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by Zetaphor on Monday June 21, 2021 @09:55AM
(#27579197)
/s is internet parlance to show that the message should be read in a sarcastic tone.
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by Tabular-Iceberg on Monday June 21, 2021 @10:09AM
(#27579319)
Yes, but what confused me is that as far as I can tell we really don’t know that it hasn’t been done before.
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by ghoward on Monday June 21, 2021 @09:45AM
(#27579088)
Not GP, but I think it indicates sarcasm?
Re:Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reprodu...
by Gravyness on Monday June 21, 2021 @12:19PM
(#27580677)
> I'm really surprised such an attack hasn't happened already.
If you count npm packages this happened quite a few times already. People (who don't understand security very well) seems to be migrating to python now.
I'm really surprised such an attack hasn't happened already. It seems so trivial for a determined attacker to take over an opensource project (plenty of very popular projects have just a single jaded maintainer).
The malicious compiler could inject an extra timed event into the main loop for the time the attack is scheduled to begin, but only if it's >3 hours away, which simply retrieves a URL and executes whatever is received.
Detecting this by chance is highly unlikely - because to find it, someone would have to have their clock set months ahead, be running the software for many days, and be monitoring the network.
That code is probably only a few hundred bytes, so it probably won't be noticed in any disassembly, and is only executed once, so probably won't show up in debugging sessions or cpu profiling.
It just baffles me that this hasn't been done already!