- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: security
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 10:57 PM
06-03-2002 10:57 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 11:07 PM
06-03-2002 11:07 PM
SolutionThere are two ways:
The first and most simplest method is to remove the path from either the 'users' .profile or the systems /etc/profile. The second and a little more drastic method is to change the permissions on the programs in /usr/sbin to be '550'. Doing so may cause one or more of your applications to collapse, but it is worthwhile at least testing.
Cheers
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 11:10 PM
06-03-2002 11:10 PM
Re: security
There are executables which are already secure
in /usr/sbin which can be run only as root.
eg. gated , sendmail
r-xr-xr-x 1 2 bin 995328 Oct 27 1997 /usr/sbin/gated
Still you can use chmod command to set your own
privileges.
#man chmod
regards,
U.SivaKumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 11:25 PM
06-03-2002 11:25 PM
Re: security
you can take sbin out of PATH for normal users, but this does NOT disable the commands for them! They still can use absolute pathes to get the commands to work:
/usr/sbin/whatever_command
will work....
To prevent all normal users, you have to change permissions on /usr/sbin, using the chmod- command:
chmod -R 550 /usr/sbin
Allways stay on the bright side of life!
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2002 12:25 AM
06-04-2002 12:25 AM
Re: security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2002 04:29 AM
06-04-2002 04:29 AM
Re: security
The best way is to keep users out of shells and into there applications, that way they can't execute squat! Really, the only users who should be allowed into shells, are System Admin's and DBA's - on production machines.
Don't forget that some /usr/sbin commands are links to /sbin and /usr/lbin.
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2002 05:52 AM
06-04-2002 05:52 AM
Re: security
Setting the correct permissions is the cleanest way to go about restricting.
Apart from permissions, some other methods include:
1) setting ACL (access control lists) for the commands in /usr/sbin. You can restrict only superuser and daemons' access to /usr/sbin etc.
man setacl (for JFS) or man chacl (for HFS) for more information.
2) use chroot to create a virtual root which prevents the user in this virtual root directory from accessing the real /usr/sbin.
man chroot for more information.
3) restrict what your users can do via restricted sam. Restricted sam allows you to limit users to specific scripts or commands. It also allows you to specify which users can run what programs with specific user's (can be another user's) privileges.
man sam for more information.
Hope this helps. Regards.
Steven Sim Kok Leong