Sponsored Content
Top Forums Programming help with C programme to lock remote resources Post 302292959 by jim mcnamara on Monday 2nd of March 2009 05:04:50 AM
Old 03-02-2009
You may also want to investigate ACL - access control lists. They provide very fine-grained control over accessing any file/device - ie., everybody but the username jmc can access this file/device. see: man chacl.

As with SELinux it may be painful to implement if this is implemented on a lot of different machines, and it will be a huge amount of work.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how to lock keyboard without using lock command

how can I lock my keyboard while I'm away from the computer without using lock command. What other commands gives me the option to lock keyboard device? thanks (7 Replies)
Discussion started by: dianayun
7 Replies

2. Shell Programming and Scripting

want to use output of c programme in expect

hi i am having a c code which gives the output of my password in text format i.e when i run my c code which which gives the password asfollows====>>>>>> $./passwdprogram ======>>>>>>abc@123(this is the output) now i have an expect script to remotely ssh which uses the password set in ... (0 Replies)
Discussion started by: xander
0 Replies

3. Programming

Need help in a c programme

Dear Friends, I ve two text files like re_im.dat 13.7663000000 5.9572200000 10.2682000000 10.9345000000 5.0810700000 14.1132000000 two real values per row Sarf.dat 127 128 128 128 71 0 128 128 128 128 71 0 128 128 128 128 71 0 This is having 6... (2 Replies)
Discussion started by: user_prady
2 Replies

4. Shell Programming and Scripting

snmpget in a perl programme

Hi Guyz can u tell me how to write a programme in perl using snmpget. Regards' Harrr (0 Replies)
Discussion started by: Harikrishna
0 Replies

5. Programming

cobol programme

I have some compile programme .crn now I want to run .crn programme on express cobol which allow only *.gnt programme any solution to run *.crn programme (0 Replies)
Discussion started by: bibi
0 Replies

6. Programming

starting programme in C

hello, For school i make the next mission: give how many chambers in a constant number. use an array which chamber is free and count how many chamber there are free. make also something to test I don't now how to start. I need an well example so i can make the mission thank you (1 Reply)
Discussion started by: wouter88
1 Replies

7. Programming

Help for coding this programme

for a floating-point array x whose size is n, find the geometric mean.. GM =n x1.x2.x3...xn (2 Replies)
Discussion started by: allyjaah
2 Replies

8. Red Hat

Security Question: Lock after invalid login, Session Lock and Required Minimum Password Length

Hello all, If anyone has time, I have a few questions: How do I do the following in Linux. We are using Red Hat and Oracle Enterprise Linux, which is based on Red Hat too. 1. How to lock the account after a few (like 3) invalid password attempts? 2. How do you lock a screen after 30... (1 Reply)
Discussion started by: nstarz
1 Replies

9. Shell Programming and Scripting

programme is ok but not working in script

hi buddies; i have a very strange problem. i made a script composed of just 5 line. it is containing awk and nawk codes and it is working perfectly when it is applied one-by-one (copy & paste). but when i type run myscript.mos, it is giving: nawk: syntax error at source line 1 context is... (5 Replies)
Discussion started by: gc_sw
5 Replies

10. UNIX for Advanced & Expert Users

Testing privileges -lock lockfile /var/lock/subsys/..- Permission denied

Hi all, I have to test some user priviliges. The goal is to be sure that an unauthorized user can't restart some modules (ssh, mysql etc...). I'm trying to automate it with a shell script but in same cases I got the syslog broadcast message. Is there any way to simply get a return code... (3 Replies)
Discussion started by: Dedalus
3 Replies
MAILDIRACL(1)						      Double Precision, Inc.						     MAILDIRACL(1)

NAME
maildiracl - manage access control lists SYNOPSIS
maildiracl {-reset} {maildir} maildiracl {-list} {maildir} {INBOX[.folder]} maildiracl {-set} {maildir} {INBOX[.folder]} {[-]identifier} {[+/-]rights} maildiracl {-delete} {maildir} {INBOX[.folder]} {[-]identifier} maildiracl {-compute} {maildir} {INBOX[.folder]} {identifier...} DESCRIPTION
maildiracl manages "access control lists" (or ACLs) of the Courier IMAP server maildir folders. Access control lists are used primarily to provide fine-grained control for accessing virtual shared folders via IMAP. Note The Courier IMAP server server implements two types of shared folders: filesystem permission-based shared folders, as well as virtual shared folders based on IMAP access control lists. Use the maildiracl command to set up access control lists for virtual shared folders. Use the maildirmake(1)[1], command to implement shared folders based on filesystem permissions. See the Courier IMAP server documentation for additional information on setting up virtual shared folders. ACL overview ACLs provide a fine-grained mechanism for controlling access to shared folders. ACLs may be used to specify, for example, that user1 may only open and read the messages in the folder; and user2 can not only do that, but also delete messages, and create subfolders. Each folder maintains its own individual access control list, that specifies who can do what to the folder. An ACL is a list of "identifier" and "rights" pairs. Each "identifier" and "rights" pair means that an entity called "identifier" (using the UTF-8 character set) is allowed to do "rights" on this folder. "rights" consists of one or more letters, each letter signifies a particular action: a identifier may modify this folder's ACLs. c identifier may create subfolders of this folder (this includes renaming another folder as this folder's subfolders). e identifier may remove deleted messages from this folder. i identifier may add messages to this folder (either uploading them one by one, or copying messages from another folder). l identifier may actually see that this folder exists. If identifier does not have the "l" right on this folder, the folder is effectively invisible to identifier. r identifier may open this folder. Note that if identifier knows the name of this folder, it can open it even if identifier does not the "l" right on this folder. s identifier may mark messages in this folder as seen, or unseen. t identifier may mark messages in this folder as deleted, or undeleted. w identifier may change other status flags of messages in this folder. May also add or remove custom keywords on individual messages. x identifier may delete this folder (which includes renaming this folder as another mailbox's subfoler. Negative rights An ACL entry of "-identifier" and "rights" is called a "negative right", which explicitly removes "rights" from "identifier". More than one "identifier" is usually used to determine the actual rights someone has for the given folder. The actual access rights are determined by taking all rights from all applicable identifier, than subtracting any negative rights, as specified in the following section. Identifiers Access rights on a given folder are computed by obtained the rights on the following identifiers, then subtracting the negative rights on the same identifiers: owner The owner of the maildir containing this folder. The maildir's INBOX's ACL defaults to all rights for its owner. A new folder's ACL is the same as its parent's ACL. In all cases, trying to remove the "a" right from the owner (either directly or using a negative right) results in an error. anyone This identifier refers literally to every userid. The associated rights (or negative rights) are always used. anonymous This is a synonym from "anyone". user=loginid Rights (or negative rights) for IMAP account "loginid". Note "loginid" is what's logged to syslog after a succesful login. In some situations "loginid" is not exactly the actual login ID used by the IMAP client. group=name Rights (or negative rights) for account group "name". Access rights are granted to an account group as a whole. The account options feature of the Courier Authentication Library specifies which account belongs to which account group. See courier-authlib's documentation for more information. administrators This is an alias for "group=administrators". Accounts that are members of an account group called "administrators" are considered administrative accounts, and automatically receive all access rights on all accessible folders. Consider the following access control list: owner aceilrstwx anyone lr user=john w -user=mary r administrators aceilrstwx This access control list specifies that the folder's owner has complete control over the mailbox (as well as the administrators, which have complete access to every folder); everyone else can see it and open it, except for "mary" who can see that the mailbox exists, but can't open it; additionally, "john" can change the status and keywords of individual messages (but not mark them as deleted/undeleted or seen/unseen, which requires additional rights). OPTIONS
maildiracl -reset maildir This command resets access control lists in maildir which as a path to a maildir. Under certain conditions, the files where a folder's ACLs are saved may continue to exist after the folder is removed. The -reset options goes through maildir and removes all stale ACL files for removed folders. Note The Courier IMAP server normally performs this maintenance function automatically. It is not necessary to run this command under normal conditions. maildiracl -list maildir folder This command lists the access control lists set for folder. folder must be either "INBOX" or "INBOX.folder.subfolder", which is the same naming convention for the Courier IMAP server. maildiracl -set maildir folder identifier rights Puts identifier (which may begin with a minus sign to specify a negative right) and rights in folder's access control list. Existing rights for identifier (or identifier) are replaced by rights unless "rights" begins with "+" or "-", which modifies the existing rights by adding or removing from them accordingly. Some examples: maildiracl -set /home/user1/Maildir INBOX.Sent user=john lr maildiracl -set /home/user2/Maildir INBOX.Notes anyone -r maildiracl -set /home/user3/Maildir INBOX.Private -user=tom +r Note Observe that the last command revokes the "r" right from "tom", by adding it as a negative right. maildiracl -delete maildir folder identifier This command removes identifier from folder's access control list, if it exists. Use "-identifier" to remove negative rights. maildiracl -compute maildir folder [identifier]+ This command takes a list of one or more identifiers. All access rights for the identifiers are combined together, then any appropriate negative rights are removed, and the result is printed on standard output. Use the following procedure to compute access rights the same way as they are computed by the Courier IMAP server: maildiracl -compute /home/tom46/Maildir INBOX.Sent owner user=tom46 This command computes access rights "tom46" has on his own folder. maildiracl -compute /home/john34/Maildir INBOX.Public user=tom46 This command computes access rights "tom46" has on "john34"'s folder. IRREVOCABLE ACCESS RIGHTS
The owner of the mailbox must always have the "a" amd "l" access rights. The administrators group must always have all access rights to all folders. Attempts to set access control lists, that do not include these minimum access rights, will be rejected. BUGS
All identifiers are specified using the UTF-8 character set. All non-Latin letters in folder names are specified using the modified-UTF7 coding as used in IMAP. This implementation of access control lists is based on version 2 (or "ACL2") of IMAP access control lists, which is a work-in-progress. The existing IMAP ACL, RFC 2086[2] is transparently implemented inside the ACL2 model. If history's of any guidance, ACL2 is subject to change at any time. Be sure to check the release notes when upgrading to a newer version of this software. The "ACL overview" portion of this manual page is a very brief summary of ACL2, which leaves out optional parts of ACL2 that are not implemented. SEE ALSO
maildirmake(1)[1], maildirkw(1)[3], AUTHOR
Sam Varshavchik Author NOTES
1. maildirmake(1) [set $man.base.url.for.relative.links]/maildirmake.html 2. RFC 2086 http://www.rfc-editor.org/rfc/rfc2086.txt 3. maildirkw(1) [set $man.base.url.for.relative.links]/maildirkw.html Courier Mail Server 08/31/2011 MAILDIRACL(1)
All times are GMT -4. The time now is 04:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy