/build/static/layout/Breadcrumb_cap_w.png

ACLs

Can the follwing advanced permissions be set to the [INSTALLDIR] using ACLs from a command line?

I need to add it to a custom action.

Traverse Folder / Execute File - ticked
List Flder / Read Data - ticked
Read Attributes - ticked
Read Extended Attributes - ticked
Create Files / Write Data - ticked
Create Folders / Append Data - ticked
Write Attributes - ticked
Write Extgended Attributes - ticked
Read Permissions - ticked

Cheers in advance for any assistance.

0 Comments   [ + ] Show comments

Answers (6)

Posted by: Inabus 15 years ago
Second Degree Green Belt
0
Any command line level permission utility can do this, an example is secedit.

P
Posted by: TOBES_UK 15 years ago
Senior Purple Belt
0
Ok thanks.

I have to use ACLs due to inhouse standards.

Do you know the syntaxt to do this using ACLs?
Posted by: anonymous_9363 15 years ago
Red Belt
0
ORIGINAL: TOBES_UK
I have to use ACLs due to inhouse standards.
Presumably the 'ACLs' you're referring to is the tool itself (as an alternative to XCACLS, SetACL etc.)? It's not a tool I'm familiar with (or heard of, come to that). It must have documentation or, at the very least, a help screen (ACLS /? or ACLS /h or ACLS -?...you get the idea...)

In-house standards are all very well but it sounds like whoever dictated the use of this tool failed to ensure that it was documented. Why not simply include an alternative tool, one whose syntax you know, in the Binary table, along with a script to use it? There's no risk to anyone there, since the tool and script will get deleted when the installer finishes.
Posted by: TOBES_UK 15 years ago
Senior Purple Belt
0
ORIGINAL: VBScab

ORIGINAL: TOBES_UK
I have to use ACLs due to inhouse standards.
Presumably the 'ACLs' you're referring to is the tool itself (as an alternative to XCACLS, SetACL etc.)? It's not a tool I'm familiar with (or heard of, come to that). It must have documentation or, at the very least, a help screen (ACLS /? or ACLS /h or ACLS -?...you get the idea...)

In-house standards are all very well but it sounds like whoever dictated the use of this tool failed to ensure that it was documented. Why not simply include an alternative tool, one whose syntax you know, in the Binary table, along with a script to use it? There's no risk to anyone there, since the tool and script will get deleted when the installer finishes.



My apologies, I meant SetACL.
Posted by: anonymous_9363 15 years ago
Red Belt
0
As far as I can make out, you just use the permission name instead of one of the standard ones e.g. 'read' would become 'traverse'
Posted by: AngelD 15 years ago
Red Belt
0
Please search for "b) Specific permissions" at http://setacl.sourceforge.net/html/doc-reference.html
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ