4 ms·

This is ingenious, your public address is also your public key, and the payload of the packet can only be decrypted by your private key. So awesome, it has encr

This is ingenious, your public address is also your public key, and the payload of the packet can only be decrypted by your private key. So awesome, it has encryption built in.

theptip 10y ago
Doesn't that make key rotation painful?
- Natanael_L 10y ago
  It does mean that key rotation = address rotation
- Hyperborian 10y ago
  It's true that key rotation would mean changing your IP address, but that is something that is fairly routine on the current internet already, though certainly infrequently done by major sites and services. The primary purpose of the encryption in CJDNS is simply to establish identity and make the completely decentralized addressing system (the key component) possible. Using the keys to do built in transparent end-to-end encryption is an important and valuable feature as well, but ultimately is secondary. If you need the kind of security that requires frequent key rotation, you should really be using an additional encryption and identity verification layer on top, just like with the current internet. Also, CJDNS uses 512 bit keys, and the nature of how the protocol works means that any address collisions (which would be unavoidable by someone impersonating you) would be obvious and detectable, so for it's intended purpose it should not be necessary to rotate keys very often at all.
  - theptip 10y ago
    Is it common to use DNS or some other name resolution system to get from 'abstract service name' to 'concrete IP'? Just thinking through the remediation steps in the case of compromised keys; how would you propagate the change-of-identity information?
    - Hyperborian 10y ago
      Currently the typical solution on Hyperboria is indeed the current internet DNS system, primarily for lack of a widely accepted decentralized alternative. A truly decentralized alternative to the current DNS system is a difficult problem to solve, and one that people continue to work on. IP addresses are easier because they are interchangeable, it really doesn't matter which one you have as long as you're the only one who has it. Domain names, though, are not at all, in fact that's basically their entire point. The question of who gets which names, issues around fraud and phishing, mass registration and domain squatting... how do you solve those problems without some sort of authority to arbitrate and enforce rules? The closest alternative to the ideal that I know of right now is probably Namecoin, which works quite well with Hyperboria, but it still involves a number of compromises that not everyone is happy with.
      - theptip 10y ago
        Thanks for the detailed explanation.
robert_foss 10y ago
So asymmetric crypto is done on the entire payload of the packet? That sounds horrifically CPU intensive. Also, it provides no forward secrecy.
- tyrellj 10y ago
  https://github.com/cjdelisle/cjdns/blob/master/doc/faq/security.md https://github.com/cjdelisle/cjdns/blob/master/doc/faq/secur...

This is ingenious, your public address is also your public key, and the payload of the packet can only be decrypted by your private key. So awesome, it has encryption built in.

theptip 10y ago

Doesn't that make key rotation painful?

Natanael_L 10y ago
It does mean that key rotation = address rotation
Hyperborian 10y ago
It's true that key rotation would mean changing your IP address, but that is something that is fairly routine on the current internet already, though certainly infrequently done by major sites and services. The primary purpose of the encryption in CJDNS is simply to establish identity and make the completely decentralized addressing system (the key component) possible. Using the keys to do built in transparent end-to-end encryption is an important and valuable feature as well, but ultimately is secondary. If you need the kind of security that requires frequent key rotation, you should really be using an additional encryption and identity verification layer on top, just like with the current internet. Also, CJDNS uses 512 bit keys, and the nature of how the protocol works means that any address collisions (which would be unavoidable by someone impersonating you) would be obvious and detectable, so for it's intended purpose it should not be necessary to rotate keys very often at all.
- theptip 10y ago
  Is it common to use DNS or some other name resolution system to get from 'abstract service name' to 'concrete IP'? Just thinking through the remediation steps in the case of compromised keys; how would you propagate the change-of-identity information?
  - Hyperborian 10y ago
    Currently the typical solution on Hyperboria is indeed the current internet DNS system, primarily for lack of a widely accepted decentralized alternative. A truly decentralized alternative to the current DNS system is a difficult problem to solve, and one that people continue to work on. IP addresses are easier because they are interchangeable, it really doesn't matter which one you have as long as you're the only one who has it. Domain names, though, are not at all, in fact that's basically their entire point. The question of who gets which names, issues around fraud and phishing, mass registration and domain squatting... how do you solve those problems without some sort of authority to arbitrate and enforce rules? The closest alternative to the ideal that I know of right now is probably Namecoin, which works quite well with Hyperboria, but it still involves a number of compromises that not everyone is happy with.
    - theptip 10y ago
      Thanks for the detailed explanation.

robert_foss 10y ago

So asymmetric crypto is done on the entire payload of the packet? That sounds horrifically CPU intensive. Also, it provides no forward secrecy.

tyrellj 10y ago
https://github.com/cjdelisle/cjdns/blob/master/doc/faq/security.md https://github.com/cjdelisle/cjdns/blob/master/doc/faq/secur...