-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove DHT signatures #4613
Comments
@Stebalien you want me to take a stab at implementing this? |
@dirkmc that would be awesome! The current thinking is to:
... And then remove everything related to signatures/authors in DHT records. |
I guess if the DHT record validator checks the signature then the resolver doesn't need to fetch the public key at all when calling Currently the DHT
Should the DHT pass a hint to the validator to indicate whether or not it should go online to get the public key? |
The opposite. We don't want the validator fetching anything. The resolver needs to first fetch the key, put it in the peerstore, and then resolve the IPNS record. The validator can use the peerstore which won't go to the network to fetch it. On Put, we'd have the same behavior as we currently have (as the resolver won't go online). Eventually, we could add some form of offline/online hint (#4009) but we can cross that bridge later. |
Ah I see what you're saying, ok makes sense |
@Stebalien here's a first pass at the go-ipfs part: |
@Stebalien PR to remove Author and Signature from go-libp2p-record: libp2p/go-libp2p-record#15 |
Is there anything else that relies in DHT record signatures? |
@vyzo not that I know of. We should have @diasdavid chime in here, however, I'm pretty sure JS doesn't actually require this field either. @diasdavid, is JS like go in this? Will it only check this signature if present (so if we remove it, we won't have any issues)? My cursory look through the JS DHT code indicated that this was the case. |
Here's the go-libp2p-kad-dht PR: libp2p/go-libp2p-kad-dht#114 |
Instead, records should (and do) provide their own signatures. We should simply validate them from the DHT record validator function.
Supersedes #4597.
The text was updated successfully, but these errors were encountered: