like, if I can't update the client code, then it's just not going to work
I'm not sure if that is it, but since this was a recent issue I thought it might be relevant
yeah, you have to move to OpenSSL 1.1.0 or greater, so good luck with ubuntu 16.04 or python2, pypy2
LarstiQ: this is pretty horrendous
fijal: well, also CA certs expire, there isn't really a way around that?
they should get a new one no?
the point is that they are relying on their self-signed cert that was introduced to a lot of software
that's a bit dodgy, IMO
well a root cert expired and some software wasn't prepared for that (and as I understand that article their recommond setup is to send two chains one with the expired root cert and a second with a valid root cert for compatibility with some android versions as they keep trusting that root cert for some reason and don't trust the new root cert, but that doesn't works with openssl 1.0.* as it sees the
first invalid chain and just fails instead of looking at the second chain, which would be valid)
Julian has joined #pypy
fijal, every root CA is self-signed, right?
jkovac11 has joined #pypy
jkovac1 has quit [Ping timeout: 264 seconds]
jkovac11 is now known as jkovac1
jacob22 has quit [Quit: Konversation terminated!]
Atque has joined #pypy
looks like there's some bug in the VFP detection on 32bit ARM in pypy3.7 7.3.6rc2