文件列表:

bcl32.lib (6656, 2002-02-04)
bn\alpha.s (6309, 2000-12-11)
bn\bn-win32.asm (12616, 1998-04-10)
bn\bn-win32.obj (1808, 1998-04-09)
bn\bn.h (14997, 2000-11-21)
bn\bn86unix.cpp (14019, 1998-04-10)
bn\bn_add.c (5013, 1998-11-07)
bn\bn_blind.c (4946, 1998-11-07)
bn\bn_div.c (7860, 1998-11-07)
bn\bn_exp.c (13629, 1998-11-07)
bn\bn_gcd.c (5851, 1998-11-07)
bn\bn_lcl.h (5830, 1998-05-07)
bn\bn_lib.c (12729, 1999-05-26)
bn\bn_mod.c (4092, 1998-11-07)
bn\bn_mont.c (8691, 1998-11-07)
bn\bn_mul.c (4087, 1998-11-07)
bn\bn_mulw.c (8167, 2000-03-07)
bn\bn_prime.h (15241, 1998-04-10)
bn\bn_recp.c (4507, 1998-11-07)
bn\bn_shift.c (5672, 1998-11-07)
bn\bn_sqr.c (4402, 1998-11-07)
bn\bn_sub.c (5503, 1999-01-31)
bn\bn_word.c (5532, 1998-11-07)
bn\bugs.txt (3706, 1998-05-07)
bn\pa-risc.s (15714, 1998-04-10)
bn\pa-risc2.s (8487, 1998-04-10)
bn\r3000.s (9845, 1998-04-10)
bn\sparc.s (6718, 1998-07-07)
bn\x86w16.asm (4747, 1998-04-10)
bn\x86w32.asm (6021, 1998-05-15)
bn\x86w32.obj (1089, 1998-05-15)
certinst.dsp (3985, 2001-12-21)
certinst.dsw (539, 2000-03-01)
cl16.mak (40578, 1999-03-24)
crypt.c (66006, 2002-01-24)
crypt.def (1507, 2002-01-30)
crypt.exp (708, 1997-01-23)
crypt.h (52119, 2002-01-28)
crypt.ico (766, 1995-11-03)
crypt.rc (906, 2002-02-03)
... ...

Changes in 3.0 release ====================== cryptlib 3.1 will introduce a new function cryptFlushData() to replace the current practice of calling cryptPushData() will all-null parameters, a change required for languages like Delphi and VB which don't handle C null pointers too well. This function is already present in 3.0 for forwards-compatibility purposes, it's recommended that you update your code to call cryptFlushData() in place of cryptPushData() with null parameters (although the existing cryptPushData() mechanism will still work). The Unix randomness-gathering code will now check for and use EGD/PRNGD if they're available. The requirement that cryptlib be built via a network share under Windows has been removed. HTTP keyset access (CRYPT_KEYSET_HTTP) formerly required that the keyset be opened without a name being given, with the full URL being specified as the key ID to retrieve keys. This was both somewhat inconsistent with the other keyset types, and didn't work well with persistent connections, for example where multiple certificates were being read from a single server. This has been changed so that the server URL is given when the keyset is opened as it is for other keyset types, and a key ID is given when reading individual keys. When reading keys with a fixed URL (with no per-key ID), the special ID "[none]" can be used to indicate that the server URL points directly at the certificate. In the simplest case the previous usage: cryptKeysetOpen( &cryptKeyset, CRYPT_UNUSED, CRYPT_KEYSET_HTTP, NULL, CRYPT_KEYOPT_READONLY ); cryptGetPublicKey( cryptKeyset, &cryptCert, CRYPT_KEYID_NAME, "http://www.server.com/cert.der" ); now becomes: cryptKeysetOpen( &cryptKeyset, CRYPT_UNUSED, CRYPT_KEYSET_HTTP, "http://www.server.com/cert.der", CRYPT_KEYOPT_READONLY ); cryptGetPublicKey( cryptKeyset, &cryptCert, CRYPT_KEYID_NAME, "[none]" ); Reading multiple certificates, for example via a CGI interface on the server, is done with: cryptKeysetOpen( &cryptKeyset, CRYPT_UNUSED, CRYPT_KEYSET_HTTP, "http://www.server.com/certstore.cgi", CRYPT_KEYOPT_READONLY ); cryptGetPublicKey( cryptKeyset, &cryptCert, CRYPT_KEYID_NAME, "user1" ); cryptGetPublicKey( cryptKeyset, &cryptCert, CRYPT_KEYID_NAME, "user2" ); cryptGetPublicKey( cryptKeyset, &cryptCert, CRYPT_KEYID_NAME, "user3" ); Changes in 3.0 final beta ========================= The cryptlib 3.0 final release divides the network timeout parameter into two parts, a CRYPT_OPTION_NET_CONNECTTIMEOUT which is applied during the connection setup process and a CRYPT_OPTION_NET_TIMEOUT which is applied during reads and writes (although in practice writes are almost always instantaneous). This means that it's now possible to avoid nonblocking I/O if required. Use of SSL/TLS client certificates is now enabled. The final version of the S/MIME PasswordRecipientInfo (PWRI) RFC contained a change in the way the key wrap algorithm is identified. The cryptlib final release produces a PWRI which follows the final RFC, but will also read the older format produced by earlier versions of cryptlib. If it's necessary to generate PWRI data in the old format, you can change the "#if 1" in keymgmt/asn1objs.c to "#if 0" to produce the older format. Support for extended CMP user configurability via PKIUser objects has been added, this allows user details to be pre-configured at the CA rather than requiring the user to know them. Changes in 3.0 beta 6 ===================== Beta 6 reduces the plethora of key generation functions by allowing the keysize to be specified in the more standard way of setting the corresponding attribute rather ... ...

近期下载者：

相关文件：

评论：我要评论

收藏者：