CHANGES
-------

Version 1.9a
------------
Fixed a problem where revoke and irevoke did not match account names
correctly with the one specified on the command line result in a
"no change" message. For example irevoke users:w dir1 would result
in "no change", but irevoke users*:w dir1 would work. This is fixed.


Version 1.9
-----------
Listacl has a new option -usepriv which will automatically take
ownership of files which it can't read the permissions of. This occurs
when you are not owner and don't have at least read permissons. The
previous owner is restored to the original state. You need take
ownership and se_restore_name (restore files and directories)
priviliges. -usepriv will be added to future versions of grant, igrant,
revoke, and irevoke.

When setting "list" permissions on a directory, igrant would set the
appropriate permissions, but explorer would complain that the permissions
are missing or corrupt. This is now fixed.

Added an option "-addpriv" to setowner which will assist in taking
ownership of files and directories when recursing. When
specifying this option you allow setowner to automatically give the
currently logged in user account rights on necessary files
and directories it can't read (because they are too deep in a tree
in which you have no rights along the way). Existing rights are not
overwritten. You must have appropriate access rights when using this
option (take ownership and possibly se_restore_name). This option is
most helpful when you need to take over a directory subtree you no
longer have rights to.


Version 1.8
-----------
A new option "-dirsonly" was added to listacl (at the request of
RichardA@Health.State.OK.US).

Recursion is more Microsoft/DOS like. Directories are treated differently
during recursion. Instead of matching the directory name to a file mask,
all directories are recursed into using the specified mask to match
against files.

Setowner now correctly set ownership on files which it doesn't own
and doesn't have the take-ownership file permission assigned to it.

revoke and irevoke now have the user:perms syntax for specifying
file and directoy permissions. however, they are still limited to
a single user account.




Version 1.7
-----------
Up to 30 users may now be specified on the command line to igrant and
grant. This fixes the problem with making permission changes to many
files and multiple users which can take a really long time. The reason
it was taking so long is the way MS designed NTFS. Permission reads
(even for a single file) can sometimes take several seconds. Writes are
much faster. This change will allow you to make permission changes
in batches of users which can reduce the number of permission reads from
the filesystem.

Version 1.6
-----------
Added -clear and -replace options to GRANT and IGRANT. These let you
set and replace user permissions. -clear will wipe out all permissions
first, then add the specified rights. -replace will replace any
existing permissions a specified user may already have on the files.

Bugs were fixed in IREVOKE and IGRANT. Thanks to Mario Eduardo
(Mario.Eduardo@vu-wien.ac.at) for reporting the bug. Certain ACEs on
directories would be ignored and "unknow ACE type" would be printed. This
is now fixed.

Added wildcard matching to user and group names in IREVOKE and REVOKE.
This allows you to revoke permissions to several accounts and groups
at once. Be careful, you can also do destructive things like 'REVOKE
-r all * *' to remove all permissions on all files from every account
and group across the filesystem! Wildcards for matching users may contain
a '*' to match any number of characters, a '?' to match a single character,
[0-9] or [a-z] to match ranges of characters, etc.




