hostname verification in syncdaemon does not respect wildcard certificates
Bug #1013406 reported by
Curtis Caravone
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Ubuntu One storage protocol | Status tracked in Trunk | |||||
| Stable-3-0 |
Triaged
|
Wishlist
|
Unassigned | |||
| Stable-4-0 |
Triaged
|
Wishlist
|
Unassigned | |||
| Trunk |
Triaged
|
Wishlist
|
Alejandro J. Cura | |||
| ubuntuone-storage-protocol (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | |||
| Precise |
Won't Fix
|
Undecided
|
Unassigned | |||
Bug Description
When connecting to staging with syncdaemon, I get an error message like:
'Host name does not match certificate. Expected fs-1.staging.
connection works against production, which doesn't employ a wildcard certificate
| Changed in ubuntuone-storage-protocol (Ubuntu Quantal): | |
| status: | New → Triaged |
| Changed in ubuntuone-storage-protocol (Ubuntu Precise): | |
| status: | New → Triaged |
Revision history for this message
| Alejandro J. Cura (alecu) wrote | #1 |
| tags: | added: canonical-webops-u1 |
| tags: | added: foundations+ |
| tags: |
added: desktop+ removed: foundations+ |
| summary: |
hostname verification in syncdaemon does not respect wildcard - certificats + certificates |
| no longer affects: | ubuntuone-storage-protocol (Ubuntu Quantal) |
Revision history for this message
| Steve Langasek (vorlon) wrote | #2 |
| Changed in ubuntuone-storage-protocol (Ubuntu Precise): | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
So far this only affects connecting to the staging servers, and for that case SyncDaemon can be started with --disable_