Description of problem: I have a subversion server which serves with mod_dav. I have my apache configured with name based virtual hosts. They work perfectly with a browser. Sadly on doing svn up the wrong certificate is polled from the server. As sni is not used. This has been reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569639 and has been fixed upstream at http://lists.manyfish.co.uk/pipermail/neon-commits/2010-March/000872.html. Version-Release number of selected component (if applicable): neon-0.29.3-1.fc13.i686 subversion-1.6.9-2.fc13.i686 How reproducible: 100% Steps to Reproduce: 1. setup mod_dav_svn 2. setup name based virtual hosting 3. do svn co on such a host Actual results: wrong certificate chosen Expected results: right certificate
Add Ville Skyttä who seems to be working on subversion.
I've merged this fix to the neon 0.29.x branch upstream and will try to wrap up a new release soon.
The relevant commit is at http://lists.manyfish.co.uk/pipermail/neon-commits/2010-May/000878.html Any chance to get this pushed out as an update?
somehow used wrong component
I am running F14 now.
neon-0.29.4-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/neon-0.29.4-1.fc14
neon-0.29.4-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update neon'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/neon-0.29.4-1.fc14
neon-0.29.5-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update neon'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/neon-0.29.5-1.fc14
neon-0.29.5-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.