@SteveBellovin, do you have any objection to me blogging on a site named rethinking-security.org ? If you do object, I will find another name. And I will make it clear that I am not you, but that the name is an allusion to Thinking Security.

I want to talk about cases where conventional wisdom (in various circles) may need some rethinking.

@jpgoldberg Btw, the oldest chapter in the book, on authentication, was written precisely to debunk conventional wisdom. And then I was on sabbatical and my original plans fell through for various reasons, so I decided to write a new book.

@SteveBellovin, when I was at 1Password, I ran a “book club” for the security team using “Thinking Security”. I was able to fill in for details that were out of date.

The next year I did the same with @veorq’s “Serious Cryptography”.

(Hey, JP. It's an outstanding book, but my most serious recommendation for a 3rd edition is that you do RSA after EC and ECDH. Understanding why RSA works requires all the math of DH and more.) You can find my slides on those chapters at https://jpgoldberg.github.io/sec-training/ )

Security Team training material

Security team training material developed by Jeffrey Goldberg while working at 1Password

@SteveBellovin, I also had the pleasure of explaining many of the jokes and allusions to a younger generation.

For example, you mentioned the Bank of San Seriffe. This led not only to me explaining that number of digits of decimal expansion of 𝜋 I know depends of the number of bugs found in TeX, but on the dangers of using knowledge of a record locator, such as a bank account numbers, as an authentication proof.

@jpgoldberg Ah, the young. A few years ago, I was giving a tech history talk in my department and used the word "teletype". Most of the students had no idea what I was talking about…
@SteveBellovin, I hope you directed your explanation to /dev/tty
@jpgoldberg I used that and the device names as referring back. And the next time I gave the talk, I included a picture of a teletype.