Skip to content
This repository has been archived by the owner. It is now read-only.

Why aren't DHT public key records signed? #220

Closed
JustinDrake opened this issue Jan 17, 2017 · 2 comments
Closed

Why aren't DHT public key records signed? #220

JustinDrake opened this issue Jan 17, 2017 · 2 comments

Comments

@JustinDrake
Copy link

JustinDrake commented Jan 17, 2017

IPFS clients publish their public key on the DHT. Those records are not signed. Why not?

My guess: the validity of the public key can be checked by hashing it and comparing it to the peer ID. No signature required.

@Kubuxu
Copy link

Kubuxu commented Jan 23, 2017

Yes the identity directly corresponds to the public key, it is better signature then RSA could ever give. Other DHT records (provider) are not currently signed due to size and computation costs of RSA. We are planning switch to x25519 crypto which will enable us to sign those records fast and cheaply

@flyingzumwalt
Copy link
Contributor

flyingzumwalt commented May 23, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants