Re:Be wary of one-time pads and other crypto unicorns
by diminoten on Monday March 30, 2015 @11:26AM
(#9290125)
Your need to be right has driven us so far afield from the original topic, I'm actually somewhat impressed.
I don't know what you think I wrote, but no one here at any time suggested writing a new crypto scheme.
It's 4 days later. I've made my point over and over again, and you understand it. You have even restated my point yourself, in your second paragraph.
I'm done. You agreed with me, and everything else you're trying to talk about is just you begging to be validated. I can't feed this anymore, sorry.
You appear to be annoyed that folks write take-downs on software like the one linked to by the article. This is the outrageous claim. If you feel this is not what you're saying then fine, I'm not sure we actually have an argument.
>> I would very much appreciate it if you separated "make outrageous claims" from "develop open source security software".
There's no reason not to develop OSS security software. There's every reason to put up big warnings saying you can't vouch for its security. There's every reason to ask people who know what they're talking about to take a look, and to be humble when they point out flaws, and to rework it if that's the case. There's every reason to take some of the excellent free courses.
But there's also no reason to go off-piste. Why develop this crazy new OTP scheme? There's existing crypto for exactly these use cases. Leave the devising and proving of new crypto constructs to the deeply-versed and the academics, who know how to prove this stuff (and disprove it).
It's like saying "I can't write my OSS networking project because people keep telling me not to rewrite the TCP stack without learning about TCP first". Do you need to rewrite the stack? If so, if you want to do a good job then it's going to take a hell of a lot of knowledge and training. Why not use the OS API?