-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.
- --
PageKite.n
-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
On 2018-11-28 21:25:45 [+0100], Petter Reinholdtsen wrote:
> The upgrade from openssl version 1.1.0h-4 to 1.1.1-1 break pagekite on
> the FreedomBox. After a debug session with the pagekite author I
> discovered the reason is changes in /etc/ssl/openssl.cfg, which now
> block connection to the pag
Package: pagekite
Version: 0.5.9.3-2
Severity: important
X-Debbugs-CC: Debian OpenSSL Team ,
FreedomBox packaging team
The upgrade from openssl version 1.1.0h-4 to 1.1.1-1 break pagekite on
the FreedomBox. After a debug session with the pagekite author I
discovered the reason is changes in /e
4 matches
Mail list logo