I2P 0.9.6
Milestone information
- Active:
- Yes. Drivers can target bugs and blueprints to this milestone.
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
Release notes
0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to Jetty 7.6.10 (2013-03-12). See below for important information on the Jetty update. The Jetty 7 series is actively maintained and we plan to stay current with it in future I2P releases.
Most users will update via HTTP. Those running development builds will attempt to update via the experimental in-network bittorrent with i2psnark. We've fixed some bugs that will enable more users to update via torrent in the 0.9.7 update cycle.
Important fix for Windows Eepsites, first install 0.9.5 only
If you first installed I2P with version 0.9.5, on Windows only, we recommend that you follow the following instructions to fix your eepsite location before you update to 0.9.6. Only original installations of 0.9.5-0 on Windows are affected by this issue. If your router version is 0.9.5-0-win1, you already have the fix and need not take any action.
See http://
Jetty 7 Migration Details
For most people, the update should just work. If you have multiple Jetty eepsites, OR have made changes to jetty.xml or other Jetty configuration files, including changing the port from 7658, you MUST take manual action AFTER updating.
* After update, the router will migrate your jetty.xml files to the new Jetty 7 format.
* The migration resets the port to 7658. If you have more than one Jetty eepsite, OR your eepsite is NOT on port 7658, OR you have made other modifications to jetty.xml (for example changing the listen address from 127.0.0.1 to 0.0.0.0), you MUST edit ALL your jetty.xml files to fix them up after updating, and restart again.
The following files will be backed up with a ".jetty6" suffix and then migrated
If you have made local changes, you may have to edit them manually and restart.
See http://
* ~/.i2p/
* ~/.i2p/
* ~/.i2p/
* ~/.i2p/
* ~/.i2p/
* ~/.i2p/
* ~/.i2p/
Plugins
Most plugins should work fine with Jetty 7.
* The I2PControl and zzzot plugins must be updated. Your router should download and install the new versions shortly after starting 0.9.6.
* If a plugin does not work, please contact the maintainer for that plugin.
DETAILS
Bug Fixes
- Several bugs with Windows installation (see above)
- Fix default form action in i2ptunnel
- Fix links on iframed console pages
- Better detection of 64-bit Windows to prevent crashes by systray
- Fix bug preventing router update via torrent
- Several SSU fixes for NATs that change UDP ports
- Ignore unsupported IPs in RouterInfos when selecting an address (prep for IPv6)
- Ignore unused option bits in Database Lookup Message (prep for requesting encrypted response)
- Fix HTTP proxy error response for malformed URIs
- Recognize UPnP devices without port forwarding capability
Other
- Jetty 7.6.10 (see above for migration information)
- Limit page size in i2psnark
- Add data directory and page size configuration to i2psnark
- Support multiple i2psnark instances
- Piece size adjustments in i2psnark
- Add more graphing support for combined bandwidth graph
- Block b32.i2p supercookies
- Allow stopping clients on /configclients
- Check for nonce count replays in HTTP client
- Support SASL authentication in IRC proxy
- Several cleanups and minor fixes in the update manager
- Translation updates: German, Portuguese, Russian, Spanish, and Swedish
- Update GeoIP data (new installs and PPA only)
Changelog
This release does not have a changelog.
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.
