centos & filepro system commands
Fairlight
fairlite at fairlite.com
Mon Jan 3 18:31:15 PST 2011
This public service announcement was brought to you by Kenneth Brody:
> What does this show?
>
> system "id ; read junk"
>
> (The "read junk" will cause the system to wait for you to press Enter before
> returning to filePro, so that you can see the output.)
>
> Also, what version of CentOS are you using?
He'll be on the latest 5.5 CentOS.
And you know that bash has dropped privileges since early in the 2.x tree
of the shell (or possibly as early as 1.2...memory is fuzzy THAT far
back--we're talking like a decade ago, here).
So the issue is obviously going to be that /appl/docs is likely owned by
filepro, but SYSTEM-executed commands are reverted to the real user by the
time they make it through the intervening bash shell. Not even sure why
you asked, as we can pretty much be 99.9%+ confident about exactly why this
is breaking for him. I'm all for thoroughness, but would have presented
the probable solution at the same time, rather than multistage him--at
least on one this obvious.
One can `chmod 1777 /appl/docs`, and the commands should start working
again, assuming that the JPEG being copied is at least readable by whatever
the -real- user(s) is/are. But only one real user at a time is going
to be able to affect or use any given files/directories unless one uses
-very- loose permissions. Hate to say this, but 0666 and 0777 are actually
closely related to the filePro community for more reasons than sheer
ignorance; in some cases, there's not a lot else to do without writing
other custom SUID wrappers around other programs.
By the way, Dave, you can SYSTEM off `chmod` to your heart's content from
processing to fix things as needed, but you cannot `chown` away from
yourself for security reasons, so don't even try.
mark->
--
Audio panton, cogito singularis.
More information about the Filepro-list
mailing list