An Intensive Introduction to Cryptography
intensecrypto.org
An Intensive Introduction to Cryptography
1–10 of 37 posts
Re: An Intensive Introduction to Cryptography
#2On the other side of the spectrum, The Manga Guide to Cryptography came out recently, if that's more your style: https://nostarch.com/mangacrypto
Re: An Intensive Introduction to Cryptography
#3What is a typical path for those who want to follow this as a career? Is it mostly PhDs in academia? Or governments? Or industries? How do they fall as a distribution?
Re: An Intensive Introduction to Cryptography
#4On the other side of the spectrum, The Manga Guide to Cryptography came out recently, if that's more your style: https://nostarch.com/mangacrypto
Somehow I have zero surprise that it comes from Japanese researchers.
I suppose authors provide contents and the publisher hire illustrators to draw?
Re: An Intensive Introduction to Cryptography
#5What is a typical path for those who want to follow this as a career? Is it mostly PhDs in academia? Or governments? Or industries? How do they fall as a distribution?
I worked on the Windows crypto team for a few years. Learned a ton about this area. Most of the work, however, is plumbing. Only a tiny fraction of crypto work is actually on algorithms and that’s mostly performance related.
Re: An Intensive Introduction to Cryptography
#6On the other side of the spectrum, The Manga Guide to Cryptography came out recently, if that's more your style: https://nostarch.com/mangacrypto
The Manga Guide series has been surprisingly good in general. Not the most in depth stuff but generally quality intro texts.
Unfortunately from the preview the typesetting of the English translation in the new crypto book looks awful. Hopefully the actual content is still of good quality.
Re: An Intensive Introduction to Cryptography
#7What is a typical path for those who want to follow this as a career? Is it mostly PhDs in academia? Or governments? Or industries? How do they fall as a distribution?
I worked on the Windows crypto team for a few years. Learned a ton about this area. Most of the work, however, is plumbing. Only a tiny fraction of crypto work is actually on algorithms and that’s mostly performance related.
The interesting thing about Crypto performance tuning is that you really have to ensure that no logical path does a different amount/kind of work than another(i.e. no short circuiting). I used to not think much of it until I saw an RSA private key recovered via acoustic analysis of capacitor whine due to a short circuit condition in a function to multiply two large numbers.(this was using a recent release of openssl) To my knowledge no other area of programming really has this pitfall
Re: An Intensive Introduction to Cryptography
#8What is a typical path for those who want to follow this as a career? Is it mostly PhDs in academia? Or governments? Or industries? How do they fall as a distribution?
To Zion.
Re: An Intensive Introduction to Cryptography
#9What is a typical path for those who want to follow this as a career? Is it mostly PhDs in academia? Or governments? Or industries? How do they fall as a distribution?
I worked on the Windows crypto team for a few years. Learned a ton about this area. Most of the work, however, is plumbing. Only a tiny fraction of crypto work is actually on algorithms and that’s mostly performance related.
What kind of previous experience is needed for that job? Do you need to be a specialist crypto developer?
Re: An Intensive Introduction to Cryptography
#10Earlier quoted context omitted.
I worked on the Windows crypto team for a few years. Learned a ton about this area. Most of the work, however, is plumbing. Only a tiny fraction of crypto work is actually on algorithms and that’s mostly performance related.
The interesting thing about Crypto performance tuning is that you really have to ensure that no logical path does a different amount/kind of work than another(i.e. no short circuiting). I used to not think much of it until I saw an RSA private key recovered via acoustic analysis of capacitor whine due to a short circuit condition in a function to multiply two large numbers.(this was using a recent release of openssl)…
seems obvious, but just checking that they needed (acoustic) access to the machine performing a calculation with private key?