Reasonably secure I2P setups

How to use I2P in a reasonably secure way? Installing it in Qubes, Whonix, and Tails seems very hard. The nature of such setups being so 'experimental' introduces risk, too. I am beginning to think I2P is just still not ready and there is no way to use it without high risk. Even the basic installation process for anything other than Windows seems like a pathetically bad user experience. Reddit is full of people just installing on their main daily driver Windows machine and going to illegal sites. Absolute insanity.

>>20849 My setup. >VM >Generic GNU/Linux distro that isn't Ubuntu. >Librewolf >Download I2P java package over tor >Launch the jar file >Go setup the proxy in Librewolf >Go the the router address in Librewolf >Configure the router And you are basically done. You don't have to run a VPN. Because that would also make it less decentralized in the sense of that you then rely on a VPN provider, which you don't need. Maybe if you are real paranoid you can also disable JS, but don't worry too much about it. People are always scared about the P2P nature of it, but the peers and seeders and yourself have no control over what is being sent because it is encrypted. Of course technically speaking you are kinda processing all the spicy stuff over your computer, but you don't know the details and the feds also don't. Also encrypt your SSD, that's just a general thing you should do, because the cops need a extra warrant to force you to decrypt your stuff.... you can also hide your stuff with veracrypt like SSH and PGP keys and such. I would also back that up with a SD card.

It's not hard to install in Whonix, I tried it once but it's pointless to use i2p in Whonix in my opinion.

>>20849 >I am beginning to think I2P is just still not ready and there is no way to use it without high risk. what security flaws have you found so far ? It seems to be less vulnerable to DDoS attacks at least

>Installing it in Qubes, Whonix, and Tails seems very hard. What about you actually try it before making a thread about it? It's not.

>>20854 I spent days trying. In Qubes I followed multiple guides/instructions and couldnt get it to work. Tried just making a debian VM, just doesnt work baed on 'official' instructions. Saw someone write vaguely that they made some sort of port-forwarded tunnel, but they used tools that are now discontinued and again i couldnt figure out how to do it. Whonix guide leads to a forum post of developers saying it doesnt work and they are still looking for people to help. All the inproxies I find are even down. It's at the point where I would have to do trial and error based on random forum posts without really understanding the details of what I am doing. Obviously is risky so i dont achieve the sense of safety that i seek that way. If it's so easy then fuarrrking share the information

>>20849 I've put i2pd on a separate account on a VPS. I use OpenVPN to connect to the HTTP proxy (I already had it for other stuff, don't recommend it) though SSH tunneling should work too. Putting it on your desktop or whatever is just fine too of course, just beware of potentially high bandwidth if you have a soykafty ISP. Read https://i2pd.readthedocs.io/en/latest/devs/building/unix/ and https://i2pd.readthedocs.io/en/latest/user-guide/run/. It's pretty easy (especially compared to the Java version, I didn't manage to build that one from scratch). I currently have a custom Firefox profile to connect to i2p (JS disabled, letterboxing etc). I intend to setup a Tails VM eventually, not sure how hard it would be.

>>20853 Here is a paper about possible attacks on the network. Enjoy.

>>20849 Besides torrenting (slowly) I don't see a reason to use i2p. It was fun, but I will be replacing it with a paid vpn.