Re: Key Management

> But cryptlib key files are encrypted and MAC'd anyway with an iterated salted
> hash.  Adding a second layer of encryption isn't going to do much.  In
> addition if they're in a database they'll still be written to disk, just as a
> database rather than a flat file.

But for this is separate linux server, where database resides on. Which 
I have full control over. Since key file is designed only for 32 private 
keys and not as a store for them, I am condemned to use this server for 
place for private keys.
It would be rather inconvenient to give an separate folder to each user 
at write an separate authentication for them, so database which already 
implemented security routines will be best solution, I suppose.



_______________________________________________
Cryptlib mailing list
[email protected] via Mail: [email protected]
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, please
subscribe in order to post messages.