[Touch-packages] [Bug 1875781] Re: Unable to verify self signed certificate
The corresponding patch has been merged in newer releases which have since been shipped. I'm going to mark this issue as Fix Released for openssl. ** Changed in: openssl (Ubuntu) Status: Triaged => Fix Released -- 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 Snapcraft: New Status in openssl package in Ubuntu: Fix Released 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 internet via company proxy. User may experience unable to access internet services via https protocol when even manually installed root trust ca-certificate on host machine due to openssl unable to verify some type of self signed certificate. 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/snapcraft/+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
[Touch-packages] [Bug 1875781] Re: Unable to verify self signed certificate
** Package changed: snapcraft (Ubuntu) => snapcraft -- 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 Snapcraft: New Status in openssl package in Ubuntu: Triaged 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 internet via company proxy. User may experience unable to access internet services via https protocol when even manually installed root trust ca-certificate on host machine due to openssl unable to verify some type of self signed certificate. 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/snapcraft/+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
[Touch-packages] [Bug 1875781] Re: Unable to verify self signed certificate
** Also affects: snapcraft (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/1875781 Title: Unable to verify self signed certificate Status in openssl package in Ubuntu: Triaged Status in snapcraft 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 internet via company proxy. User may experience unable to access internet services via https protocol when even manually installed root trust ca-certificate on host machine due to openssl unable to verify some type of self signed certificate. 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
[Touch-packages] [Bug 1875781] Re: Unable to verify self signed certificate
The patch to address this is rather large, and doesn't quite apply cleanly to 1.1.1f that we currently ship. Also there is a workaround for this - just generate a better / different self-signed cert which is identified as such by openssl. But I do understand that doing that may be very inconvenient as well. ** Changed in: openssl (Ubuntu) Status: New => Triaged ** Changed in: openssl (Ubuntu) Importance: Undecided => Medium -- 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: Triaged 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 internet via company proxy. User may experience unable to access internet services via https protocol when even manually installed root trust ca-certificate on host machine due to openssl unable to verify some type of self signed certificate. 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
[Touch-packages] [Bug 1875781] Re: Unable to verify self signed certificate
** 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. + Ubuntu host in order to access internet via company proxy. + + User may experience unable to access internet services via https + protocol when even manually installed root trust ca-certificate on host + machine due to openssl unable to verify some type of self signed + certificate. 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 -- 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 internet via company proxy. User may experience unable to access internet services via https protocol when even manually installed root trust ca-certificate on host machine due to openssl unable to verify some type of self signed certificate. 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
