-
Notifications
You must be signed in to change notification settings - Fork 41
The IPFS bootstrap nodes seem to use 1024 bits RSA keys #378
Comments
@lgierth @kyledrake what's the main reason why we don't use 1024 bits keys in our Infrastructure nodes? |
Ping @lgierth and @kyledrake |
Historic reasons -- we bumped the default to 2048 at some point. There are a few 2048 bit peerIDs in the default bootstrap list that I added like 9 months ago - we should:
|
@lgierth can we have a list of all the nodes and their keys here? |
New nodes (not running yet, just PeerIDs):
Old nodes:
|
@lgierth is it possible we could have a similar schema as the old |
They're already in go-ipfs's default bootstrap. I also think that at one point we'd break from that scheme anyway when there's a situation where we need to quickly add new nodes (brute-forcing these took a day or three). |
I got hit by this:
It seems that in the default boostrapper list, only one node has a key >= 2048 and support IPv4, which makes it a fairly brittle and slow bootstrap process. Note: I'm using libp2p directly, which has a 2048 minim length required, unlike go-ipfs (512). |
Got hit too, I will try to expedite a fix |
For legacy compatibility, the 'old' bootstrap nodes with small keys are essentially stuck in-place, and are deprecated by the 'new nodes', under Closing as resolved, but please reopen if you run into issues. |
@mburns it might be worth making an announcement so that people update their IPFS/libp2p configs + checking where those old nodes show up (in the default configs + examples) and updating them to only show the new ones. |
indeed. I'll track some notes and the announcement here: #496 |
While 2048 bits keys are default and would be preferred.
cc @diasdavid
The text was updated successfully, but these errors were encountered: