On Fri, 4 Apr 2003 17:19:00 -0800 Abhishek Amit <[EMAIL PROTECTED]> wrote:
> On 19:49 Thu 03 Apr , C. Brewer wrote:
> > > The only issue is that lft needs to be suid to work for non-root, and
> > > I've not yet dealt with that in the ebuild....
> > >
> > > -JimC
> >
> > I know this is off the thread a bit,but you can chmod right in the ebuild..
> > chmod 2755 ${D}/usr/bin/lft
> > and that'll fix up the perms before the merge:)
> >
> > --
> > Chuck Brewer
> > Registered Linux User #284015
> > Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
> >
> >
>
> I don't know what the actual policy is, but the links ebuild does the
> following instead of making it suid.
> einfo "You had the svga USE flag enabled, but for security reasons"
> einfo "the links2 binary is NOT setuid by default. In oder to"
> einfo "enable links2 to work in SVGA, please change the permissions"
> einfo "of /usr/bin/links2 to enable suid."
>
>
> --
> [EMAIL PROTECTED] mailing list
>
I'll admit I'm not familiar with whatever actual policy is either, and you do present
a viable solution. I'm also just guessing that lft won't function non-suid. I was just
mostly rambling about how you can execute commands in the ebuild to accommodate
special procedures, for after all, it's still bash underneath:)
--
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
pgp00000.pgp
Description: PGP signature
