lupine/hide-eid
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Files
118b7b8125f30060b3835526486c0301a6b06854
hide-eid/pass-1/rloc-registry.json

29 lines
640 B
JSON
Raw Normal View History

pass 1: first night of code. Nothing interesting yet.
2013-08-02 23:58:54 +01:00
{
"type": "rloc-registry",
Second night's commit. We're a bit closer to something sane, now. We can wrap, but not unwrap, packets. Asymmetric encryption is *big*. encrypted text with a 4096-bit RSA public key is 512 bytes. We can't fragment yet. Fortunately, this isn't an infinite regress once we *can* fragment. Performance is still a big question mark, of course. There may still be endianness issues hanging around. The eid<->rloc map is almost certainly far, far too slow to be of any use in the real world.
2013-08-04 03:07:20 +01:00
"eid_rloc_map": [
Another night's work - move to ECDH + AES256 from RSA pubkey
2013-08-08 00:48:02 +01:00
{ "family":"ipv4", "network":"172.16.10.0", "netmask":24, "rloc":"81.187.47.40"},
{ "family":"ipv4", "network":"172.16.11.0", "netmask":24, "rloc":"213.138.102.147"}
Second night's commit. We're a bit closer to something sane, now. We can wrap, but not unwrap, packets. Asymmetric encryption is *big*. encrypted text with a 4096-bit RSA public key is 512 bytes. We can't fragment yet. Fortunately, this isn't an infinite regress once we *can* fragment. Performance is still a big question mark, of course. There may still be endianness issues hanging around. The eid<->rloc map is almost certainly far, far too slow to be of any use in the real world.
2013-08-04 03:07:20 +01:00
],
pass 1: first night of code. Nothing interesting yet.
2013-08-02 23:58:54 +01:00
"keys": {
Some doc / example updates
2013-08-06 23:16:28 +01:00
Another night's work - move to ECDH + AES256 from RSA pubkey
2013-08-08 00:48:02 +01:00
"81.187.47.40":
Second night's commit. We're a bit closer to something sane, now. We can wrap, but not unwrap, packets. Asymmetric encryption is *big*. encrypted text with a 4096-bit RSA public key is 512 bytes. We can't fragment yet. Fortunately, this isn't an infinite regress once we *can* fragment. Performance is still a big question mark, of course. There may still be endianness issues hanging around. The eid<->rloc map is almost certainly far, far too slow to be of any use in the real world.
2013-08-04 03:07:20 +01:00
"-----BEGIN PUBLIC KEY-----
Another night's work - move to ECDH + AES256 from RSA pubkey
2013-08-08 00:48:02 +01:00
MD4wEAYHKoZIzj0CAQYFK4EEAB4DKgAEdlvMHCK1rsACyk53Oo5PEfmj/ZON3oKt
wXgyHsydIb6JMt2tD3bFZA==
-----END PUBLIC KEY-----",
Some doc / example updates
2013-08-06 23:16:28 +01:00
Another night's work - move to ECDH + AES256 from RSA pubkey
2013-08-08 00:48:02 +01:00
"213.138.102.147":
Second night's commit. We're a bit closer to something sane, now. We can wrap, but not unwrap, packets. Asymmetric encryption is *big*. encrypted text with a 4096-bit RSA public key is 512 bytes. We can't fragment yet. Fortunately, this isn't an infinite regress once we *can* fragment. Performance is still a big question mark, of course. There may still be endianness issues hanging around. The eid<->rloc map is almost certainly far, far too slow to be of any use in the real world.
2013-08-04 03:07:20 +01:00
"-----BEGIN PUBLIC KEY-----
Another night's work - move to ECDH + AES256 from RSA pubkey
2013-08-08 00:48:02 +01:00
MD4wEAYHKoZIzj0CAQYFK4EEAB4DKgAEaDuTFicM87FKVqEHUMGW4BaFz9GAwjAC
+pnmMUh00yFgDEyi6ozUrw==
-----END PUBLIC KEY-----"
Second night's commit. We're a bit closer to something sane, now. We can wrap, but not unwrap, packets. Asymmetric encryption is *big*. encrypted text with a 4096-bit RSA public key is 512 bytes. We can't fragment yet. Fortunately, this isn't an infinite regress once we *can* fragment. Performance is still a big question mark, of course. There may still be endianness issues hanging around. The eid<->rloc map is almost certainly far, far too slow to be of any use in the real world.
2013-08-04 03:07:20 +01:00
Some doc / example updates
2013-08-06 23:16:28 +01:00
pass 1: first night of code. Nothing interesting yet.
2013-08-02 23:58:54 +01:00
}
Some doc / example updates
2013-08-06 23:16:28 +01:00
}
Reference in New Issue Copy Permalink