openbsd@systemfailure.net wrote:
>
> 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.
>
I don't know why, but your email has not been forwarded to the mailing
list even though you sent it. Anyway, it's up there for anyone who wants
to read it.
I don't think this is a problem for the maintainer to take care of.
Rather, it is a problem for OpenBSD's package management tools, which do
not handle these changes to ports correctly. The tools should detect and
apply these changes while keeping the old configuration files and
renaming them *.old-pkg, allowing the system administrator to adapt
their old configuration to the new one. I wouldn't worry about it. I
would apply the update as is.
On another note, I think it would be beneficial to port i2pd-tools to
OpenBSD. It's inconvenient to have to use Linux every time I need to
generate authentication strings for registrants.
https://github.com/purplei2p/i2pd-tools
No comments:
Post a Comment