I2pd 2.36.0

Milestone information

Project:
I2pd
Series:
trunk
Version:
2.36.0
Released:
 
Registrant:
R4SAS
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon i2pd-2.36.0.tar.gz (md5, sig) source code 5
last downloaded 72 weeks ago
Total downloads: 5

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

ECIES-x25519 (crypto type 4) for new routers
reg.i2p for default addressbook instead inr.i2p
Yggdrasil transports and reseeds
Encrypted lookup and publications to ECIES-x25519 floodfiils
Dump addressbook in hosts.txt format
Try to connect to all compatible addresses from peer's RouterInfo
Threads naming
ECIES-X25519-AEAD-Ratchet for shared local destination
Fixed handling chunked HTTP response in addressbook
Calculate missing ECIES-X25519-AEAD-Ratchet tags for multiple streams with the same destination
Refresh on swipe in Android webconsole
Request RouterInfo through exploratory tunnels if direct connection to fllodfill is not possible
Select reachable router of inbound tunnel gateway
Reseed if no compatible routers in netdb
Check if public x25519 key is valid
Replace LeaseSet completely if store type changes
Limit tunnel length to 8 hops and quantity to 16
Decrypt follow-on ECIES-X25519-AEAD-Ratchet NSR messages
Fixed SSU crash on termination
Correct NAME for NAMING REPLY in SAM
Don't create notification when Windows taskbar restarted
Viewport and styles on error in HTTP proxy
Cumulative SSU ACK bitfields

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.