I dont know if this is what you are looking for but something like this will email it too you daily.
Dont know if this is on the right track, but it is just a simple script that you can put in cron that will check files and email too you. For any other files you want just put them in there as a new line.
Hi Team,
I want to set permissions to one folder in such a way that the user can write files or create folder inside that but should not able to delete it.
Basically reason behind this is i am using Pidgin Messenger. There is a directory of logs in which, when user chat its store his logs.... (2 Replies)
Introduction
I have seen some misinformation regarding Unix file permissions. I will try to set the record straight. Take a look at this example of some output from ls:
$ ls -ld /usr/bin /usr/bin/cat
drwxrwxr-x 3 root bin 8704 Sep 23 2004 /usr/bin
-r-xr-xr-x 1 bin bin ... (6 Replies)
Hello,
If you are interested in security, check out this new directory of unix and linux related software tools.
Security - Links
If you have any of your favorite tools, feel free to add them to the directory. (0 Replies)
I work for a big company and all the people within my unit share a common drive to save documents to. I am listed in the group(AMS group) that has access rights to folders within this drive. but i'm trying to restrict access to a confidential folder so that only I can access it.
when I set the... (0 Replies)
Hello,
What does the following mean in terms of file permissions.
-rw-rwSrw- 1 owner group 999 May 25 2004 file_name
What does the "S" stand for.
Thanks in advance for your input. :) (3 Replies)
I am starting an audit of unix security within our company and am looking for any information that may assist me with this. I am looking for any tips or pointers that I should be aware of when looking at unix. I am very new to unix so any help will do. Maybe there is someone out the that has had... (3 Replies)
audit.conf(4) Kernel Interfaces Manual audit.conf(4)NAME
audit.conf, audit_site.conf - files containing event mapping information and site-specific event mapping information
DESCRIPTION
Files and store the event mapping information that can be used by and
An event is a particular system operation. It may be either a self-auditing event or a system call. Auditable events are classified into
several event categories and/or profiles. Events and system calls may have aliases.
When the auditing system is installed, a default set of event mapping information is provided in In order to meet site-specific require-
ments, users may also define event categories and profiles in
In general, an event category is defined as a set of operations that affect a particular aspect of the system. A profile is defined as a
set of operations that affect a particular type of system. With these classifications, a set of events can be selected when using or by
specifying the event category or the profile that the events are associated with.
Here is the syntax of the directives in and
Event categories are defined using the directive for base events and the directive for event aliases.
Base events are events that are pre-defined by the HP-UX operating system. They are always associated with self-auditing events that have
the same name and/or with a list of system calls with the names that are referred to by the HP-UX auditing system.
Event aliases, distinct from base events, are combinations of base events, self-auditing events, system calls, and system call aliases.
The system call name referred to by the auditing system usually matches the real system call name with a few exceptions. If the system
call is one of these exceptions, an alias name may be defined using the directive, and the alias name can be used by and system call level
selection. For example, the system call is referred to as the system call by the auditing system. The interface of is not publicly
exported, but the security relevant information of this system call is described in this file documents the security relevant information
for all system calls that have names beginning with a period
Profiles are defined using the directive. Profiles can be combinations of any events.
In only and directives are allowed; names picked for or must begin with a uppercase character and must have at least one lowercase charac-
ter. Adding or at the end of an event name indicates only include successful or failed operations.
EXAMPLES
Here are some example entries that could be in
Selecting for auditing enables audit for the system calls (for both pass and fail), (for pass only), and (for fail only). Note that con-
tains and the fail events covered under Selecting this profile causes to be audited for both pass and fail, and to be audited for fail, and
to not be audited at all.
AUTHOR
was developed by HP.
FILES
File containing event mapping information
File containing audit information description for
HP-UX internal system calls which are not publicly supported
File containing site-specific event
mapping information
SEE ALSO audevent(1M), audisp(1M).
audit.conf(4)