×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Loud, that kind of restriction requires the exit program, so that when a
"cd" request comes through, you get to see what the user is trying to do
and you can allow or reject. You could have any 'cd' request rejected,
e.g., so they can only go to their home directory. Or you could allow them
to make subdirectories of the home directory and allow them to 'cd' only to
one of those - you'd want to allow 'cd ~', becasue that takes them to the
home directory - if FTP allows that - don't remember - and possible 'cd ..'
for parent, so long as it does not go above the home directory.
The same treatment would be required for any path specified on other
commands, like mget.
Real security and control gets complicated fast, eh?
HTH
Vern
At 11:35 AM 2/5/2003 -0600, you wrote:
This is great timing, we had a need to make the exact changes below.
So if I set up a user to be in "/home/goodbar/", what prevents me from doing
a "cd /", "cd /qsys.lib/production.lib", "mget *"?
In other words, how can I restrict a user to just /home/goodbar?
Thanks,
Loyc
--
Loyd Goodbar
Programmer/analyst
BorgWarner Incorporated
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
