importd servers don't deal with invalid certificates gracefully
Bug #512763 reported by
Tom Haddon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Michael Hudson-Doyle |
Bug Description
The following output is seen on https:/
- Hostname: source.mysema.com
- Valid: from Mon, 18 Aug 2008 10:49:13 GMT until Thu, 16 Aug 2018 10:49:13 GMT
- Issuer: IT, Mysema Ltd, Helsinki, Helsinki, FI
- Fingerprint: a1:1f:62:
(R)eject, accept (t)emporarily or accept (p)ermanently?
This means it's going to hang waiting for a response. The issue in question is a self-signed certificate.
Related branches
lp:~mwhudson/launchpad/ssl-imports-bug-512763
Merged
into
lp:launchpad
- Aaron Bentley (community): Approve
-
Diff: 32 lines (+15/-0)1 file modifiedscripts/code-import-worker.py (+15/-0)
affects: | launchpad → launchpad-code |
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Michael Hudson (mwhudson) |
Changed in launchpad-code: | |
milestone: | none → 10.02 |
status: | In Progress → Fix Committed |
Changed in launchpad-code: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It appears that the SSL certificate has been added manually to russkaya and neumayer, but somehow galapagos was missed. Hopefully, we can improve this situation now that we're using bzr-svn.