Support for wildcards in policy?

Jul 9, 2007 at 5:20 PM
Are wildcards supported within folder names specified in policies? If yes, are there any special coding techniques when listing these names in the policy? The documentation appears to be silent on this.

Example: An application creates a folder name that varies slightly for each user (e.g., Name____). This folder should be marked for encryption, but the parent folder should not be marked. It is possible to add names with wildcards, Name* or Name????, to the policy (Folders to Encrypt properties), but they are ignored when policy is applied.

Cipher.exe supports wildcards.
Jul 10, 2007 at 6:39 PM
The tool does not support wildcards. It does support using environment variables though, so if you can get an environment variable set with the appropriate folder path, you can include that environment variable in either the encrypt or do not encrypt list. If the environment variable is not set, nothing will be added to the respective list.