[SLL] script interpreter bootstrap tricks

[Brian Hatch]

At almost 2008-04-01 17:23 -0700, Scott Blachowicz spoke out:

> > I'll have to petition the admins on the oddball system to allow it in
> > /etc/shells.
> 
> Just curious...what does /etc/shells have to do with anything?  Are you saying
> that there's something in the system that looks at /etc/shells to decide
> what's OK to be on the #! line?  I've never heard of that before...

/etc/shells is traditionally used as the list of acceptable login
shells.  Then, in order to allow things like pop/ftp/etc where
you didn't want interactive shells, you'd create '/bin/poponly'
or '/bin/ftponly' which did an exit(1), and then add those to
/etc/shells and make that a user's login shell.

Shouldn't have anything to do with what your shebang line looks
like.  Python/perl/ruby/etc aren't shells after all.


-- 
Brian Hatch                  The only consistent feature
   Systems and                of all your dissatisfying
   Security Engineer          relationships is you.
http://www.ifokr.org/bri/

Every message PGP signed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists2.linuxjournal.com/pipermail/linux-list/attachments/20080401/f747c7d0/attachment.sig