Pascal Junod
@cryptopathe.me
800 followers 730 following 150 posts
applied cryptographer - certified nerd god - head of cryptography & research at duokey - founder modulo p - ex-Snap - co-founder ex-strong.codes - has-been professor - trail runner - aidjolat
Posts Media Videos Starter Packs
Reposted by Pascal Junod
matthewdgreen.bsky.social
This is amazing research by Nadia Heninger and her co-authors Wenyi Morty Zhang, Annie Dai, Keegan Ryan, Dave Levin and Aaron Schulman. TL;DR a huge number of satellite links over our heads are totally unencrypted. satcom.sysnet.ucsd.edu
🛰️ SATCOM Security
Research project homepage for SATCOM Security: papers, source code, and recent satellite communications vulnerabilities.
satcom.sysnet.ucsd.edu
cryptopathe.me
👀 ⬇️
campuscodi.risky.biz
Firefox 144 is out with hardened encryption for locally stored passwords

www.firefox.com/en-US/firefo...
cryptopathe.me
Looks obvious to me...
ccanonne.github.io
I... I just don't know what to do
A red button, with a label taped on it that says PLEASE DO NOT PRESS
Reposted by Pascal Junod
financialtimes.com
The UK government has issued a new order to Apple to create a backdoor into its cloud storage service, this time targeting only British users’ data on.ft.com/4nonyx0
cryptopathe.me
Everybody knows Levenshtein distance, but only @cosic.bsky.social people know Leuvenshtein distance.
Created by Wouter Leiet, COSIC - KU Leuven / Accelerated on FPGA by Belfort / Leuvenshtein Database Demo / Preprocessing / Encrypting and processing the database
Reposted by Pascal Junod
matthewdgreen.bsky.social
I’m flagging this nice book/paper on FHE schemes not necessarily because it’s correct and I endorse it, but because it looks pretty useful. arxiv.org/pdf/2503.05136
arxiv.org
Reposted by Pascal Junod
quarkslab.bsky.social
RTFM they say but if you read the manual and copy code examples from it you may inadvertently introduce vulns in your code 🙀
In April we audited the PHP code. Now we followed up with a review of the code snippets in PHP documentation and found 81 issues 👇
blog.quarkslab.com/security-rev...
Security review of PHP documentation - Quarkslab's blog
The Open Source Technology Improvement Fund, Inc., engaged with Quarkslab to perform a security audit of the code snippets in the English version of PHP documentation, focused on some specific pages.
blog.quarkslab.com
Reposted by Pascal Junod
cryptopathe.me
Stopped reading at "[...] the resulting guarantees are only asymptotic. At best, one can state that “the probability that an adversary learns something about the secret message [...] decreases rapidly with increasing key length.”" They seem stuck in the 80's. en.wikipedia.org/wiki/Concret...
Concrete security - Wikipedia
en.wikipedia.org
Reposted by Pascal Junod
cosic.bsky.social
Check out the new open letter signed by more than 450 scientists who have serious concerns on the latest (July 2025) version of the chat control proposal. csa-scientist-open-letter.org/Sep2025
csa-scientist-open-letter.org
Reposted by Pascal Junod
signal.org
Signal @signal.org · Sep 8
Until now, if you lost or broke your phone, your Signal message history was *gone,* a real challenge for everyone whose most important conversations happen in Signal. So, with careful design and development, we’re rolling out opt-in secure backups.

signal.org/blog/introducing-secure-backups
Introducing Signal Secure Backups
In the past, if you broke or lost your phone, your Signal message history was gone. This has been a challenge for people whose most important conversations happen on Signal. Think family photos, sweet...
signal.org
cryptopathe.me
"Stefan Wolf, der Gastgeber der Runde, formuliert seine Sorge klar: Die E-ID führe zur Überidentifizierung. [...] Wolf befürchtet, dass die E-ID mit der Zeit faktisch obligatorisch würde, selbst für Alltägliches wie den Einkauf in einem Onlineshop." ⬅️ Stefan nails it, this is a very valid point.
Reposted by Pascal Junod
grapheneos.org
Swissquote has launched official support for GrapheneOS for their main app instead of it only being available for Yuh:

play.google.com/store/apps/d...

> What’s new
> - We now officially support GrapheneOS!
> - Bug fixes and minor improvements

They're verifying GrapheneOS via hardware attestation.
Swissquote - Apps on Google Play
Trade, invest and bank! Your all-in-one banking solution for smarter finances.
play.google.com
cryptopathe.me
I guess that a trained mathematician is well aware that a single sample brings only little information about a large sample space 😅
cryptopathe.me
We can agree on this point, and the security community is well aware of this fact. Yet, this is also the case for e.g., many important open-source projects that have experienced some success.
gro-tsen.bsky.social
And it misses the point, because the problem isn't just complexity, it's also the creation of a single point of failure: “Let's Encrypt” could either be taken down by a DDOS attack, or it could go out of business. And this would take down something like half of the Web.
cryptopathe.me
This claim comes out of nowhere. On my side, I genuinely don’t remember last time I hit an expired certificate. Months, if not years ago.
gro-tsen.bsky.social
… and the claim is experimentally wrong because I encounter sites that are broken ALL THE TIME. If a system breaks all the time, it's not “easy”.

And, of course, like >99.99% of all users, I just click on “shut up and let me see the site” without checking anything. So the security is exactly zero.
cryptopathe.me
No, “tremendous amount of complexity” and “absolute nightmare” is grossly over-exaggerated language. Most Linux distributions and web hosters make this experience uncomplicated.
gro-tsen.bsky.social
Finally, “it's really easy to configure an HTTPS-protected website” is both wrong and misses the point. It's wrong because it adds a tremendous amount of complexity (the Let's Encrypt renewal script is an absolute nightmare of bad documentation, incomprehensible options and dependencies); …
cryptopathe.me
Today, it's really easy to configure an HTTPS-protected website and set up automatic renewals. Sometimes it breaks, but such mishaps do not justify denigrating HTTPS or Let's Encrypt, or spreading wrong facts if we look at the benefits they bring for safeguarding our privacy and online security 😒.
cryptopathe.me
People having some minimal understanding of web and PGP security tend to not publish their private keys.
gro-tsen.bsky.social
2. The fallacy here 🔽 is that this offers a reasonable explanation why the KEY HOLDER may set an expiration date, but this is not a reason why the holder should be forced to do so.

PGP keys don't expire. You can't force security on people: they could well be publishing their secret key anyway.
cryptopathe.me
2. Certificates need to expire for many reasons: (a) Cryptographic strength of algorithms changes over time (broken ciphers, insufficient key sizes) and certificate expiration ensures that old, weak certificates are automatically phased out.
cryptopathe.me
Fair enough, they are referenced, but I meant they are ranked with very low priority if they compete with HTTPS-protected website on the same keywords.
gro-tsen.bsky.social
4. 🔽 So, first, the “search engines don't reference HTTP-only websites” is just flat-out completely wrong. Search “site:madore.org” www.google.com/search?q=sit... for proof. Search in Bing or DuckDuckGo if you want to check it's not a Google thing.
cryptopathe.me
4. People don't set up HTTP-only websites anymore because search engines are not referencing them, and because browser vendors are pushing for HTTPS.
cryptopathe.me
Reality force you to implement pragmatic solutions, which might not be perfectly adapted to any scenario or threat model.
gro-tsen.bsky.social
… And a threat model that makes sense for a banking site is completely different from a threat model for a webcomic (whose attack scenario is… uh… 🤔). The “one-size-fits-all” approach of HTTPS makes no sense because it tries to protect against Everything Everywhere All at Once.