Seahorse issues

Joe Marcus Clarke marcus at marcuscom.com
Sat Apr 12 17:51:35 UTC 2008


On Sat, 2008-04-12 at 13:38 -0400, Joe Marcus Clarke wrote:
> On Sat, 2008-04-12 at 12:43 -0400, Coleman Kane wrote:
> > 
> > As for the mlock() privilege issue, I am not sure what we'll do about
> > that. It would be nice, at some point, to support that feature for
> > normal users. As long as I'm diligent about my swap-space, etc... and
> > access to my workstation, I'm *pretty* secure. Things like common-use
> > lab computers, etc... are probably more appropriate for this feature.
> 
> Since we already have an rlimit for locked memory (RLIMIT_MEMLOCK), and
> it is used by the mlock(2) syscall, what about the attached patch to add
> a sysctl to control user access to mlock (but not allowing mlockall(2))?
> This has been tested to fix the gnome-keyring issue when the sysctl is
> set to 1.  If this is agreeable, I can add some manpage docs as well.

Minor modification to allow munlock(2) as well as mlock(2).

http://www.marcuscom.com/downloads/vm_mmap.c.diff

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20080412/e28493e9/attachment.pgp


More information about the freebsd-gnome mailing list