Yeah, without the latency regression, it probably would have gone undetected much longer. Using a secondary thread and spreading the CPU load over a few seconds would have made it not even register as a spike in CPU usage.
Or do cheap ECDSA instead of expensive RSA. Even if the backdoor is hidden inside RSA decryption and the rest of the system thinks the thing being decrypted should be encrypted with RSA, you don't have to use it for the back door.
If you deleted /lib, you'd probably be better off reinstalling packages while booting off of USB or something. You're gonna have downtime because programs won't work correctly.
I also had to wonder why not just liveboot from USB or attach the affected boot medium to another system, then use the recovery system's fully working tools to just relink the /lib folders?
“This is not a very important machine, and I could have just reimaged the MicroSD card and be done with it, but I was curious if I could recover from the error.”
"E-bikes produce virtually no greenhouse emissions after manufacturing"
Except for the electricity to charge it, which could either come from clean or dirty power. True about the lack of exhaust though.
Then it leads to the question about the efficiency of generation, distribution, and battery charging vs the distribution and burning of gasoline. Also the weight of the bike. Perhaps someone else has already done the math on this.
You have to have a really really dirty energy supply for an electric vehicle to be a higher emitter than an ICE vehicle. E-bikes also will replace things like two-stroke mopeds which are especially dirty for ICE vehicles.
There was the tarpit that sends out markov-chain-generated random words, loading very slowly . If the client has a limited number of concurrent requests, that could theoretically choke the client.
Tagged files are too useful. 4 byte tag name, 4 byte length of the object, then the binary data of the object. You see these all the time. Sometimes you see the size before the tag name.
Occasionally, you also see a file header, followed by a size, and an "x", that often indicates a block of ZLIB compressed data.
It's also detecting when a file on DOS/Windows is opened in "ASCII mode" rather than binary mode. When opened in ASCII mode, "\r\n" is automatically converted to "\n" upon reading the data.
reply