Crypto 101 – Introductory course on cryptography
61–70 of 148 posts
Re: Crypto 101 – Introductory course on cryptography
#62Can any crypto people here on HN verify that this gets it right?
Re: Crypto 101 – Introductory course on cryptography
#63Quick question, I had apparently Pinboarded this in March 2014. I see the PDF is still pre-release. Has anything changed with this, or is it kinda just coming up again because of recent political climate. I'm fine either way, just curious if this has changed drastically from what I had looked at previously.
I should stop calling it a pre-release. There's no useful "done" marker. It includes most of the material I wanted to talk about, and has for a while. You should update the PDF though; as the other commenter mentioned, it does get updated :)
Re: Crypto 101 – Introductory course on cryptography
#64Stop trying to make "streets ahead" a thing...
Re: Crypto 101 – Introductory course on cryptography
#65Suggestion: Add some notification medium for when the book is ready.
Agreed. The one time I actually want to sign up to a mailing list, and there's no way of doing it.
I should really remove that pre-release stuff. There's no useful point for "done", and it already includes most of the stuff I wanted to talk about.
Re: Crypto 101 – Introductory course on cryptography
#66Stop trying to make "streets ahead" a thing...
Re: Crypto 101 – Introductory course on cryptography
#67Re: Crypto 101 – Introductory course on cryptography
#68Re: Crypto 101 – Introductory course on cryptography
#69Earlier quoted context omitted.
Of course; my point is (and I assume that's also the point of other people who assert similar stances on the topic) that the average programmer or software engineer should leave these things to recognized cryptographers. This also highlights a peculiarity with cryptography, in that it is very hard to understand for laymen (assuming laymen are ppl with some CS or math education), so most arguments in discussions of la…
> Of course; my point is (and I assume that's also the point of other people who assert similar stances on the topic) that the average programmer or software engineer should leave these things to recognized cryptographers. If "crypto is for cryptographers" is your stance I think you're doing yourself a disservice. Understanding crypto, as in learning the foundations of it, is important for everyone. Having a good gra…
Also, if you're ever interested in something.. find a protocol in a language, and try to refactor it, but first create a bunch of test cases, and make SURE to include unicode characters, etc in any strings you're testing, high byte characters are often missed as a use case, and it gets weird.
Getting multiple systems in multiple languages talking can sometimes be frustrating to say the least.