Agreed, it struck me as unique that the author says anything about women. I have seen dozens (if not hundreds) of programming tutorials and that was the first one that said anything about genders. The problem is somewhere else.
As everyone said, you have created a stream cipher. But I feel that I have to add that your idea (OTP with small key) is usually implemented this way: the small key is a counter used an input to some PRNG specifically designed for this (you should try AES in CTR mode), which you increment every time.
This produces a sequence which is always the same for each session, but because the keyspace is so large (2^128 with AES-128), this is acceptable because these PRNGs are actually cryptographically secure hash functions, which makes them very hard to reverse. Therefore, the only efficient way to crack your session is to either catch the key (your counter) or to brute force it by using every value of the counter and test whether this leads to a successful decryption. Not only are there 2^n possibilities, but every possibility is extremely expensive to test and then you have to accurately check whether the decrypted values are coherent (this is difficult with packets with a fixed header and nearly impossible with raw binary data).
The big disadvantage is having to store your small key until decryption.
If a cryptographic algorithm is fundamentally secure, a small (128 - 256 byte) key will be all it needs to be secure. If an algorithm can't be secure with a key that size, giving it a bigger key is likely to only make it marginally better.
He meant free (as in freedom), not open. "Proof" of that is in the submission's article. It's not exactly a formal proof but it has convinced most people here.
Unfortunately, this highlights some weaknesses in the GPLv2, which is supposed to guarantee freedom.
Problem is, the prompt doesn't appear until the encryption has ended, the key has been sent to the servers (it's kind of complicated, it apparently tries to find servers on its own, I wonder if it can be fooled) and that key has been locally destroyed.
So, by the time the user is notified that there is malware on their PC, it's too late. People who know to detect viruses while they're running don't run attachments in the first place.
According to the KernelMode thread¹ the keypair is generated on the server. The public key is retrieved from it, but its private counterpart will never be on your machine. No key is sent to the server.
I share that opinion so I'll answer. IMO, China letting control over currency just slip away is as realistic as China letting control over anything slip away. AFAIK it's still an authoritarian state. It could happen (it has a relatively free economy after all) but it's not consistent with China.
> Surely they don't see themselves as an authoritarian control-monger.
Why do you believe this? There's a very long chinese tradition of vesting control in the social hierarchy. "Authoritarian control-monger" may be dirty language in the US, but not everywhere.
He said "They should have made IPv6 mandatory", as in, it cannot use IPv4. Obviously, "when connecting to the Internet is required" is implied, and having an always online console is irrelevant to his point.
Don't talk shit on Android. It is FOSS, therefore it respects your 4 freedoms, unlike iOS, which you cited.
Agreed on Chrome OS. I'll stay with my cheap old Linux Thinkpad. My remote services run on my server at home anyway and they're pretty close to what Google offers, minus the sleek look (who cares, I'm functional).
"Don't talk shit on Android. It is FOSS" - is it? did you ever commit code to it? did anyone outside of google and other corp ever committed code to it?
