You could also check the checksum of the files. This gives a unique number associated with the file and its contents. If the contents change but the size, permissions and mod time stay the same, the checksum will change.
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)
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 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,
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)
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)
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)
Discussion started by: paragnehete
2 Replies
LEARN ABOUT HPUX
sum
sum(1) General Commands Manual sum(1)NAME
sum - print checksum and block or byte count of file(s)
SYNOPSIS
[file ...]
Remarks
is obsolescent and should not be used in new applications that are intended to be portable between systems. Use instead (see cksum(1)).
DESCRIPTION
calculates and prints to standard output a checksum for each named file, and also prints the size of the file in 512 byte blocks, rounded
up.
The default algorithm is a 16-bit sum of the bytes in which overflow is ignored. Alternate algorithms can be selected with the and
options.
Standard input is used if no file names are given.
is typically used to verify data integrity when copying files between systems.
Options
recognizes the following options:
Use an alternate algorithm in which the 16-bit sum is right rotated
with each byte in computing the checksum.
Use the 32-bit cyclical redundancy check (CRC) algorithm used by
RETURN VALUE
returns the following values upon completion:
All files were processed successfully.
One or more files could not be read or some other error occurred.
If an inaccessible file is encountered, continues processing any remaining files, but the final exit status is affected.
DIAGNOSTICS
Read error conditions are indistinguishable from end of file on most devices; check the block or byte count.
WARNINGS
This command is likely to be withdrawn from X/Open standards. Applications using this command might not be portable to other vendors'
platforms. The usage of cksum(1) is recommended.
SEE ALSO cksum(1), wc(1).
STANDARDS CONFORMANCE sum(1)