[PR #2919] [MERGED] Profiles: add I2P #4583

New issue

Closed

opened 2026-05-05 10:22:51 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:22:51 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/2919
Author: @corecontingency
Created: 8/21/2019
Status: ✅ Merged
Merged: 8/21/2019
Merged by: @rusty-snake

Base: master ← Head: master

📝 Commits (4)

7b96833 profiles: add i2p
09d110a Apply suggestions from code review
bd470dc Applied further suggestions from code review
d3c510b added i2prouter to firecfg

📊 Changes

3 files changed (+76 additions, -0 deletions)

View changed files

📝 etc/disable-programs.inc (+4 -0)
➕ etc/i2prouter.profile (+71 -0)
📝 src/firecfg/firecfg.config (+1 -0)

📄 Description

Added an I2P profile.

This was tested with Arch/KDE, installing I2P using the official distro-independent java installer and Xubuntu, installing I2P using the official PPA.

This does not support the AUR packages for I2P, as they install it really funky and require root privileges to run I2P. Didn't see the point of supporting that when there is an official distro-independent java installer, that only requires normal user privileges to run I2P.

Was not able to create a private-bin for I2P, unfortunately. I'm sure it is possible, but it uses a java wrapper shell script to start I2P, and I thought I copied all the necessary binaries to get it running, but no luck. Are there some debugging tools for firejail that simplifies the process of creating a private-bin?

By default, after starting up I2P opens your default browser to the I2P router console at http://127.0.0.1:7657/home. I couldn't get this to work, so currently it just shows some error messages that it can't open the browser. Luckily, this can be turned off in the I2P settings. I don't think it is that much of an inconvenience to manually open your browser and go to http://127.0.0.1:7657/home instead.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/2919 **Author:** [@corecontingency](https://github.com/corecontingency) **Created:** 8/21/2019 **Status:** ✅ Merged **Merged:** 8/21/2019 **Merged by:** [@rusty-snake](https://github.com/rusty-snake) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (4) - [`7b96833`](https://github.com/netblue30/firejail/commit/7b968332937ca451016262947463924f847a159b) profiles: add i2p - [`09d110a`](https://github.com/netblue30/firejail/commit/09d110a8e2e986a725f2d3bd2fb807afb954f929) Apply suggestions from code review - [`bd470dc`](https://github.com/netblue30/firejail/commit/bd470dccbc5d5ab41fde0246dbddd565134aa03b) Applied further suggestions from code review - [`d3c510b`](https://github.com/netblue30/firejail/commit/d3c510b167e3df9f7c587f47f5f0c6071f432772) added i2prouter to firecfg ### 📊 Changes **3 files changed** (+76 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `etc/disable-programs.inc` (+4 -0) ➕ `etc/i2prouter.profile` (+71 -0) 📝 `src/firecfg/firecfg.config` (+1 -0) </details> ### 📄 Description Added an I2P profile. This was tested with Arch/KDE, installing I2P using the official distro-independent java installer and Xubuntu, installing I2P using the official PPA. This does not support the AUR packages for I2P, as they install it really funky and require root privileges to run I2P. Didn't see the point of supporting that when there is an official distro-independent java installer, that only requires normal user privileges to run I2P. Was not able to create a private-bin for I2P, unfortunately. I'm sure it is possible, but it uses a java wrapper shell script to start I2P, and I thought I copied all the necessary binaries to get it running, but no luck. Are there some debugging tools for firejail that simplifies the process of creating a private-bin? By default, after starting up I2P opens your default browser to the I2P router console at http://127.0.0.1:7657/home. I couldn't get this to work, so currently it just shows some error messages that it can't open the browser. Luckily, this can be turned off in the I2P settings. I don't think it is that much of an inconvenience to manually open your browser and go to http://127.0.0.1:7657/home instead. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>