Recent comments

j8810kkw wrote (edited by a moderator )

I don't know about that part, I think that though they may be good for the household they're not good for things in the industrial scale (which is also my concern). And that part about the poisonous stuff? I think I'll do some research on it and bring back what I can find. Thanks though for bringing up the topic.

1

invertedlurker OP wrote

So I'm coming back, and I actually figured it out. Somehow, there was an instance of I2Pd that was set to run on startup with root privileges. "sudo lsof -i:4444" was what it took to find it. because I didn't think about using lsof with sudo. I killed that instance and also uninstalled I2Pd, to not have problems like that again, and because I never use it anyways. Yeah, you're right.

2

invertedlurker OP wrote (edited )

It never was disabled in the first place. But I added all these outproxies as you suggested. Still nothing. geez I wish I could show you pictures to make sure I'm not doing it wrong.

(also why is the title of every failed access "I2Pd HTTP proxy" ? I'm not using it as far as I know)

By the way here are the startup logs of the tunnel. Port 4444 fails, that might be why

<div>
• Client ready ➜ Listening on 127.0.0.1:7659
• Tunnels ready for client [Standard client on 127.0.0.1:7659]
• Client ready ➜ Listening on 127.0.0.1:4445
• Tunnels ready for client [HTTPS Proxy on 127.0.0.1:4445]
• Client ready ➜ Listening on 127.0.0.1:7660
• Tunnels ready for client [Standard client on 127.0.0.1:7660]
• Stopping client IRC Client on 127.0.0.1:6668…
• Error listening for connections on /127.0.0.1 port 6668: java.net.BindException: Address already used
• Stopping client HTTP Proxy on 127.0.0.1:4444…
• Error listening for connections on /127.0.0.1 port 4444: java.net.BindException: Address already used
</div>

Translated from French because even though I set English, network errors are in my language.

1

z3d wrote

If you disabled the default configured outproxy in your HTTP Proxy Client tunnel, you won't be able to access clearnet or .onion sites. In your HTTP Proxy tunnel, restore the purokishi.i2p outproxy for HTTP and HTTPS if you wish to access .onion sites over .i2p. You can configure multiple outproxies if you want some random variation, e.g. purokishi.i2p,exit.stormycloud.i2p,outproxy.acetone.i2p.

2

fintere_934fintere wrote

Politically, cyberattacks have become a fundamental part of modern conflicts, targeting sensitive objectives in a strategic manner. China’s cyber offensive against the US is not solely about advanced technology, but largely driven by the desire to spy and monitor matters that might seem minor yet hold significant importance in the context of influence and control .

1

Yolli wrote

Reply to Soothing GIF by Wahaha

Whenever the Tesseract turns inside out my mind blows. How could one create such an animation in 3D modeling programs? Perhaps code is needed.

1

Yolli wrote

Reply to Meet Alice by not_bob

Do these ai image generators include watermarks in the images that can be used to identify the user who created it?

1

Yolli wrote

For reading rss feeds there exists also the desktop application thunderbird. Configuring the network settings in thunderbird under manual proxy configuration / http proxy worked for me. Entering into 2 text fields {!ip-address of your i2p node in local network!} port number of http-proxy (4444 for example) worked. I do not know about other rss feed readers.

1

guidry wrote

i saw online read only phone once, or VOIP swap number possibility. but maybe we can also share fake account. Would need some for a cloud GPU PAAS project using google collab as a showcase

1

cumlord OP wrote

it's the same thing notbob is doing from notbobs post wrote about it some here:

encrypted leaseset for stuff you don't want found and making sure auth is enabled with the biglybt webui are the best ways (or disabling the webui)

any leaseset is stored in the netdb, and the netdb is stored by floodfills. if you run a floodfill you can watch the leasesets come in from peers and try them with a scanning tool. in practice and even with only a router or 2 designated for this you can scan a majority of the steadily available content in i2p that isn't registered within a week or 2 probably

1

cumlord wrote (edited )

if you have any server tunnel that you want to be accessible publicly as a service it will be picked up like this. for stuff you don't want to be public to the network, you have some options:

  • encrypted leasesets
  • whitelist a list of b32s
  • dummy content on port 80 with the "real" thing on a random port
  • auth
2