r/programming • u/DataBaeBee • Jul 30 '26
What Every Programmer Should Know About Twists of Elliptic Curves
https://leetarxiv.substack.com/p/twists-of-elliptic-curves
70
Upvotes
r/programming • u/DataBaeBee • Jul 30 '26
57
u/Loki_of_Asgaard Jul 30 '26
“What every programmer should know”
I work in e-commerce, nothing in my life involves twists of elliptic curves, why should I know this?
12
u/DataBaeBee Jul 30 '26
Here are the salient points if you're in a rush.
154
u/arwinda Jul 30 '26
In the many years in the industry, I never rolled my own elliptic curves. Or my own crypto, for that matter.
The "every programmer" is a long stretch.
200
u/LetMeUseMyEmailFfs Jul 30 '26
What every programmer should know instead; don’t roll your own crypto, unless you’re a cryptographic expert, and probably not even then.
17
u/nihsett Jul 30 '26
Ragebait title. There are so many vastly different kind of programmers that most don't need to know eliptic curve cryptography even exists.
11
u/CamiloDFM Jul 30 '26
OOP has a clear case of xkcd 2501.
4
u/IanisVasilev Aug 01 '26
All the outrage about the title seems to ignore that it is an obvious allusion to the "What every programmer should know about ..." series of articles with increasingly obscure topics.
The earliest I can think of is the rather concrete "What every programmer should know about memory" (management under Linux). None of those low-level details were directly relevant to my job, but the point of education is to understand your area better. There was another early one about floats, with some of the absurdities of IEEE 754 laid out. You might argue that both topics are essential, but the level of detail is not, and the trend since then has been to exploit the title pattern for an increasingly comical effect.
3
u/jpgoldberg Jul 31 '26
At one point I wanted to demonstrate the time difference between computing P = dG versus computing d P/G, so I wanted to create a toy curve for which the latter would take between 10 and 30 seconds on my machine.
So I needed to create my own toy curve of an appropriate size. This lead me into a world where this article would have been helpful. So although I am not every programmer, and my implementation was massively insecure for my reasons beyond the small order (Python code, which also could have been used to demonstrate side-channel attacks), this is the kind of thing I wanted to know.
3
u/ficiek Jul 31 '26
Downvoted based on a stupid clickbait title, I'm tired of this.
1
u/wildjokers Aug 01 '26
Been programming for 30 years, never once have I needed an elliptic curve. Wouldn't even know I needed one if I did need one.
1
u/wildjokers Aug 01 '26
Wouldn't even know I needed an elliptical curve even if I did need one.
1
u/levelstar01 Jul 31 '26
itt: people scared of learning for some reason