Eric S. Hvozda <hvozda@netcom.com> wrote:
> On Sat, 09 Dec 1995 11:57:52 -0600  Jon Buller wrote:
> > unless I run it a root.  I have SETUIDSCRIPTS in the config
> > file, and it used to work...  Any suggestions?
> 
> I have that in my config file as well, but I've always made scripts
> at least 555 (far as I know to run a script, it must be readable too).

Scripts did not have to be readable to execute when I made my Sept
28 kernel, (perhaps from fresh source or perhaps from source as
old as the end of August) but it appears that they need to be now.
Perhaps this should be on the tech-kern list?

Randy Terbush <randy@zyzzyva.com> writes:
> Jon Buller <jonb@metronet.com> writes:
> > (This may not be current any more, please humor a post that's
> > only a day or two late... 8-)

Well, I guess this isn't a problem, since they haven't switched the
sup tree from 1.1 to current yet... 8-)

> > Was there a recent change in the way scripts are exec'd (in the
> > last 2 months)?  The reason I ask is that I was using a script
> > to connect with my Internet provider, and it has clear-text
> > passwords in it.  To compensate for this, I made the script
> > mode 711 owned by root.  Everything worked fine, but I just
> > compiled a 1.1 kernel and now I get the message:
> 
> setuid requires modes 4711

Yes, but the stuff in my script does not require root privileges, so I
don't need it suid.  The SETUIDSCRIPTS flag is used in the kernel file
that exec's scripts though, and I thought it might have some bearing
on the problem at hand.  I didn't mean it to be a red herring.  I just
want an executable and non-readable script to hold the clear passwords.

Jon Buller