3 ms·
Me: Still using ed25529tools,^1 which predates minisign. Separation of concerns, fewer "features", fewer options to remember. Uses original nacl-20110221 sour
by 1vuio0pswjnm7 5y ago
Me: Still using ed25529tools,^1 which predates minisign. Separation of concerns, fewer "features", fewer options to remember. Uses original nacl-20110221 source. More concise code. Unable to find compelling reason to switch to something more complicated.
1.
https://github.com/stribika/curveprotect/tree/master/source/ed25519tools https://github.com/stribika/curveprotect/tree/master/source/...
- rdpintqogeogsaa 5y ago> Uses original nacl-20110221 source. Considering the website[0] starts with "WARNING: This signature software (both at the C level and at the C++ level) is a prototype. It will be replaced by the final system Ed25519 in future NaCl releases. A NaCl-compatible Ed25519 implementation is already available as part of SUPERCOP," I'm not convinced that using the original NaCl source for signing is a good sign. [0] https://nacl.cr.yp.to/sign.html https://nacl.cr.yp.to/sign.html
- deleted 5y ago[deleted]