Extended Validation certificates.
The plan for KDE is that QCA will provide access
to the issuer name and certificate policies
(which is already possible), plus access to the
special information fields. KDE will then decide
whether the certficate is really EV (based on
whether Konqi thinks the issuer is trustworthy
and the policy (which is issuer specific) denotes
EV.
svn path=/trunk/kdesupport/qca/; revision=601157
found in Extended Validation certificates.
The spec for this can be seen at
http://www.cabforum.org/EV_Certificate_Guidelines_-_Draft_10-2...pdf, Section 6 provides the information on the certificate
contents.
Note that this is based on an draft of the "guidelines",
and there could be some changes (although it is pretty
unlikely - this part of the spec has been pretty stable
for a while).
svn path=/trunk/kdesupport/qca/; revision=601153
the QCA::KeyStore class.
There is something seriously wrong with KeyStore at
the moment, and this test segfaults in the
constructor.
CCMAIL: justin@affinix.com
svn path=/trunk/kdesupport/qca/; revision=597919
Also check that PKCS12 support is available before trying
to use it in the constructor that takes a filename.
svn path=/trunk/kdesupport/qca/; revision=597049
1. this provider now uses the "pkcs12" label instead of "pix",
to match a change I just committed into the main part of QCA.
2. Fix a crash that occurs when trying to output a KeyBundle
in PKCS12 format.
3. Implement support for "friendly name" when loading PKCS12
(.p12) format files.
svn path=/trunk/kdesupport/qca/; revision=597047
I think this one has pretty good test coverage, however
it is causing the OpenSSL provider to segfault. Looks
like an bug in the provider rather than the unit test though.
svn path=/trunk/kdesupport/qca/; revision=597003
now has OFB support. This won't be released until 1.3.0.
Also, the fixes for SHA2 (i.e. SHA384/SHA512) didn't make
it into libgcrypt-1.2.3 for reasons that I don't understand,
but in any case, we need to manage that here.
svn path=/trunk/kdesupport/qca/; revision=595614
(RFC3546).
Note that this will only work if your underlying OpenSSL implementation
also supports it, which is true for the 0.9.9 development (essentially
CVS HEAD for OpenSSL), but not for 0.9.8 or earlier.
This version should build with either 0.9.9 or 0.9.8, and should also
be OK with at least 0.9.7.
Also has some gratuitous whitespace changes courtesy of my new
xemacs configuration.
CCBUG: 122433
svn path=/trunk/kdesupport/qca/; revision=594801
Also enable the base64 unit test, which was previously
commented out pending the completion of the CMake port
svn path=/trunk/kdesupport/qca/; revision=594798
1. Merge the .h into the .cpp
2. Update the qmake buildsystem to match
3. Add CMake support
4. Update the certificates, which had expired. Once
again, I'm using the test certs from http://openvalidation.org.
svn path=/trunk/kdesupport/qca/; revision=594720
same file for declaration and definitions, and ajust
the build system to match.
Also add CMake support.
svn path=/trunk/kdesupport/qca/; revision=594717
