summaryrefslogtreecommitdiff
path: root/src/WinTLSContext.cc
Commit message (Collapse)AuthorAgeFilesLines
* make clang-format using clang-format-3.6Tatsuhiro Tsujikawa2015-12-271-28/+18
|
* Fixed some typos in code commentsDan Fandrich2015-01-161-2/+2
|
* Move warn logic into SocketCoreNils Maier2014-12-141-10/+41
| | | | | Also fiddle a bit with the WinTLS implementation, forcing "strong" crypto only for > SSLv3.
* Add --min-tls-version optionTatsuhiro Tsujikawa2014-12-061-9/+31
| | | | | The --min-tls-version option specifies minimum SSL/TLS version to enable. Possible Values: SSLv3, TLSv1, TLSv1.1, TLSv1.2 Default: TLSv1
* Consistent style in the platform TLS implementationsNils Maier2014-05-291-32/+23
|
* WinTLS: Move some defines out of the headerNils Maier2014-04-131-0/+14
|
* WinTLS: Make ca-file rejection a warningNils Maier2014-04-131-1/+1
|
* WinTLS: Use SCH_USE_STRONG_CRYPTONils Maier2014-04-131-2/+8
| | | | See: #217
* WinTLS: Accept chains with no revocation information.Nils Maier2014-04-131-1/+2
| | | | | | | | | | | | | | | | | | This is kind what browser do anyway (IE, Firefox, Chrome tested), what AppleTLS does, what GnuTLS does and what OpenSSL does. Actually, most browsers will also be OK with the CRL/OCSP provider being offline. WinTLS will still fail in that case. Should revocation information be available in the trust chain (CRL or OCSP) the certificate still will be checked! "Real" CAs, aka. those provided by the OS or system CA bundle, usually provide revocation information and are thus still checked. It should be mostly (only?) custom (organization) CAs that lack revocation information, but those users might want to use aria2 in their intranets and VPNs anyway ;) See #217
* WinTLS: Fix PKCS12 loadingNils Maier2013-09-301-20/+31
| | | | | It appears that, contrary to most documentation, CERT_CONTEXT* is eaten alive by AcquireCredentialsHandle(). Hence you cannot really reuse that.
* Implement WinTLSNils Maier2013-09-301-0/+189
generated by cgit (git 2.46.0) at 2026-10-12 05:06:41 +0000