diff options
Diffstat (limited to 'src/mscrypto/README')
| -rw-r--r-- | src/mscrypto/README | 43 |
1 files changed, 28 insertions, 15 deletions
diff --git a/src/mscrypto/README b/src/mscrypto/README index 0b3f4b6b..f7d45636 100644 --- a/src/mscrypto/README +++ b/src/mscrypto/README @@ -1,28 +1,28 @@ WHAT VERSION OF WINDOWS? ------------------------------------------------------------------------ -The xmlsec-mscrypto lib is developed on a windows XP machine with MS Visual -Studio (6 and .NET). The MS Crypto API has been evolving a lot with the +The xmlsec-mscrypto lib is developed on a windows XP machine with MS Visual +Studio (6 and .NET). The MS Crypto API has been evolving a lot with the new releases of windows and internet explorer. MS CryptoAPI libraries -are distributed with ie and with the windows OS. Full functionality will -only be achieved on windows XP. AES is for example not supported on pre -XP versions of Windows (workarounds for this are possible, I believe). -Direct RSA de/encryption, used by xmlsec-mscrypto, is only possible from -Win 2000 (possibly also with a newer version of ie, with strong encryption +are distributed with ie and with the windows OS. Full functionality will +only be achieved on windows XP. AES is for example not supported on pre +XP versions of Windows (workarounds for this are possible, I believe). +Direct RSA de/encryption, used by xmlsec-mscrypto, is only possible from +Win 2000 (possibly also with a newer version of ie, with strong encryption patch installed). It's very likely more of these issues are lying around, a nd until it is tested on older windows systems it is uncertain what will work. -KEYS MANAGER with MS Certificate store support. +KEYS MANAGER with MS Certificate store support. ------------------------------------------------------------------------ -The default xmlsec-mscrypto keys manager is based upon the simple keys -store, found in the xmlsec core library. If keys are not found in the -simple keys store, than MS Certificate store is used to lookup keys. -The certificate store is only used on a READONLY base, so it is not possible -to store keys via the keys store into the MS certificate store. There are enough +The default xmlsec-mscrypto keys manager is based upon the simple keys +store, found in the xmlsec core library. If keys are not found in the +simple keys store, than MS Certificate store is used to lookup keys. +The certificate store is only used on a READONLY base, so it is not possible +to store keys via the keys store into the MS certificate store. There are enough other tools that can do that for you. -When the xmlsec application is started, with the config parameter the name of +When the xmlsec application is started, with the config parameter the name of the (system) keystore can be given. That keystore will be used for certificates and keys lookup. With the keyname now two types of values can be given: - simple name (called friendly name with MS); @@ -33,7 +33,20 @@ KNOWN ISSUES. 1) Default keys manager don't use trusted certs in MS Crypto Store (http://bugzilla.gnome.org/show_bug.cgi?id=123668). -2) The only supported file formats are PKCS#12 and DER certificates +2) Missing crypto functionality: + - HMAC (http://bugzilla.gnome.org/show_bug.cgi?id=123670): does not look + like MS would support it soon. + - RSA-OAEP (http://bugzilla.gnome.org/show_bug.cgi?id=123671): MS says + that they will support this in the near future. + - AES KW (http://bugzilla.gnome.org/show_bug.cgi?id=123672): no native + support, might be possible to implement on top of AES cipher itself + - DES KW (http://bugzilla.gnome.org/show_bug.cgi?id=123673): no native + support, might be possible to implement on top of AES cipher itself + +3) Actual AES Crypto provider name is different from the "official" one +(http://bugzilla.gnome.org/show_bug.cgi?id=123674). + +4) The only supported file formats are PKCS#12 and DER certificates (http://bugzilla.gnome.org/show_bug.cgi?id=123675). |