The Invisible Internet Project

--Stolen and reposted here, sorry zab, but I hope you're fine with some extra promotion--

Hi,

[...]

After about a year off MuWire is back to the land of the living and the network has ~50 active users at any given time. Here is how to set it up and connect:

1. Go to the GitHub release page

2. Download the connections.txt file and save it somewhere

3. Depending on your operating system:

On Windows, download the MuWire-0.8.14-beta2.exe installer and run it. It will install everything you need to run MuWire. Skip to step 5.

On Linux, you need to install Java 17 or newer. This will be different on each distribution

On Mac, you need to install Java from [here] (https://jdk.java.net/22/) (available for both Intel and Apple Silicon).

4. Download the [MuWire-0.8.14-beta2.zip] (http://muwire-0.8.14-beta2.zip/) file and unzip it. Run the bin/MuWire script to launch MuWire.

5. Go through the MuWire setup wizard. When the main window appears, select Connections (top-left menu) -> Import connections and select the connections.txt file you saved in step 1.

Watch the bottom right of the main window - there is an icon like a molecule with the number of active connections to the MuWire network. As soon as MuWire connects, you can use it to search, share, download, message other users and more.

Enjoy!

zab_

[2.53.0] - 2024-07-19

Added

• New congestion control algorithm for streaming
• Support miniupnp-2.2.8
• Limit stream's outbound speed
• Flood to next day closest floodfills before UTC midnight
• Recognize duplicated routers and bypass them
• Random SSU2 resend interval

Changed

• Set minimal version to 0.9.69 for floodfills and 0.9.58 for client tunnels
• Removed openssl 1.0.2 support
• Move unsent I2NP messages to the new session if replaced
• Use mt19937 RNG instead rand()
• Update router's congestion caps before initial publishing
• Don't try introducer with invalid address
• Select newest introducers to publish
• Don't request relay tag for every session if we have enough introducers
• Update timestamp for non-reachable or hidden router
• Reset streaming routing path if duplicated SYN received
• Update LeaseSet if inbound tunnel failed
• Reseeds list

Fixed

• Crash when a destination gets terminated
• Expired offline signature upon destination creation
• Race condition between local RouterInfo buffer creation and sending it through the transports

This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.

Newer routers will be favored when selecting floodfill routers. I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes. Legacy transport protocols are being removed, simplifying the code in the UDP transports. Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability. Additional tweaks were made to peer selection strategies.

I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked. We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit. If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each. Non-exit relays and Tor clients are unaffected by this and do not need to change anything.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

RELEASE DETAILS Changes

• Router: Increase minimum version for floodfill routers

• Router: Disable I2P over Tor

• Address Book: Cache locally hosted destinations

Bug Fixes

• I2PSnark: Peer Exchange Tweaks

• I2PSnark: Bugfixes

• Router: Peer Selection Tweaks

Other

• Translation updates

From the maintainer "alreadyburnt" on reddit.

Before we begin: Snap(and AppImages) are still not official packages. This still an experimental package and just a side-project of mine.

A few years ago, I got way too interested in these semi-novel packaging systems that the various distributions came out with. I went on a rampage of experimental package creation, often without necessarily knowing the future of the packages themselves. Many versions ago, the most popular of those packages broke in a particu`larly annoying way, and I did not have time to fix it. Until a few weeks ago, that is, and now, it's actually a lot easier for me to be sure that what I'm packaging is going to actually work because I can generate and test the packages continuously.

TL:DR the Snap, which I created, then broke, is now fixed, and it's likely to stay that way. If you are a snap user stuck on an old version, update as soon as possible.

It is generated using jpackage combined with the Easy-Install source. As a package, it functions like the Easy-Install bundle and not like the .deb or .jar installers.

https://snapcraft.io/i2pi2p

What's the real point? Nobody really cares about Snapcraft that much, except maybe Canonical. A lot of people don't even like them. That's not why there's a Snap of I2P now. The reason there's a Snap of I2P now, and that this experiment was not discontinued outright, is because it demonstrates the power of jpackage, the technology underlying the Easy-Install Bundles for Windows, to generate self-contained images that can easily be adapted to Linux package formats. Once you can stick a jpackage inside a Snap, you can just as easily stick it inside of an AppImage. A slightly different manifest format will leave you with a working Flatpak. The same applies to docker-compose and probably many other tools. Or, you can just stick it all into a .zip file and treat it like an I2P portable installation. The files your packaging are always the same, and are simply generated by jpackageing a custom I2P router launcher.

For more information, see:

https://snapcraft.io/i2pi2p

https://github.com/eyedeekay/I2P-Snaps-and-Appimages/

Picked up from the other site. I'm not the dev of this.

Any feedback is welcome, source: https://github.com/umutcamliyurt/I2Proxy

On Windows, installing I2P is easy.

On Linux... not so much. That's because Linux isn't Linux. There's a Debian package, but OpenSuse is its own thing. Is there a way to get I2P, Snark, etc. up and running there without having to jump through too many hoops?

I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

RELEASE DETAILS

Changes

• Console: Update rrd4j to 3.9.1-preview
• Router: Publish G cap if symmetric natted

Bug Fixes

• i2ptunnel: Fix bug causing truncation of some HTTP content
• i2ptunnel: Fix custom option form width (light theme)
• Tunnels: Fix selection of peers with expired RIs

Other

• Translation updates

[2.52.0] - 2024-05-12

Added

• Separate threads for persisting RouterInfos and profiles to disk
• Give preference to address with direct connection
• Exclude addresses with incorrect static or intro key
• Avoid two firewalled routers in the row in tunnel
• Drop unsolicited database search replies

Changed

• Increase number of hashes to 16 in exploratory lookup reply
• Reduce number of a RouterInfo lookup attempts to 5
• Reset stream RTO if outbound tunnel was changed
• Insert previously excluded floodfill back when successfully connected
• Increase maximum stream resend attempts to 9
• Reply to exploratory lookups with only confirmed routers if low tunnel build rate
• Don't accept too old RouterInfo
• Build client tunnels through confirmed routers only if low tunnel build rate
• Manage netDb requests more frequently
• Don't reply with closer than us only floodfills for lookup

Fixed

• Crash on router lookup if exploratory pool is not ready
• Race condition in excluded peers for next lookup
• Excessive number of lookups for same destination
• Race condition with transport peers during shutdown
• Corrupted RouterInfo files

Some projects have been DMCA'ed and hosting them on I2P could be a viable alternative.

I2P 2.5.1 is being released to address Denial-of-Service Attacks affecting the I2P network and services. With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack. This should help the network return to normal operation. Those of you who have disabled the Sybil attack detection tool may safely re-enable it. Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I'm looking to try out i2p but I'm having trouble getting it going.

I have a docker-compose container going with this docker-compose.yml:

version: "3.5"
services:
    i2p:
        image: geti2p/i2p
        ports:
            - 4444:4444
            - 127.0.0.1:6668:6668
            - 7657:7657
            - 54321:12345
            - 54321:12345/udp
        volumes:
            - ./i2pconfig:/i2p/.i2p
            - ./i2ptorrents:/i2psnark
        restart: always
        environment:
            - IP_ADDR=0.0.0.0
            - JVM_XMX=1024m

The container starts up and the log outputs:

$ docker logs i2p-i2p-1 
Starting I2P
[startapp] Running in container
[startapp] setting reachable IP to container IP 0.0.0.0
Starting I2P 2.4.0-0

But when I try to access the console, I'm seeing:

$ curl localhost:7657
curl: (56) Recv failure: Connection reset by peer

Is there anything else that I need to do here?

The I2P network is currently under a Denial-of-Service attack. This attack affects I2P and i2pd but in different ways and is having a serious effect on network health. Reachability of I2P sites is badly degraded.

Java I2P users are suggested to disable the sybil attack tool, delete the sybil-blocklist, and re-start their routers.

To disable the sybil attack detector tool

Open the sybil attack detector in your router console at http://127.0.0.1:7657/netdb?f=3&m=15

Change "Background Analysis Run Frequency" to "Never"

Click "Save" to save the settings.

To delete the sybil blocklist, run:

On Debian and Ubuntu:

rm "/var/lib/i2p/i2p-config/sybil-analysis/blocklist-sybil.txt"

On other Linuxes and on Mac OSX:

rm "$HOME/.i2p/sybil-analysis/blocklist-sybil.txt"

And on Windows:

del %LocalAppData%\i2p\sybil-analysis\blocklist-sybil.txt"

When you are finished, re-start your I2P router.

If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability. Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.

zzz has posted the following update:

"I2P network reliability is currently degraded due to a novel and persistent attack. Please be patient as we work on mitigations. If you have not yet updated to the latest release 2.5.0, please do so as it provides some defences."

For i2pd users, you can try building their latest from GitHub which may help.

I host i2p on a rpi 3 in order to use it as a mutualize gateway for my private network. i2p consume so much ressources that I couldn't even curl it's web interfaces. It try to get some info on what are the hardware requirements, but didn't find anything.

• What are the minimal hardware requirements for the current version of i2p ?
• Is it a good idea to mutualise a gateway on a private server ?
• If so, is it a good idea to give access to this gateway through a VPN ?

Thanks for your answers

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.firefox and 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.firefox project 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.firefox updates are signed in their .su3 form. The NSIS-powered .exe installer 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.

Anyone know how to switch browser in i2p mobile? I opted for the built in one, but it's kind of limited and I can't seem to change it. I have Firefox installed but can't select it as the default.

https://files.catbox.moe/cnhm5n.png

https://files.catbox.moe/fahyd1.png

https://files.catbox.moe/n0krr2.png

https://files.catbox.moe/uxw472.png

https://files.catbox.moe/xeoef1.png

https://files.catbox.moe/5y043e.png

https://files.catbox.moe/45ju8a.png

https://files.catbox.moe/qaezsx.png

Check the tutorial in my blog!

Borrowed from that other site.

Someone's managed to somewhat revive MuWire, the anonymous filesharing app.

It can be downloaded from within i2p or you can get it here: https://ufile.io/y1uecxev

As always, be careful with unknown binaries. I take no responsibility for the files or what you do with them.

From IDK.

After the very challenging 2.3.0 and 2.4.0 release cycles we're going to have a long release cycle this time, targeting an April release. This release will feature performance improvements and new application features.

To keep track of newly merged features, follow along at: https://git.idk.i2p/i2p-hackers/i2p.i2p/-/merge_requests?scope=all&state=merged&milestone_title=2.5.0

• Target Release Date: April 29, 2024.
• Major Changes Due Date: March 31, 2024
• Tag Freeze Date: December April 11, 2023

If you want to run the code I am (Usually) running, use the master branch from git.

Hello all!

So i would like to increase my upload bandwidth of i2psnark but it doesn't let me go beyond 9.999. I have a 500/500 fiber connection with no cap and like to share bit more then only the 9.999 KBs.

EDIT: I manage to solve it thanks to sopuli.xyz

I changed the i2psnark.upbw.max ration inside ~/local/share/containers/storage/volumes/i2p_i2phome/_data/i2psnark.config.d/i2psnark.config"

the perhaps odd file locations is due to me using podman in rootles mode