- 18 6月, 2001 2 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
everywhere.
-
- 17 6月, 2001 2 次提交
-
-
由 Ben Laurie 提交于
PR:
-
由 Ben Laurie 提交于
-
- 16 6月, 2001 1 次提交
-
-
由 Bodo Möller 提交于
-
- 11 6月, 2001 8 次提交
-
-
由 Bodo Möller 提交于
-
由 Andy Polyakov 提交于
Submitted by: Reviewed by: PR:
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
In the new crypto/ui/, this was changed into tty (which is usually /dev/tty), i.e. the FILE * used for reading passwords from the user. However stdio buffering for read/write streams is not without pitfalls (passwords would be echoed on some systems). To avoid problems, split tty into tty_in and tty_out (which are opened separately).
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
- 08 6月, 2001 2 次提交
-
-
由 Ulf Möller 提交于
-
由 Lutz Jänicke 提交于
-
- 07 6月, 2001 6 次提交
-
-
由 Richard Levitte 提交于
Spotted by Nalin Dahyabhai <nalin@redhat.com>
-
由 Richard Levitte 提交于
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
-
由 Ulf Möller 提交于
-
由 Ulf Möller 提交于
-
- 06 6月, 2001 3 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
_XOPEN_SOURCE.
-
由 Richard Levitte 提交于
(for new functions...). One might still want to be able to pass down a user-data pointer to be used by the UI. However, ex_data doesn't quite cut it, since that means the appropriate index to it might need to be shared between parts that aren't really related in that sense, and would require the currently hidden (static) index holders to be uncovered. Not a good thing. Therefore, add the possibility to add a user-data pointer to a UI.
-
- 05 6月, 2001 3 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
-
- 04 6月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
-
- 01 6月, 2001 7 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
-
由 Bodo Möller 提交于
(The attack against SSL 3.1 and TLS 1.0 is impractical anyway, otherwise this would be a security relevant patch.)
-
由 Bodo Möller 提交于
-
由 Richard Levitte 提交于
links.
-
由 Geoff Thorpe 提交于
a bit of weird code in sk_new.
-
- 31 5月, 2001 1 次提交
-
-
由 Andy Polyakov 提交于
Submitted by: Reviewed by: PR:
-
- 30 5月, 2001 2 次提交
-
-
由 Richard Levitte 提交于
string (some engines may have certificates protected by a PIN!) and a description to put into error messages. Also, have our own password callback that we can send both a password and some prompt info to. The default password callback in EVP assumes that the passed parameter is a password, which isn't always the right thing, and the ENGINE code (at least the nCipher one) makes other assumptions... Also, in spite of having the functions to load keys, some utilities did the loading all by themselves... That's changed too.
-
由 Richard Levitte 提交于
-
- 29 5月, 2001 2 次提交
-
-
由 Lutz Jänicke 提交于
-
由 Andy Polyakov 提交于
details (performance numbers and accompanying discussions:-). Note that the code is not engaged in ./Configure yet. I'll add it later this week along with updates for .spec file. Submitted by: Reviewed by: PR:
-