 
|
|
CipherSafe.NET™ Wish List The following features are being considered for future releases of CipherSafe.NET™: Linked application profiles
Description:
It would be helpful to allow several application profiles to be defined as "linked",
in which case making a change in one profile would be automatically reflected in all linked profiles.
For example, if a new value is added to a profile, it should be automatically added to all other
applications linked to this profile. This can make it easier for application administrators to
manage shared settings between multiple applications.
Remote administration
Description:
Add capability to administer application profiles on remote systems.
This feature should be configurable,
i.e. the system may be set up to disallow remote access.
Support short paths
Description:
Allow CipherSafe.NET™ to identifying applications by file names instead of full paths.
This will enable the same module
(such as a class library executing from different Bin folders of various ASP.NET
applications) to access the same application profile.
To limit security vulnerability,
this application type can be used in conjunction with the strong name feature.
Support application identities based on strong names
Description:
Allow all applications signed with the same public/private key
to access the same application profile.
Set CipherSafe registry key permissions to allow access by Key Manager
Description:
If the Key Manager service is set up to run under unprivileged account,
it will fail because it will not have the right to read and/or write to
the CipherSafe registry hive.
Currently, administrators must set up permissions on the registry
manually; it would be better if this has been done by the installer.
If you have additional suggestions or comments, please let us know.
|