On Saturday, February 14th, 2026 at 4:28 PM, David Uhden Collado <[email protected]> wrote:
> Hello, > > Please find attached a patch that updates the net/i2pd port to version > 2.59.0. > > The upstream release notes and full list of changes are available at: > > https://github.com/PurpleI2P/i2pd/releases/tag/2.59.0 > > In addition to the version bump, I have included several adjustments > that both the maintainer and I previously discussed in another thread on > this mailing list. That discussion is available at: > > https://marc.info/?t=176780204200003&r=1&w=2 > > I would also like to ask whether it might be possible to improve > compatibility with LibreSSL. A new API for ML-KEM was recently > introduced, and i2pd currently enables this post-quantum encryption > algorithm only when built against OpenSSL. It seems that adding support > for LibreSSL may now be feasible. > > Additionally, there are several other features in i2pd that are > currently disabled when building with LibreSSL because it was previously > assumed that equivalent functionality could not be implemented. It may > be worth revisiting some of these areas to determine whether support > could now be added. > > Thank you for your time and consideration. > > Best regards, > David. Hi, Thank you David. I'm testing since a few days a patch very similar to yours (with only minor differences), but there are problems and I'm not sure how to address them properly. First, this patch introduces breaking changes for existing i2pd installations. Upgrading from a previously installed router is not straightforward, since the _i2pd user has now a new home directory (/var/i2pd). If this user is not recreated, i2pd will somehow "insist" on writing files to the old directory (/var/lib/i2pd) and crash. The content of the old directory must be moved to the new one, otherwise B32 addresses are lost. And also, for users who configured i2pd to write logs to a separate file (like I am), newsyslog.conf must be adapted. Here's the upgrade procedure I came up with : - stop i2pd gracefully - remove the old package - delete the _i2pd user and group - move /var/lib/i2pd to /var/i2pd - rmdir /var/lib - install the new package - edit /etc/i2pd/i2pd.conf - (optional) edit /etc/newsyslog.conf - restart i2pd I guess this should be documented in the README, at least until the old port is not supported anymore, in other words until 7.8 is phased out? Secondly, deleting the _i2pd user and group, and letting the i2pd port recreate them, ends up giving ownership of the whole /var directory to _i2pd:_i2pd . I could not figure out how that happens, or what's wrong with the PLIST... I hope we'll be able to update the port soon, since this new release of i2pd partially mitigates an ongoing DDoS/Sybil attack disrupting the I2P network. FYI this new attack may be the result of a botnet operator's incompetence: https://krebsonsecurity.com/2026/02/kimwolf-botnet-swamps-anonymity-network-i2p/ . Best regards.
