Releases: i2p/i2p.firefox
i2p-firefox-2.4.9
I2P Easy-Install Bundle for Windows 2.4.9
This is a pre-release of the I2P Easy-Install Bundle for Windows.
This changes how the I2P bundle and browser profile manager are installed and integrated with the host system.
The Easy-Install bundle is now a "portable" system that can be moved to different locations within or between Windows file-systems while retaining all built-in functionality.
A shortcut for starting the I2P router is still provided by the installer for convenience, but the shortcuts for starting the I2P Browser are now integrated with the I2P desktop UI.
The browser profile manager itself has been split away from the monolithic I2P router+Java/jpackage, and moved into an I2P plugin managed by the router.
While this was done primarily to reduce how complex the existing code was, this also results in behavior which is closer to the main distribution of I2P for Windows and will lead to a more flexible installer, which can bundle additional default plugins and may be suitable for installation as a Windows service.
I2P Plugins can also be updated independently of the router that hosts them, so it will be possible to update the browser profile manager independently of the router itself.
It also means that the browser profile manager can be un-installed by uninstalling the plugin, and much more importantly that the browser profile manager is now compatible with all Java I2P distributions.
Why a dev build 3 weeks before the release?
By further delineating the components of the bundle, these changes also affected how the release process happens.
In particular the build process of each component has been encapsulated in a CI description which can be reproduced on a local PC.
This simplifies and automates the build process by ensuring that up-to-date build tools are installed in a brand-new container for every build.
In effect this should speed up the release process for I2P Easy-Install for Windows considerably.
This release is a test-run of the new process, so I can document what is going on.
It breaks down roughly like this:
- It takes ~22 minutes to compile all the targets for the
i2p.plugins.firefoxand make the resulting artifacts available. During this process, I must insert 1 HSM and enter 1 password. (This part used to be about 30 steps, now it takes 1) - It takes ~22 minutes to compile all the targets for the
i2p.firefoxproject and make the resulting artifacts available. This process produces only unsigned artifacts identified by their hashes, and is non-interactive. (This part used to be around 60 steps the first time, and 40 steps each additional time) i2p.firefoxupdates are signed in their.su3form. TheNSIS-powered.exeinstaller is the current updater. The next step is to sign just this installer and generate a torrent of the result. (This process used to depend on the previous build process and couldn't be done independently. Now it takes about 30 seconds)- Generate and sign a newsfeed to notify the users of an update. This process is the only process that is slower when containerized, because there are dozens of feeds to be signed in their respective containers. It takes about an hour.
For you the end user, nothing much should change.
You'll get your updates a lot faster, and have more options available for testing.
The same installer is used for the updater, and the process is handled the same way.
However for developers, testers, and maintainers, this release will result in big changes for the better.
This release still embeds a 2.4.0 Java I2P router. No changes have been made to update the embedded router.
Network behavior will be unchanged until the official 2.5.0 release.2023-01-23 idk
- Move build scripts to their own directory and make them use correct paths when moved
- Add EXTRA to router when generating embedded router jars.
2022-09-20 idk
- improve compatibility with local service installs and with un-bundled installs side-by-side with bundled intalls
- version 1.9.7
2022-09-18 idk
- remove unstable/deprecated targets from Makefile.
- make it fatal if a jpackaged I2P is not found, the profile launcher is now part of the jpackage
2022-09-16 idk
- remove unstable/deprecated functionality. Better solutions have been developed and instructions
on how to use them are provided. - update build documentation.
2022-09-13 idk
- make it a "portable" application in that the entire app and config can be carried on a portable
storage device. Requires minor tweaks to work well still.
2022-09-08 idk
- Generate a source tarball when we checkout a branch of i2p.i2p
- Upload a source tarball when we do a daily build
- Clean up a source tarball when running the clean script. Regenerate tarball after cleaning.
2022-09-06 idk
- Point release 1.9.5, fixes a bug which occurs more often on Windows 11, fixes a SusiDNS issue
2022-08-28 idk
- Migrate away from batch scripts and simply launch a browser if I2P is already running.
This is more flexible, stable, and simplet to install - Improves compatibility with detatched and un-bundled routers on the same system
- Fixes bugs in Firefox path finding
2022-05-8 idk
- Add translations for Arabic, German, French, Italian, Japanese, Portuguese, Russian,
and Chinese. - Add support for I2P+ Router Console detection. Not an endorsement of I2P+, just
a convenience requested by a helpful user. - The build system has been radically improved in order to be simpler to set up and
configure. - Fixed a bug where the build deleted a config file.
2022-05-5 idk
- Fix a bug where the I2P router detection inappropriately prioritized an easy
install bundle when a non-bundled instal was in use.
2022-03-25 idk
- This release adds support for user-mode, non-privileged installation of the
jpackaged router and the browser profile. Admin installation is still supported
and detected automatically, to support existing bundles. - On restart to update, will detect if a router requires admin rights to install
and will ask the user to authorize the update. In user-mode, no prompt will ever
be seen. - Updates to the Firefox profiles to improve compatibility with more Firefoxes
2022-02-10 idk
- This release fixes automatic update using Bittorrent within the I2P network
and the custom Update PostProcessor. - Fixes the first-run launcher bug
- Drastically simplifies the Windows build process
- Adds support for development releases
- Adds support for Debian packaging(Of just the Firefox profile)
2021-11-1 idk
- HTTPS Everywhere will now self-disable on some Firefox versions. This is not
an issue since HTTPS Everywhere is deprecated in favor of Firefox built-in
HTTPS enforcement features. - .bat Script: Detect location of C:\Program Files\I2P or
C\Program Files(x86)\I2P in launcher scripts - NSIS changes
- Make launcher scripts static artifacts instead of generating them during
the install process - If a jpackaged I2P router is present in $checkout/I2P, include it in an
installer. - If a running installer doesn't find an I2P router in Program Files, install
the jpackaged I2P router. Mark it as jpackaged so we can quickly determine
from other applications.
- I2P in Private Browsing changes
- bugfix for
reset()of dynamic theme - bugfix for erroneous redirect/contain of mis-identified I2PSnark containers
- improve support for in-I2P HTTPS
- use global CSS on pageAction panels for HTTP, HTTPS, and Bittorrent(@Sadie)
- improve support for I2PSnark web handler in HTTPS tabs
- icon update(@Sadie)
- contain android-incompatible features so they won't be executed on Fennec
- translate into Spanish
- visually conceal/reveal features based on whether they are enabled/configured.
- I2P Jpackage
- support for building an I2P Jpackage has been added to the build system
Note that support is platform-specific, to build a Windows jpackage one must
use a Windows OS, to build a Linux jpackage one must use a Linux OS. Only
Windows jpackages are used for a release product. - For information about how releases are built see README.md and UPDATES.md
- The jpackaged router has the following differences from mainline I2P:
- The jars are installed to a different directory.
- The native libraries are installed to a different directory
- The wrapper script is not installed and not used, and replaced by the
browser launcher. - The I2P executable is %programfiles%/I2P/I2P.exe, command-line flags are not
compatible but configuration files are. - wrapper.config is unused
- The built-by entry will reflect that idk built the package
- Use flags to achieve compatibility with plugins that use Reflection on Java
17 jpackages
2021-01-17 idk
- Use Local Application Data instead of Roaming application data for router.config file
- Use Roaming Application Daya only if a clients.config.d is present, indicating that the
roaming application directory is in use deliberately.
2020-12-20 idk
- Add I2P in Private Browsing plugin, which for the purposes of this profile provides
- X-I2P-Location functionality(Alternate service locations for mirrors)
- X-I2P-TorrentLocation functionality(Alternate resource locations for sites)
- Pre-Disable HTTPS only mode dom.security.https_only_mode=false in the profile in favor of HTTPS-Everywhere
- Enable the use of extensions in private mode by default.
2019-02-10 zab
- Fix missing texts on Finish page
2019-02-09 zab
- Enable js on the console and disable everywhere else
- Newer versions of plugins
- Bump profile version to 0.2
- Move I2P detection to happen before any files are written
- Update I2P detection to detect "zero" installer as well
- Bump installer version to 0.02a
2019-01-08 zab
- Rename the output of the windows installer to include version.
- current (initial) version is 0.01a
- Change text in prompts for Firefox and I2P locations
- check 32-bit location even if install should have been 64-bit
- use a Toopie as icon
- Add la...
