PSA: git.idk.i2p will be switching to HTTPS in order to resolve issues with gitlab

Release Announcements
Post Reply
User avatar
eyedeekay
Posts: 75
Joined: 21 Jul 2018 06:53

PSA: git.idk.i2p will be switching to HTTPS in order to resolve issues with gitlab

Post by eyedeekay »

In order to resolve issues in the way gitlab handles HTTPS and WebSockets connections, git.idk.i2p will switch to HTTPS with a self-signed certificate. I believe this is essentially unavoidable with gitlab. This will require users to import the self-signed certificate into their I2P browser. It is highly recommended by the gitlab admin, me, that you do this with an I2P-only browser, not a browser used for clearnet navigation.

For verification, the fingerprint of the certificate is:

Code: Select all

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

SHA256 Fingerprint=09:B4:67:10:A7:5E:89:F1:5B:08:BB:BF:BD:E4:F9:30:CB:9C:27:CD:62:EF:E0:C5:0B:99:AC:F8:69:FC:41:82
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEcNIGBzi++AUjrK/311wDs5teFOEFAmVtIukACgkQ11wDs5te
FOFLgwgAmpSRrqxsp3x4u/Aijt7mFtMv51ZUrA3HOan73HGl3U8GjRpmZxIsJ8Dq
IMLqfT/noIEN4/B36zAJa/E+rBssefgkx+7f8uK+w/mNdBX8rMuSYQnlShAof4Hc
+eUnV42Hc+LMFDx9Tb4QtF7OmxQXUjir1lsNxpRJngeGI3vDAVcv+uzBzKUTu4os
UOswLYZ4j98sM9Q5U1Jii36a5KAEOWZ32peKISjeQPDU49sW30Lb3Nla5aZjM6g5
enAzCSwu5X7vh1MT1aRQVl2muGl3o0IylnhhLDyNNbFjKrC9bvgk93YsMWVKqgkH
Oo4v5xeoKW60jDqOj4K7HwiP5TjiKg==
=1zw1
-----END PGP SIGNATURE-----
This transition will occur in 2 days. It is not expected to incur much downtime but gitlab service will be momentarily interrupted.
User avatar
eyedeekay
Posts: 75
Joined: 21 Jul 2018 06:53

Re: PSA: git.idk.i2p will be switching to HTTPS in order to resolve issues with gitlab

Post by eyedeekay »

HTTPS is up and running. HTTP will continue to work but users are advised to switch to HTTPS if they are having issues with gitlab features not working, false-positive errors, websocket issues, etc.
Post Reply