** Changed in: nginx (Ubuntu Bionic)
Status: Incomplete => Invalid
** Changed in: nginx (Ubuntu)
Status: Incomplete => Invalid
** Changed in: openssl (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: openssl (Ubuntu)
Status: New => Invalid
--
You received t
Looks like the update to 1.1.1-1ubuntu2.1~18.04.4 resolved the issue!
The listed failing tests above are now passing.
I don't see a way I can close out an issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubun
** Changed in: nginx (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833476
Title:
libssl1.1 version 1.1.1-1ubuntu2.1~18.0
** Also affects: openssl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl i
Could you try if the followup SRU made a difference there?
https://bugs.launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.3
** Tags added: regression-update
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
After upgrade to OpenSSL 1.1.1 I get this err_ssl_version_interference error in
chrome.
running nginx -V I got this:
nginx -V
nginx version: nginx/1.14.0 (Ubuntu)
built with OpenSSL 1.1.0g 2 Nov 2017 (running with OpenSSL 1.1.1 11 Sep 2018)
TLS SNI support enabled
so I don't kn
Another thing to mention is that the new failures are all due to the
same error as in the previous comment. It seems like the failing tests
all expect the session to be reused, and fails.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
I did not do anything special outside of the steps in my repro to
specifically enable SSL in the nginx configs, but should that matter in
terms of running these SSL tests? With the Dockerfile in the description
as it is, I can already see in the test output that SSL tests are
running and succeeding
This sounds more like an OpenSSL issue than an NGINX one. Until such
investigations are complete to confirm this and rule out NGINX as the
problem, I am marking this as 'Incomplete' in NGINX in Ubuntu.
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
--
You received this bug notif
Default nginx configurations **in Ubuntu** do not enable SSL by default.
Have you passed an SSL enabled config to your docker container first?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.lau
** Also affects: nginx (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833476
Title:
libssl1.1 version 1.1.1-1ubuntu2.
11 matches
Mail list logo