-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Oh shoot, I just noticed this bug is filed against the pagekite
package, not against openssl. The pagekite maintainers obviously
cannot fix the issues I was ranting about in my previous message,
please accept my apologies for noise.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello!
Thanks Petter, for reporting this and helping me debug it today.
I can confirm that just allowing TLSv1 would allow connections to
the existing PageKite infrastructure. Upgrading the server in
question is increasingly becoming a priority for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello folks,
I wanted to register a voice of dissent here. I don't think
"embarrassment" justifies breaking people's working and valid
certificates in this way.
This is only barely a security issue - StartCom and WoSign were
being punished for not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sebastian,
My problem was just Pound - I'm just a user when it comes to
these tools.
I do not know how widespread this problem is or how common it is
for projects to use openssl dhparam -C during their build process
(as opposed to running it once
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello! Note that this bug has been fixed upstream and new
releases made to fix this and other bugs. :-)
Cheers,
- Bjarni
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBAgAGBQJWJi7dAAoJEI4ANxYAz5SRdzwH/i3rME/acFIlwWoxHUhY+eUp
5 matches
Mail list logo
