Public bug reported: See the upstream bug background https://github.com/openssl/openssl/issues/1418
The issue initially was caught in a case when developers works behind company firewall and requires install company self signed certificate on Ubuntu host in order to access via company proxy. This is also causing problems for snapcraft developers who work behind proxy servers unable to build snap packages. There is a fix going into openssl upstream apparently https://github.com/openssl/openssl/pull/10587 Just create a bug here to track this issue in Ubuntu in order to make sure we merge upstream fixes ultimately. Similar case reported by other users: [1] https://serverfault.com/questions/966846/cannot-trust-development-https-self-signed-certificate-in-ubuntu-18-04-2-lts [2] https://stackoverflow.com/questions/55485511/how-to-run-dotnet-dev-certs-https-trust/59702094#59702094 ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Description changed: See the upstream bug background https://github.com/openssl/openssl/issues/1418 - - The issue initially was caught in a case when developers works behind company firewall and requires install company self signed certificate on Ubuntu host in order to access via company proxy. + The issue initially was caught in a case when developers works behind + company firewall and requires install company self signed certificate on + Ubuntu host in order to access via company proxy. This is also causing problems for snapcraft developers who work behind proxy servers unable to build snap packages. There is a fix going into openssl upstream apparently https://github.com/openssl/openssl/pull/10587 Just create a bug here to track this issue in Ubuntu in order to make sure we merge upstream fixes ultimately. - Similar case reported by other users: [1] https://serverfault.com/questions/966846/cannot-trust-development-https-self-signed-certificate-in-ubuntu-18-04-2-lts - [2] + [2] https://stackoverflow.com/questions/55485511/how-to-run-dotnet-dev-certs-https-trust/59702094#59702094 -- 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/1875781 Title: Unable to verify self signed certificate Status in openssl package in Ubuntu: New Bug description: See the upstream bug background https://github.com/openssl/openssl/issues/1418 The issue initially was caught in a case when developers works behind company firewall and requires install company self signed certificate on Ubuntu host in order to access via company proxy. This is also causing problems for snapcraft developers who work behind proxy servers unable to build snap packages. There is a fix going into openssl upstream apparently https://github.com/openssl/openssl/pull/10587 Just create a bug here to track this issue in Ubuntu in order to make sure we merge upstream fixes ultimately. Similar case reported by other users: [1] https://serverfault.com/questions/966846/cannot-trust-development-https-self-signed-certificate-in-ubuntu-18-04-2-lts [2] https://stackoverflow.com/questions/55485511/how-to-run-dotnet-dev-certs-https-trust/59702094#59702094 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1875781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
