Timeline for OpenSSL - creating random elliptic curve and measuring performance
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2017 at 12:27 | comment | added | Daniel Herbrych | @SqueamishOssifrage I get this topic from my supervisor. It should be for scientific purposes. For example, I could generate one curve, use it and then use another curve etc... Im going to fail because I havnt time and I wasn't able to implement my own SEA algorithm in C with OpenSSL... | |
| Dec 8, 2017 at 23:04 | comment | added | Squeamish Ossifrage | There are many ways to get a diploma thesis other than generating elliptic curves on a Raspberry Pi! What is the problem you're trying to solve in order to get a diploma thesis of which you believe generating elliptic curves on a Raspberry Pi to be a subproblem? These days, modern ECC is usually so restricted that for a particular security target there is exactly one curve, or at worst a handful, satisfying all the relevant criteria and maximizing performance, so if you applied all the relevant criteria you'd get the same curve each time. (E.g., Curve25519, Curve448, or E-521.) | |
| Dec 8, 2017 at 11:03 | comment | added | Daniel Herbrych | @SqueamishOssifrage Because it's my diploma thesis... And I think now it's not as easy as I thought. For example curves over Fp, I generate a, b, p. But if I want to compute base point, I need to know order of the curve what should be done with SEA algorithm. And I can't find code of SEA, maybe I have to implement myself in C. Not easy, or? | |
| Dec 8, 2017 at 3:12 | comment | added | Squeamish Ossifrage | Why do you want to generate curves on devices with resource constraints? What is your actual goal here? | |
| Dec 8, 2017 at 0:12 | history | edited | Daniel Herbrych | CC BY-SA 3.0 |
added 298 characters in body
|
| Dec 3, 2017 at 16:57 | comment | added | Squeamish Ossifrage | Yes, that's the Sage I mean. You can see an example of its use in elliptic curve design at SafeCurves: safecurves.cr.yp.to/verify.html | |
| Dec 3, 2017 at 12:41 | answer | added | entrop-x | timeline score: 2 | |
| Dec 3, 2017 at 9:31 | comment | added | Daniel Herbrych | @SqueamishOssifrage Thanks, you mean this? | |
| Dec 3, 2017 at 1:28 | history | edited | Squeamish Ossifrage | CC BY-SA 3.0 |
Math monkey! Also capitalization and punctuation.
|
| Dec 2, 2017 at 23:45 | comment | added | Squeamish Ossifrage | You may find it easier to do all this with Sage than with OpenSSL. OpenSSL is intended for cryptography applications that use standard algorithms and curves, not for exploration in the math and curve selection. | |
| Dec 2, 2017 at 19:12 | history | edited | e-sushi | CC BY-SA 3.0 |
Fixed formatting and typos. Didn't convert all MathJax opportunities due to lack of time.
|
| Dec 2, 2017 at 17:49 | review | First posts | |||
| Dec 3, 2017 at 9:27 | |||||
| Dec 2, 2017 at 17:46 | history | asked | Daniel Herbrych | CC BY-SA 3.0 |