On Sat, Dec 3, 2011 at 3:10 AM, /dev/ammo42 mickeytintincolle@yahoo.frwrote:
Le Sat, 3 Dec 2011 02:05:59 +0000, Tiago Marques tiagomnm@gmail.com a écrit :
I think that saving it in memory can be potentially exploited and is something that shouldn't be done.
kdesud is protected against ptrace, at least in KDE 4.5. So I think the issue is whether we can trust the Linux kernel's memory protection. Also, KDE 4.5's "Keep password" feature (which is available in Slackware KDE packages) doesn't allow to re-use the password for another command, but only for the already launched application.
Then it is probably secured enough if implemented that way. Any idea of the situation in Trinity?
Best regards, Tiago
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting