Notices by Jeffrey Goldberg (jpgoldberg@ioc.exchange)

@skinnylatte Parse “sea lions” as “seal ions”.

@skinnylatte, I am still waiting for an aquarium to explain that sea lions are produced when seals are exposed to a strong current.

@Caution @mekkaokereke

Back in the late 90s, I literally had to explain why spam filters weren’t a violation of free speech. It seemed like a ridiculous thing to have to explain. I thought it would be obvious to everyone that their right to speak didn’t impose an obligation on others to listen.

Seeing that the same point still needs to be made today just makes me sad.

@lcamtuf, Chapter 1 defines numbers, some common mathematical notation, and a few other things that give you hope that you can read this book.

You might get through Chapter two.

By Chapter 3, you,put it on the shelve with all your other Springer textbooks.

@chartier, I haven’t read the article yet, but I wonder what the implications are for #E2EE messaging systems.

@SteveBellovin @lanodan @feld @cendyne @drwho, I agree that the issue about recorded traffic. But QC isn’t the only thing to worry about with a 30 year horizon.

I fully advocate intensive research in PQC. And QC isn’t the only reason to want to ditch crypto now harder than discreet log and factoring problems. But I feel like we are still learning things “too fast” to actually standardize.

The best argument for standardizing I’ve heard is that we are learning things so fast because we are trying to adopt standards.

@lanodan @feld @cendyne @drwho

Mostly I feel that it is too early to be standardizing PQC. The process has helped discover problems, with SIKE for example, and so is good thing. But I don’t think we are ready to codify winners.

We really do have time. Work on PQC remains well ahead of any cryptographically relevant QC.

My colleagues at 1Password have just open sourced our typeshare crate. It makes it much easier for #rust devs to create and manage FFIs and producing data types for #GoLang, #Swift, #kotlin, and #TypeScript built from the structs we need those to know about.

Blog post: https://blog.1password.com/typeshare-for-rust/

Crates.io: https://crates.io/crates/typeshare

GitHub: https://github.com/1Password/typeshare