Official eMule-Board: Using Rsa Public Key Hash As Node Id To Prevent Keyword Hijack - Official eMule-Board

Jump to content


Page 1 of 1

Using Rsa Public Key Hash As Node Id To Prevent Keyword Hijack

#1 User is offline   highfly 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: 22-November 11

Posted 22 November 2011 - 07:21 AM

1. Generate a RSA key pair
2. Use hash (public key) as node id
3. Send public key and signature of gettimeofday(), ip and port as certification

When update the contact information, it can be verified whether the node id is owner by this ip and port for no firewalled node.
Using a hash node id, we can prevent the keyword hijack. It's hard to generate node id near by the keyword.

But the asymmetric signing need a lot of CPU time.

This solution is totally decentralized node generation algorithm.
0

#2 User is offline   Some Support 

  • Last eMule
  • PipPipPipPipPipPipPip
  • Group: Yes
  • Posts: 3628
  • Joined: 27-June 03

Posted 22 November 2011 - 08:52 AM

There is already a hash key/token solution (based on a hash of a secret + the receivers IP) in place which prevents node id hijacking. Asymmetric encryption offers no advantages over the current solution.

#3 User is offline   highfly 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: 22-November 11

Posted 22 November 2011 - 09:02 AM

View PostSome Support, on 22 November 2011 - 08:52 AM, said:

There is already a hash key/token solution (based on a hash of a secret + the receivers IP) in place which prevents node id hijacking. Asymmetric encryption offers no advantages over the current solution.


Could you give a link to this solution?
I am starting to read some paper on emule kad and I am very interesting to build up a decentralized blog system on Kad.
0

  • Member Options

Page 1 of 1

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users