New i2pd release 2.52.0
New i2pd release 2.52.0
github.com GitHub - PurpleI2P/i2pd: 🛡 I2P: End-to-End encrypted and anonymous Internet
🛡 I2P: End-to-End encrypted and anonymous Internet - PurpleI2P/i2pd
![GitHub - PurpleI2P/i2pd: 🛡 I2P: End-to-End encrypted and anonymous Internet](https://lemmy.world/pictrs/image/2647b041-65c3-4c98-8dac-a30e83ab7735.png?format=webp&thumbnail=256)
[2.52.0] - 2024-05-12
Added
- Separate threads for persisting RouterInfos and profiles to disk
- Give preference to address with direct connection
- Exclude addresses with incorrect static or intro key
- Avoid two firewalled routers in the row in tunnel
- Drop unsolicited database search replies
Changed
- Increase number of hashes to 16 in exploratory lookup reply
- Reduce number of a RouterInfo lookup attempts to 5
- Reset stream RTO if outbound tunnel was changed
- Insert previously excluded floodfill back when successfully connected
- Increase maximum stream resend attempts to 9
- Reply to exploratory lookups with only confirmed routers if low tunnel build rate
- Don't accept too old RouterInfo
- Build client tunnels through confirmed routers only if low tunnel build rate
- Manage netDb requests more frequently
- Don't reply with closer than us only floodfills for lookup
Fixed
- Crash on router lookup if exploratory pool is not ready
- Race condition in excluded peers for next lookup
- Excessive number of lookups for same destination
- Race condition with transport peers during shutdown
- Corrupted RouterInfo files
3 comments
Never heard of this before, is this a fill blown replacement for the Internet?
1 0 ReplyYou've never heard of I2P? It's similar in concept to TOR but also has its differences
7 0 ReplyNope, just an encrypted layer. I2p wiki
6 0 Reply