kwallet and QCA

[Rafael Fernández López]

Hi,

> I guess you could store the password centrally and then leave it to each
> individual program to open the file, lock it for reading, decrypt and
> then unlock, but that looks like a suboptimal approach.
>
> I would prefer a standardised interface via D-Bus and a non-standardised
> file format.

From my understanding of this issue I also think this is the best solution 
nowadays.

For sure I prefer to maintain code that I'm used to, rather than a mixture of 
different flavours, what in the end, becomes unmaintainable.


Regards,
Rafael Fernández López.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080605/cb667d46/attachment.sig>