korrents
Matthew Green

What Matthew Green thinks about crypto

@matthew-green · 11 positions · On ppll ↗

Cryptographer and professor at Johns Hopkins University, where he works on applied cryptography and user privacy. He writes A Few Thoughts on Cryptographic Engineering, which is where most public arguments about messaging encryption, client-side scanning and cloud backup end up being adjudicated.

Matthew Green did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter crypto · Newest first
Topic
All 11privacy 8Telegram 3crypto 2design 2the cloud 2Apple 1cybersecurity 1data centers 1government 1
2 more topics
product management 1Silicon Valley 1
Sort
NewestOldest

Only Matthew Green on crypto. See everyone on crypto

2 dated positions, 2021, in their own words. Our reading of what Matthew Green has said — not written or endorsed by them.

2 positions so far — this page is not yet offered to search engines.

  1. Our readingA tracing requirement in an encrypted messenger gives up the confidentiality of who sent what, which is the part that protects the sender.

    privacy

    Their wordsIn short: traceability can really screw with the “who sent what” side of content confidentiality.

    ↗Thinking about “traceability”blog.cryptographyengineering.com 1st of 3 in this piece

  3. Our readingWho sent what is not metadata, so an encrypted system that reveals it has given up more than the routing information it could never hide.

    privacy

    Their wordsInformation revealed about “who sent what” in an E2E system is not the same as metadata.

    ↗Thinking about “traceability”blog.cryptographyengineering.com 2nd of 3 in this piece