@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BravoOreo
BubbRubb
Chrono
Daddy
Danny
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest5036
Irc2PGuest59861
Irc2PGuest63688
Onn4l7h
Onn4|7h
Over
Rogueone
Sisyphus
Sleepy
St1nt
T3s|4_
Teeed
aargh
aisle
ardu
b3t4f4c3___
cumlord
dr4wd3
duanin2
eyedeekay_bnc
nilbog-
not_bob_afk
ohThuku1
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
wew
x74a6
zzz
eyedeekay, gitlab web+ssh dead
eyedeekay
Gitlab's back again, running into storage issues with my VPS
eyedeekay
Today's the deadline day I posted on the forum, I'm going to be up at midnight tonight so midnight is the deadline
zzz
thanks eyedeekay
zzz
also, monthly request, please fix and close your tickets
zzz
in particular please renew your 1-year plugin cert before the release
eyedeekay
Ack I'll do the plugin cert and close the remaining closables today
zzz
ok make sure you renew it, don't create a new key
eyedeekay
I *should* be able to do that now that my key library is fixed, I'll make sure before I check it in
zzz
ok, if the privkey is in a java keystore we have a java CLI for renewal, I can give it to you if you need it, otherwise you're on your own
eyedeekay
It's in a Java keystore but I implemented a Java keystore library in Go which is how I ended up accidentally blowing away my old keys and with a wrong expiration date on the new ones, both were bugs
zzz
interesting. be aware that the java keystore format has changed a couple times, used to be custom but now is some PKCS standard, depends on java version and who knows what
zzz
good practice, check all certs with certtool -i before checking in
eyedeekay
Will do thanks zzz :)