You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Ntk_andna_counter_pubk 1.5KB

1234567891011121314151617181920212223242526272829303132333435363738
  1. == NTK_RFC 0007 ==
  2. Subject: ANDNA counter system based on public key
  3. ----
  4. This text describes a change to the counter_gnode system in ANDNA.
  5. It will be included in the final documentation, so feel free to correct it.
  6. But if you want to change the system here described, please contact us first.
  7. ----
  8. {{{
  9. The counter_gnode is used to prevent massive registrations of hnames by a
  10. single node, however there is a bug in the actual protocol.
  11. Currently the IP of the counter_gnode is the hash of the public key of the
  12. register node.
  13. The public key is part of the key pair used by the register_node to register
  14. and update its hnames, therefore there should be only one key pair for each
  15. node.
  16. However, nothing prevents the register node to create multiple key pairs,
  17. modify the ntkd code and use them at the same time.
  18. With this technique, the register node can have a new counter_gnode for each
  19. new generated key pair, avoiding in this way the registration limit.
  20. The solution is to calculate the IP of the counter_gnode using the hash of the
  21. IP of the register_node. This method was previously proposed but it was
  22. discarded because every time the register_node changes IP it will have a new
  23. counter_gnode. The new counter_gnode cannot know how many hnames the
  24. register_node registered before so it will accept all the new requests, but in
  25. reality, this is not a problem, in fact, the new counter_gnode can accept only
  26. 256 hnames, thus the limit is maintained.
  27. }}}
  28. ----
  29. related: ["Netsukuku RFC"]