ulf> > des_read_pw_string ../libcrypto.a(evp_key.o)
ulf>
ulf> Is there any reason why that function is defined in the DES directory
ulf> at all? Couldn't the implementation be moved into evp/evp_key.c?
I assume it has to do with the EAY's thoughts about it all (taken from
doc/ssleay.txt, section why.doc):
[...] The reason why
I keep everything in its own directory, and don't put all the
test programs and header files in 'test' and 'include' is because I want
to keep the 'sub-libraries' independant. I still 'pull' out
indervidual libraries for use in specific projects where the code is
required. I have used the 'lhash' library in just about every software
project I have worked on :-).
That together with the fact (or at least, I think that's how things
are) that DES was among the first crypto things EAY wrote makes it
logical.
Other than that, you're right, it should be moved somewhere else. Not
into EVP though, since that would more or less implicitely mean you
include another bag of stuff you don't want (assuming someone wants to
pull out parts of the library, like EAY used to do :-)). I'd rather
put it in it's own directory, called "passwd" for example...
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-161 43 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
