slowdoorsemillc

I figured it out, it's the CIA. Edward Snowden got no punishment for leaking despite "NSA reads minds" and yet the CIA leakers got 40 years and 8 months for not even leaking the code. The CIA has an AI that wrote several hundreds of millions of lines of software exploit code according to Vault 7. CIA and their Artifical Intelligence(s) are the deep state.

How do I block someone on HN? I hate ad-hominems. There may be a hardware backdoor in the 5th Gen Intel and Zen 1 and newer CPUs. I can tell my computer is hacked when I use anything newer than my 3rd Gen Intel that's in my 2012 Macbook Pro.

Yes, the entire file would be encrypted but with the private key after adding, say, 2048 bits of all 0's to the beginning of the file. After decrypting the whole file, check if the first 2048 bits are all 0's. If they are, good, boot. It can be brute forced, but with 1 in 2^2048 probability of guessing right.

The chain is only as strong as it's weakest link.

Current signature verification: Calculate hash of known operating system image, decrypt digital signature with public key (known because it's public) which is a hash encrypted with private key, compare calculated hash with decrypted hash, boot if equal.

That's like saying "I know the hash value and operating system image encrypted and decrypted so I can deduce the private key."

If the current signature verification algorithms aren't subject to known plaintext attacks (but are to hash collision attacks) then my algorithm isn't subject to known plaintext attacks and isn't subject to hash collisions.

The only thing hidden in current signature verification is the private key (intended for signing) and my idea for a mitigation also keeps the private key private (intended for signing.)

Heavy FBI and Police gangstalking presence in Hacker News, 4Chan, Slashdot, LinkedIn, Scaleupstream, Installgentoo Wiki, Real Life, etc. have gotten out of hand.

I love it.

I also have other repositories on GitHub, all Public Domain of course. One is my 64Bit BitBitJump Implementation, another is my cryptographic signature verification mitigation idea that throws out the hash function and uses padding at the beginning of the file and checks it after decryption to see if it's all 0s. Another is my halting problem solution.

How to block every single HNer at once?

I solved the halting problem, it doesn't exist.

Just check every n + 1 clock cycles whether the previous savestate (a term from speedrunning) matches the current savestate exactly, byte for byte. You can discard the previous previous savestate.

Now where's my million dollars for proving P=NP...