git.i2pd.i2p SSL_ERROR_RX_RECORD_TOO_LONG

[lgillis]

https://git.i2pd.i2p/ SSL_ERROR_RX_RECORD_TOO_LONG

#+begin_quote Firefox 135.0.1
Fehler: Gesicherte Verbindung fehlgeschlagen

Beim Verbinden mit git.i2pd.i2p trat ein Fehler auf. SSL hat einen Eintrag erhalten, der die maximal erlaubte Länge überschritten hat.

Fehlercode: SSL_ERROR_RX_RECORD_TOO_LONG

Die Website kann nicht angezeigt werden, da die Authentizität der erhaltenen Daten nicht verifiziert werden konnte.
Kontaktieren Sie bitte den Inhaber der Website, um ihn über dieses Problem zu informieren.
#+end_quote

#+begin_quote https://kinsta.com/knowledgebase/ssl_er ... _too_long/
What Causes the “SSL_ERROR_RX_RECORD_TOO_LONG” Error?

From the above screenshot, you can see that this error message gives you a few details about the issue. For example, it mentions that the page you’re trying to view can’t display “because the authenticity of the received data could not be verified.”

It also mentions that the secure connection failed and indicates an issue with the site’s SSL certificate.

This error message may be a result of poor security on the part of the website you’re trying to visit, whether it’s your own or someone else’s. In a nutshell, the most common cause is that the SSL certificate is not properly configured, and your browser is, therefore, unable to complete the connection with the port on the server successfully.

One of the possible causes could be that you have a misconfigured listing port. Another potential reason is that your browser doesn’t currently support an adequate version of Transport Layer Security (TLS). In the past, this used to be a common issue with TLS 1.2; however, in recent years, it seems to be arising with TLS 1.3 as well.
#+end_quote

[zzz]

Can't reproduce via a Java I2P HTTP client proxy (I get a timeout), but this is almost certainly caused by the server not supporting HTTPS, or i2pd serving HTTP over the HTTPS port.

The Java HTTP server proxy handles it differently, if SSL is not configured, it sends a RESET, and firefox will display PR_END_OF_FILE_ERROR instead of SSL_ERROR_RX_RECORD_TOO_LONG

[anikey]

Basically: because you used https, where http should be used instead.

[lgillis]

eww https://git.i2pd.i2p/ Contacting host: git.i2pd.i2p:443, error in process filter: gnutls-error: (gnutls-error git.i2pd.i2p -15)
eww http://git.i2pd.i2p/ Contacting host: git.i2pd.i2p:80 - 502 Bad Gateway (nginx)
Falkon: ERR_SSL_PROTOCOL_ERROR / 502

It doesn't matter because there's nothing I can do about it anyway.

The I2Pd source code, the I2Pd docs and the I2Pd homepage do not mention the above-mentioned I2P addresses anywhere. There is therefore no I2Pd base within I2P. Regardless of who has registered these I2P addresses - whether they are fans or scammers - in my opinion, the only real contact points are all on the Internet.

[anikey]

There's also http://git.community.i2p/PurpleI2P/i2pd.

Or you can go on IRC (or github) and ask the i2pd devs about git.i2pd.i2p.

Edit: I went ahead and asked on github: https://github.com/PurpleI2P/i2pd/discussions/2161

[anikey]

Got an update: https://github.com/PurpleI2P/i2pd/discu ... t-12436232

git.i2pd.i2p is temporary disabled, git.community.i2p/PurpleI2P/i2pd is not official.

[lgillis]

Shouldn't we scoff now and claim that I2Pd's headquarters is GitHup because Microsoft knows a thing or two about Internet security?

Thanks, anikey.

[anikey]

i2pd has their own i2p site (i2pd.i2p), they also have a (russian-language) forum (333.i2p), and they also have their own IRC network. In any case, if someone really needs to get the source somewhere outside of Github, they can go and ask the developers (the devs surely have the source).

[lgillis]

i2pd has their own i2p site (i2pd.i2p), they also have a (russian-language) forum (333.i2p), and they also have their own IRC network. In any case, if someone really needs to get the source somewhere outside of Github, they can go and ask the developers (the devs surely have the source).

https://youtu.be/rm0FA8otEAk