- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- RBAC question
Operating System - HP-UX
1753448
Members
4855
Online
108794
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО10-15-2010 10:14 AM
тАО10-15-2010 10:14 AM
RBAC question
I'm trying to set up an authorization within RBAC that would allow a user to delete files within a specific directory that he doesn't own.
I can make it work if I just remove the directory itself. But it fails if I have the associated command as follows:
/usr/bin/rm /var/test/bscan2/*
As soon as it tries to run the command, it expands the "*". Then it fails as the command line is no longer a match for the original command.
$ privrun -v /usr/bin/rm /var/test/bscan2/*
privrun: user vendor intends to execute command /usr/bin/rm
privrun: input entry: '/usr/bin/rm:/var/test/bscan2/test :(,):///:dflt:dflt::'
privrun: no matching cmd found in cmd_priv database
I have a feeling that it will not work with the wildcard. Am I right, or am I setting it up wrong?
I can make it work if I just remove the directory itself. But it fails if I have the associated command as follows:
/usr/bin/rm /var/test/bscan2/*
As soon as it tries to run the command, it expands the "*". Then it fails as the command line is no longer a match for the original command.
$ privrun -v /usr/bin/rm /var/test/bscan2/*
privrun: user vendor intends to execute command /usr/bin/rm
privrun: input entry: '/usr/bin/rm:/var/test/bscan2/test :(,):///:dflt:dflt::'
privrun: no matching cmd found in cmd_priv database
I have a feeling that it will not work with the wildcard. Am I right, or am I setting it up wrong?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-16-2010 04:30 AM
тАО10-16-2010 04:30 AM
Re: RBAC question
Hi,
You could make an RBAC for the command "chown -R dirname". After that, with a succesful chown operation the user could delete the files as his own files. Call it as a workaround, I think this should work as chown -R doesn't require wildcards.
Regards,
Viktor
You could make an RBAC for the command "chown -R dirname". After that, with a succesful chown operation the user could delete the files as his own files. Call it as a workaround, I think this should work as chown -R doesn't require wildcards.
Regards,
Viktor
****
Unix operates with beer.
Unix operates with beer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-18-2010 01:52 PM
тАО10-18-2010 01:52 PM
Re: RBAC question
Hello,
Show us the results of the following commands:
# authadm list
# roleadm list
# rbacdbchk
Be aware that when assigning an authorization
that contains the asterisk ├в *├в character, you
must surround the wildcard character with
quotes to prevent shell interpretation.
The operations specified in /etc/rbac/auths
file must be fully-qualified and cannot use
wildcards. But, the objects can be be
specified with a wildcard using the asterisk
character (*). Authorizations that contain
wildcard operations are validated using a
match operation. At least one operation must
match the wildcard to assign the
authorization to the role.
Cheers,
VK2COT
Show us the results of the following commands:
# authadm list
# roleadm list
# rbacdbchk
Be aware that when assigning an authorization
that contains the asterisk ├в *├в character, you
must surround the wildcard character with
quotes to prevent shell interpretation.
The operations specified in /etc/rbac/auths
file must be fully-qualified and cannot use
wildcards. But, the objects can be be
specified with a wildcard using the asterisk
character (*). Authorizations that contain
wildcard operations are validated using a
match operation. At least one operation must
match the wildcard to assign the
authorization to the role.
Cheers,
VK2COT
VK2COT - Dusan Baljevic
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP