top | item 7696187 Announcing ClearCrypt: a new transport encryption library 27 points| dbaupp | 12 years ago |mail.mozilla.org | reply 10 comments order hn newest [+] [-] nn3|12 years ago|reply What's the point of announcing something that doesn't exist?Don't waste your time on the link. It's pure vaporware.Actually vaporware usually usually has a design, but this is more like "write something in rust, but we're not sure yet what (but it sounds good)".So let's call it "nothingware" [+] [-] bascule|12 years ago|reply We're aiming for a project where all commits receive public scrutiny. This includes how the project is governed.We're discussing contributing guidelines here:https://github.com/clearcrypt/clearcrypt/pull/2Initial code PR with a ChaCha20 implementation here:https://github.com/clearcrypt/clearcrypt/pull/3 load replies (1) [+] [-] Ygg2|12 years ago|reply I suppose to gather crypto people to contributes via patches, reviews or whatever else. [+] [-] higherpurpose|12 years ago|reply CurveCP sounds good, but what's Noise? And could CurveCP be improved by using QUIC instead of UDP? [+] [-] infinity0|12 years ago|reply https://github.com/trevp/noise/wiki [+] [-] kbaker|12 years ago|reply QUIC already has a lot of TLS support baked in afaik...NaCL already exists and CurveCP is a part of that, why not just add a Rust port? (and a protocol for certificate transport) [+] [-] yetfeo|12 years ago|reply > Emphasis will be placed on simplicity, clarity, and audibility.Most projects start with this as an implicit goal. Unfortunately they tend to grow out of control as the code base gets larger. [+] [-] bascule|12 years ago|reply We aim to make it an explicit goal, rather than implicit. Wherein other projects this is a "would be nice", in this project it's an absolute necessity for the project's security and therefore success. [+] [-] bradhe|12 years ago|reply Wow, you can announce stuff before it's actually built now?
[+] [-] nn3|12 years ago|reply What's the point of announcing something that doesn't exist?Don't waste your time on the link. It's pure vaporware.Actually vaporware usually usually has a design, but this is more like "write something in rust, but we're not sure yet what (but it sounds good)".So let's call it "nothingware" [+] [-] bascule|12 years ago|reply We're aiming for a project where all commits receive public scrutiny. This includes how the project is governed.We're discussing contributing guidelines here:https://github.com/clearcrypt/clearcrypt/pull/2Initial code PR with a ChaCha20 implementation here:https://github.com/clearcrypt/clearcrypt/pull/3 load replies (1) [+] [-] Ygg2|12 years ago|reply I suppose to gather crypto people to contributes via patches, reviews or whatever else.
[+] [-] bascule|12 years ago|reply We're aiming for a project where all commits receive public scrutiny. This includes how the project is governed.We're discussing contributing guidelines here:https://github.com/clearcrypt/clearcrypt/pull/2Initial code PR with a ChaCha20 implementation here:https://github.com/clearcrypt/clearcrypt/pull/3 load replies (1)
[+] [-] Ygg2|12 years ago|reply I suppose to gather crypto people to contributes via patches, reviews or whatever else.
[+] [-] higherpurpose|12 years ago|reply CurveCP sounds good, but what's Noise? And could CurveCP be improved by using QUIC instead of UDP? [+] [-] infinity0|12 years ago|reply https://github.com/trevp/noise/wiki [+] [-] kbaker|12 years ago|reply QUIC already has a lot of TLS support baked in afaik...NaCL already exists and CurveCP is a part of that, why not just add a Rust port? (and a protocol for certificate transport)
[+] [-] kbaker|12 years ago|reply QUIC already has a lot of TLS support baked in afaik...NaCL already exists and CurveCP is a part of that, why not just add a Rust port? (and a protocol for certificate transport)
[+] [-] yetfeo|12 years ago|reply > Emphasis will be placed on simplicity, clarity, and audibility.Most projects start with this as an implicit goal. Unfortunately they tend to grow out of control as the code base gets larger. [+] [-] bascule|12 years ago|reply We aim to make it an explicit goal, rather than implicit. Wherein other projects this is a "would be nice", in this project it's an absolute necessity for the project's security and therefore success.
[+] [-] bascule|12 years ago|reply We aim to make it an explicit goal, rather than implicit. Wherein other projects this is a "would be nice", in this project it's an absolute necessity for the project's security and therefore success.
[+] [-] nn3|12 years ago|reply
Don't waste your time on the link. It's pure vaporware.
Actually vaporware usually usually has a design, but this is more like "write something in rust, but we're not sure yet what (but it sounds good)".
So let's call it "nothingware"
[+] [-] bascule|12 years ago|reply
We're discussing contributing guidelines here:
https://github.com/clearcrypt/clearcrypt/pull/2
Initial code PR with a ChaCha20 implementation here:
https://github.com/clearcrypt/clearcrypt/pull/3
[+] [-] Ygg2|12 years ago|reply
[+] [-] higherpurpose|12 years ago|reply
[+] [-] infinity0|12 years ago|reply
[+] [-] kbaker|12 years ago|reply
NaCL already exists and CurveCP is a part of that, why not just add a Rust port? (and a protocol for certificate transport)
[+] [-] yetfeo|12 years ago|reply
Most projects start with this as an implicit goal. Unfortunately they tend to grow out of control as the code base gets larger.
[+] [-] bascule|12 years ago|reply
[+] [-] bradhe|12 years ago|reply