Bug 454151
Summary: | CA certificate "missing" for launchpad, bzr fails | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gene Czarcinski <gczarcinski> | ||||||
Component: | curl | Assignee: | Kamil Dudka <kdudka> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 9 | CC: | emaldona, kdudka | ||||||
Target Milestone: | --- | Flags: | gczarcinski:
needinfo-
|
||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-07-14 15:39:33 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 501138 | ||||||||
Attachments: |
|
Description
Gene Czarcinski
2008-07-05 14:20:33 UTC
also reported upstream: http://sourceforge.net/tracker/index.php?func=detail&aid=2011303&group_id=976&atid=100976 As I get more information, I am adding it to the upstream report so track that report. It is sure looking like something in libcurl (nss.c for now). Any suggestions appreciated. Thanks for reporting, at least the curl-config --ca reporting @CURL_CA_BUNDLE@ looks pretty broken as it seems unevaluated by configure. There is something really strange going on in curl/libcurl when success or. failure depends on specify "-v". This tells me there might be an uninitialized variable somwhere of that a versiable is getting different values depending on the codepath. "ca-bundle.crt is copied from "/etc/pki/tls/certs/" -------------------------------------------------------------------------- [gc@falcon test]$ curl --cacert ./cacert.pem https://launchpad.net >xxx % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 13706 100 13706 0 0 10244 0 0:00:01 0:00:01 --:--:-- 69573 --------------------------------------------------------------------------- [gc@falcon test]$ curl --cacert ./ca-bundle.crt https://launchpad.net >xxx % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 13706 100 13706 0 0 11259 0 0:00:01 0:00:01 --:--:-- 69573 ----------------------------------------------------------------------------------- [gc@falcon test]$ curl -v --cacert ./ca-bundle.crt https://launchpad.net >xxx * About to connect() to launchpad.net port 443 (#0) * Trying 91.189.90.211... connected * Connected to launchpad.net (91.189.90.211) port 443 (#0) * CAfile: ./ca-bundle.crt CApath: none * Bad certificate received. Subject = 'CN=launchpad.net,OU=Domain Control Validated,O=launchpad.net', Issuer = 'E=practices,CN=Starfield Secure Certification Authority,OU=http://www.starfieldtech.com/repository,O="Starfield Technologies, Inc.",L=Scottsdale,ST=Arizona,C=US' * NSS error -8179 * Closing connection #0 * Peer certificate cannot be authenticated with known CA certificates curl: (60) Peer certificate cannot be authenticated with known CA certificates More details here: http://curl.haxx.se/docs/sslcerts.html That command works for me:: [badger@Clingman tmp]$ curl -v --cacert /etc/pki/tls/certs/ca-bundle.crt https://launchpad.net>xxx * About to connect() to launchpad.net port 443 (#0) * Trying 91.189.90.211... connected * Connected to launchpad.net (91.189.90.211) port 443 (#0) * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSL connection using SSL_RSA_WITH_RC4_128_MD5 * Server certificate: * subject: CN=launchpad.net,OU=Domain Control Validated,O=launchpad.net * start date: Jul 25 18:24:13 2006 GMT * expire date: Jul 25 18:24:13 2009 GMT * common name: launchpad.net * issuer: E=practices,CN=Starfield Secure Certification Authority,OU=http://www.starfieldtech.com/repository,O="Starfield Technologies, Inc.",L=Scottsdale,ST=Arizona,C=US > GET / HTTP/1.1 > User-Agent: curl/7.18.2 (i386-redhat-linux-gnu) libcurl/7.18.2 NSS/3.12.0.3 zlib/1.2.3 libidn/0.6.14 > Host: launchpad.net > Accept: */* > < HTTP/1.1 200 Ok < Date: Tue, 08 Jul 2008 23:24:12 GMT < Server: zope.server.http (HTTP) < X-Powered-By: Zope (www.zope.org), Python (www.python.org) < Content-Length: 13706 < Content-Type: text/html;charset=utf-8 < Set-Cookie: lp=Oagcw-BgHWWV7PnBux2Gia6LvrYkn3vlMb-fhHglhaJYfEDRlyO5uU; Domain=.launchpad.net; expires=Wed, 08 Jul 2009 23:24:12 GMT; Path=/; secure; < Via: 1.1 launchpad.net < Vary: Accept-Encoding < % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 13706 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0{ [data not shown] 100 13706 100 13706 0 0 10699 0 0:00:01 0:00:01 --:--:-- 31009* Connection #0 to host launchpad.net left intact * Closing connection #0 My machine is Fedora 9 with the following packages:: nss-3.12.0.3-0.9.1.fc9.i386 curl-7.18.2-1.fc9.i386 libcurl-7.18.2-1.fc9.i386 glibc-2.8-3.i686 openssl-0.9.8g-9.fc9.i686 Yes, and it works for me too sometimes and under some conditions. One thing I notice is that you are running i386 whereas I am running x86_64. We are running the same maintenance level ... package version/release. Why does it work for me if I copy ca-bundle.crt to my local directory to be used with --cacert ./ca-bundle.crt but then not work when I add "-v" OK, I just tried it on a x86_64 laptop and it worked (with or without the -v). But I was not current with nss so I updated to the latest ... and it stopped working correctly ... install --oldpackage .. worked but now did not work with "-v" I tried installing --oldpackage nss on my desktops, but they did not work. It does work consistently on a i386 install vmware virtual with current maintenance. I can get it to consistently work or not work but I have no idea what the precise conditions are. I have also opened a bug report with curl/libcurl upstream: https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2011303&group_id=976 I have also used wireshark to capture the packets for a "works" and a "woes not work" situation. I am attaching plain text exports of the certificate packet in both cases. I am not really knowledgeable at this level but (to me) the certificates look the same. Created attachment 311375 [details]
"works" certificate packet
Created attachment 311376 [details] "does not work" certificate packet In this case, libcurl says this is a bad certificate * Bad certificate received. Subject = 'CN=launchpad.net,OU=Domain Control Validated,O=launchpad.net', Issuer = 'E=practices,CN=Starfield Secure Certification Authority,OU=http://www.starfieldtech.com/repository,O="Starfield Technologies, Inc.",L=Scottsdale,ST=Arizona,C=US' curl: (60) Peer certificate cannot be authenticated with known CA certificates Changing to "x86_64" from "all" since the only systems I have problems on (I tried several) are all running x86_64 Fedora 9. Interesting, the curl/libcurl folks upstream claim that fedora screwed things up and are not looking at the problem ... in fact, they auto-closed the problem ... not friendly at all!! https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2011303&group_id=976 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Is the bug still present in up to date Fedora 9 (with curl-7.19.4-5.fc9)? It seems like already fixed: $ curl-config --ca /etc/pki/tls/certs/ca-bundle.crt $ curl --silent --verbose https://launchpad.net > /dev/null ... * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA * Server certificate: * subject: CN=launchpad.net,OU=Domain Control Validated,O=launchpad.net * start date: Jul 25 18:24:13 2006 GMT * expire date: Jul 25 18:24:13 2009 GMT * common name: launchpad.net * issuer: E=practices,CN=Starfield Secure Certification Authority,OU=http://www.starfieldtech.com/repository,O="Starfield Technologies, Inc.",L=Scottsdale,ST=Arizona,C=US > GET / HTTP/1.1 > User-Agent: curl/7.19.4 (x86_64-unknown-linux-gnu) libcurl/7.19.4 NSS/3.12.3 zlib/1.2.3 libidn/0.6.14 libssh2/0.18 > Host: launchpad.net > Accept: */* > < HTTP/1.1 200 OK ... Setting state to NEW as the bug is still unconfirmed. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |