Common string encryption

Waldo Bastian bastian at
Tue May 20 10:15:04 BST 2003

Hash: SHA1

On Tuesday 20 May 2003 10:46, Michael Goffioul wrote:
> > If you can use a one-way encryption or hash, it would be best, since the
> > original password could not be retrieved from the written data. If you
> > really need to store a password, then I'd suggest waiting a couple of
> > months to see how far along KWallet comes.
> >
> > I don't think this is the time to start writing encryption stuff into the
> > core libraries if we are going to have an engine to handle passwords
> > efficiently in the near future.
> My point was not to rewrite an encryption routine, but simply to move
> the simple kmail encryption function (5 lines of code) to kdelibs such
> that other apps can store passwords in non-clear form. But OK, I can
> live with clear-form storing, in the end, it's the user who decides
> if he wants to store the password or not (the simple encryption was
> only intended for very basic security).

Yes, I think it's a good idea to move those lines from KMail to KStringHandler 
as long as it does not make any references to "encryption" since that 
suggests a sense of security that it does not provide. "obscuring" would be a 
more appropriate term.

- -- 
bastian at -=|[ SuSE, The Linux Desktop Experts ]|=- bastian at
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see


More information about the kde-core-devel mailing list