Re: Insecure memory



Adam Schreiber wrote:
> On Nov 24, 2007 11:46 PM, James Utter <james utter gmail com> wrote:
>> chmod u+s /usr/bin/seahorse
>> chmod u+s /usr/bin/seahorse-agent
>>  chmod u+s /usr/bin/seahorse-daemon
> 
> The above should be enough to be using secure memory.

Note that in seahorse version 2.21.3 and later it is not necessary or
useful to use setuid on these binaries. Seahorse now uses the
gnome-keyring secure memory APIs.

Cheers,
Stef Walter



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]