OpenConnect upstream has released OpenConnect v2.25:
addressing following security related issues (from ):
OpenConnect v2.25 — 2010-05-15
* Always validate server certificate, even when no extra --cafile
* Add --no-cert-check option to avoid certificate validation.
* Check server hostname against its certificate.
* Provide text-mode function for reviewing and accepting "invalid"
* Fix libproxy detection on NetBSD.
This issues affect the versions of the openconnect package, as shipped
with Fedora release of 12 and 13. Please rebase to new version.
Created openconnect tracking bugs for this issue
Affects: fedora-all [bug 620220]
If we're going to treat this as a security advisory rather than the eventual completion of a known-missing feature (as I suppose we probably should), then I would very much appreciate it if someone from the security team could review my cert-validation code.
It sucks that I had to write this for myself, and that OpenSSL didn't provide a library function which did most of it for me. App developers are too stupid to be trusted with such things, as a rule.
See the verify_peer() and match_cert_hostname() functions, and helpers, at http://git.infradead.org/users/dwmw2/openconnect.git/blob/v2.25:/ssl.c#l496
Updates processing seems to be a little slow atm.
openconnect-2.25-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
openconnect-2.25-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
The CVE identifier of CVE-2010-3901 has been assigned to this issue.