On Wednesday, January 7th, 2026 at 3:18 PM, David Uhden Collado <[email protected]> wrote:
> Hello all, > > Attached to this email is a patch that includes one fix and several > improvements for the net/i2pd port. IMHO, the changes you are proposing are mostly a matter of personal preference. I see no sufficient reason to deviate from upstream configuration choices, which are are kind of the default way of configuring i2pd, and also what most users are expecting. > First, the patch addresses an issue related to log handling. By default, > i2pd uses a separate log file located at /var/log/i2pd/i2pd.log. > However, this file is not rotated by newsyslog(8), causing it to grow > without bounds. The proposed solution is to configure i2pd to write its > logs to /var/log/daemon by updating the i2pd.conf configuration file. I personally like to have a separate log file for i2pd, and not mix its output with other things. That's a matter of taste, and anyway log rotation can be configured in /etc/newsyslog.conf . > Second, the directory used to store port-related files changes from > /var/lib/i2pd to /var/i2pd, which better aligns with the OpenBSD style. > To accomplish this change, the patch updates the PLIST, the RC script, > and the i2pd.conf configuration file. It is true that /var/i2pd would "better align with the OpenBSD style", but apart from that stylistic issue, what's wrong with /var/lib/i2pd ? Using this directory does not prevent i2pd from running fine on OpenBSD, and it is referenced by all guides and tutorials on i2pd, so changing it could confuse new users. I don't think it would be worth introducing a lot of changes in the PLIST, rc script and default config file. > Finally, the i2pd.conf and tunnels.conf configuration files are adjusted > to improve security and usability. Specifically, the web interface and > the default IRC tunnel are disabled, log verbosity is reduced, and > additional address book sources for I2P aliases are configured. That's also a matter of personal choice. I personally use the web interface, which is a very convenient way to interact with your daemon, and I guess that a lot of users are also expecting it to work. Security-wise, it's not too bad as long as you don't expose it publicly on the internet. If you don't like it, you're free to disable it in the configuration file. The same applies for the IRC tunnel, log verbosity, etc. I guess most i2pd users are editing i2pd.conf and tunnels.conf anyway. I don't use the IRC tunnel either, but I've always seen this configuration snippet as an example provided by the developers to demonstrate how to configure tunnels. > I look forward to any feedback or suggestions. At the end of the day, I think that porters should not set their personal configuration preferences as the default for all users; we should stick to upstream's choices as long as they're working under OpenBSD and don't introduce unnecessary risks. Moreover, i2pd's configuration is documented and the users can decide for themselves what's good for their use case. > Best regards, > David.
