Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handshake parameters #161

Closed
whyrusleeping opened this issue Oct 13, 2014 · 3 comments
Closed

Handshake parameters #161

whyrusleeping opened this issue Oct 13, 2014 · 3 comments

Comments

@whyrusleeping
Copy link
Member

I think we should modify the handshake protocol between nodes to include options such as "prefer compression" and "prefer encryption" and if the both peers can agree on an encryption/compression type, applying that as a filter over the connection.
@jbenet
Copy link
Member

jbenet commented Oct 13, 2014

Very much agreed. I think we should abstracting out all this into a package like crypto/tls, basically a tls-lite type of thing. Will be much easier to audit + verify + reuse.

@whyrusleeping whyrusleeping mentioned this issue Oct 14, 2014
Closed
@whyrusleeping
Copy link
Member Author

Another parameter that I was thinking of would be "Supported Services", so nodes can run "Just a DHT" or opt out of having diagnostics, or maybe just serve bitswap, or maybe just serve overlay (when we get there), or any combination of them all.

@jbenet
Copy link
Member

jbenet commented Oct 20, 2014

Another parameter that I was thinking of would be "Supported Services", so nodes can run "Just a DHT" or opt out of having diagnostics, or maybe just serve bitswap, or maybe just serve overlay (when we get there), or any combination of them all.

+:100: ^ :100:

@aschmahmann aschmahmann mentioned this issue May 14, 2021
Closed
71 tasks
ariescodescream pushed a commit to ariescodescream/go-ipfs that referenced this issue Oct 23, 2021
@Stebalien
return info for connected peers in handleFindPeer
2c8f387 
This way, users who are actually trying to find a peer (not just nodes near a
key in the DHT) can find that peer, even if they aren't a DHT server and/or
aren't in anyone's routing table.

fixes ipfs#161
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Feb 25, 2022
@thibmeu
feat: add DNS.MaxCacheTTL for DNS-over-HTTPS resolvers (ipfs#161)
ba468c8
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Feb 25, 2022
@thibmeu
go-ipfs-config: feat: add DNS.MaxCacheTTL for DNS-over-HTTPS resolvers (
b863234 
ipfs#161)
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Mar 4, 2022
@thibmeu
go-ipfs-config: feat: add DNS.MaxCacheTTL for DNS-over-HTTPS resolvers (
0f3ba31 
ipfs#161)
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Mar 4, 2022
@thibmeu
go-ipfs-config: feat: add DNS.MaxCacheTTL for DNS-over-HTTPS resolvers (
9a0bd0f 
ipfs#161)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jbenet @whyrusleeping