| Summary: | Webdavs doesn't fully support Subject Alternative Name | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jason Haar <jhaar> |
| Component: | nautilus | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | mclasen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-01 03:51:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Actually, I think this is libreoffice now - not nautilus. When I opened the davfs share, it was clicking on .doc files that triggered the cert warning. However, I can't see how libreoffice would even know it was a dav share? Surely gvfs "pipes" the file open request - so only it would know it was a remote file? I dunno - you guys should ;-) Jason This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. |
Description of problem: nautilus doesn't properly support webDAV servers that have multiple hostnames via Subject Alternative Name If you connect to a trusted (ie the CA is trusted) webdavs server by an alternate DNS name, it connects just fine (ie the Alternate name support works). However, if you click on a file on such a share, it gives you a warning that the cert refers to a different host than it should ("Security Warning: Domain Name Mismatch") - so different checks are going on there... Version-Release number of selected component (if applicable): nautilus-3.0.2 I'm actually on FC15, but googling didn't show anyone else noticing, so I assume it's still an issue under FC17 How reproducible: always per mount-time. Steps to Reproduce: 1. mount webdavs share in nautilus 2. double-click on file 3. see warning Actual results: Expected results: Additional info: This is probably some library at fault - not nautilus - but I ain't guessing! As nautilus should have already done that check when the share was opened, why does it check when the first file is opened? Surely any decision making has already occurred?