#curve25519 — Public Fediverse posts

RE: https://dol.social/@dima/115969231949139332

Shoutout to Proton support - they helped me reset my Drive volume entirely.

The difference between RSA2048 and Curve25519 (ECC) on mobile is night and day. Loading is now instant, and the "thermal throttling" is gone.

Moral of the story: Modern crypto isn't just about security, it's about accessibility and efficiency.

Now my data is encrypted by my own key, and the system actually feels "functional" for the first time.

#Proton #GPG #Cryptography #ECC #Curve25519 #Infosec #TechDeepDive #Privacy #Blog #Thoughts #ProtonMail

Как я НЕ взломал ED25519

В этой статье будет описано, как один чересчур поверивший в себя программист пытался взломать один из фундаментальных алгоритмов криптографии. Эта статья признана огородить других от подобных попыток или наоборот заинтересовать новых смельчаков для подобной авантюры. Сначала я опишу суть алгоритма на простом коде, затем перечислю методы и идеи, которыми я пытался его взломать.

https://habr.com/ru/articles/939686/

#curve25519 #ed25519 #python #хакинг #криптография #эллиптические_кривые #исследования_в_ит #математика #edwards_curve #уязвимости

Oh wow. Die Release Notes von #PHP 8.4 verraten es zwar nicht, aber die OpenSSL-Library unterstützt nun endlich #Curve25519 EC-Verschlüsselung.

Gibt es eine leicht erfassbare und verständliche Übersicht, welche Kryptoalgorithmen, Schlüssellängen, etc. nach dem #StandDerTechnik verwenden sollte? Ich stelle mir da eine Liste vor, die ich einem Admin in die Hand drücken kann und er macht nix falsch.

Das @bsi erstellt zwar (schwer verdauliche) Empfehlungen. Aber diese schwiegen sich aus zu üblichen Verfahren wie #Curve25519, die in RFCs beschrieben sind. Bei #telestrust gabs das mal - ist in neuen Versionen aber herausgefallen. Und die Zusammenstellung der #NIST verweist oft auf andere Dokumente.

@AG_KRITIS @kuketzblog

#InfoSec #Cryptographie #Kryptographie
#FollowerPower #PleaseBoost

@djb (Daniel J. Bernstein) tooted about a new blog post[1] he published. It's here:
https://blog.cr.yp.to/20250118-flight.html

It's interesting. He's a #mathematician and software guy that in more recent years has been known mostly for his work in #cryptography, #theoretical and #practical. You're probably using his #Curve25519 every day in your #communications.

I'm not a mathematician (by a long shot), but it's written in a pretty accessible manner - it's not #formulae and #turgid academic #prose.

The central point he's getting at, by my possibly-mistaken understanding of it, is that current "common sense" about when attacks against pre-quantum cryptography like #RSA (and therefore when post-quantum cryptography becomes critical) are badly mistaken - based on bad assumptions about how attacks work, how they're implemented, and on badly #extrapolating from those bad assumptions using logic that doesn't actually represent the way attacks are developed and become practical.

TL;DR is something along the lines of "#quantum cryptographic attacks against RSA will be practical sooner than most people think, and you should be deploying quantum-resistant cryptography now, not later".

It's worth reading if you're at all interested in #crypto and #security stuff.

He also mentions a project he's involved in that has been discussed separately, transparent post-quantum tunnelling for unmodified #server and #client #software. Link in post.

[1] Written more like a conference presentation, FWIW.

And this is all joined together into a page where an X25519 key exchange for TLS is explained: «Hands-on: X25519 Key Exchange: Let's exchange a secret to start a secure conversation.»

Excellent stuff anyone interested in #TLS and/or #ECC should always have handy. Wow!

6/6
#X25519 #KeyExchange #Curve25519
https://x25519.xargs.org/

Coffee and elliptic curves

https://f.lapo.it/display/6a1cc041-1164-7767-4e2f-8f0061563271

It’s 2023 and you’re designing a decentralised system based on public-key cryptography where a person’s identity(ies) are their public key(s).

Do you…

#cryptography #postQuantumCryptography #pqc #pq #ed25519 #curve25519 #x25519 #SmallWeb #Kitten

Ahead of today’s stream on implementing a basic end-to-end encrypted peer-to-peer Small Web chat example with #Kitten, here are some accessible resources on the math behind the #encryption:

1. @martin’s excellent Implementing #Curve25519/#X25519: A Tutorial on Elliptic Curve #Cryptography (https://martin.kleppmann.com/papers/curve25519.pdf)

2. The Animated Elliptic Curve (Visualizing Elliptic Curve Cryptography) https://curves.xargs.org/ and Hands-on: X25519 Key Exchange https://x25519.xargs.org/ by Michael Driscoll

Having issues with GitHub atm, account flagged, but I jotted down the commands to create a secure #EdDSA #PGP key. It requires #Ed25519 for cert, sign, and auth keys and #Curve25519 for encryption.

Strictly speaking you don’t require the auth key for your use case, it’s mostly useful only for SSH.

But this is the correct way to create a secure EdDSA key.

It’s also of note that it is the default setup for latest Kleopatra.

Here’s the link, feel free to drop it in the thread for further discussion:

https://telegra.ph/Best-practice-for-generating-a-secure-PGP-key-EdDSA-11-25

Funny when you think I was hanging out with Daniel ages ago without a clue who he was or what he’d done.

And to think how important his work is to the Small Web (and to privacy in general in the digital and networked age)…

PS. He also happens to be a lovely, humble guy and a very engaging and funny presenter. You can do far worse than to watch his talk from the conference we met at:

https://projectbullrun.org/surveillance/2015/video-2015.html

#cryptography #ed25519 #curve25519 #x25519 #DanielJBernstein #SmallWeb

Hi Mastodon, I'm looking for help.

Should I use Ed25519 or Curve25519 for long term identity?

more details: https://www.reddit.com/r/crypto/comments/fx7sx0/ed25519_or_curve25519_for_long_term_identity

#Crypto #Cryptography #signalApp #signal #ed25519 #x25519 #Curve25519

RFC 8731: Secure Shell (SSH) Key Exchange Method using Curve25519 and Curve448

Cela fait déjà pas mal de temps que des mises en œuvre du protocole #SSH intègrent les courbes elliptiques « Bernstein », comme #Curve25519. Ce RFC est donc juste une formalité, la normalisation officielle de cette utilisation.

https://www.bortzmeyer.org/8731.html

RFC 8410: Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure

Ce #RFC spécifie l'utilisation des #courbesElliptiques #Curve25519 et Curve448 dans PKIX, c'est-à-dire dans les certificats utilisés notamment pour TLS. Il réserve des identifiants pour les algorithmes, comme Ed25519.

https://www.bortzmeyer.org/8410.html

#EdDSA #ECDH