An Overview of Cryptography in Java, Part 4: Permissions, Documentation, and Export Issues Oregon

provided by: 
Originally published at Internet.com

With the new JCE 1.2.1, customizing securitymanager may be necessary in order to properly implement your provider. Sun also asks that providers carefully document services for users, and although JCE 1.2.1 hallmarks availability of these cryptography tools outside of the United States, implementing them in this way adds a layer of complexity.

Permissions

Your provider may need permissions from securitymanager in order to run. java.io.FilePermission is needed when authenticating JCE 1.2.1, java.lang.RuntimePermission is needed for a provider to get its own protection domain, and java.security.SecurityPermisions are necessary to set provider properties. These permissions are necessary when the JCE 1.2.1 framework is not an installed extension or when a client does not install your provider as an installed extension.

Documentation

The types of algorithms and other services implemented by your provider and instructions for installation need to be included as part of your provider documentation, especially if you plan on selling or sharing your provider online. This should at least include the name programs should use to refer to your provider, which is currently case sensitive.
...

Read article at Internet.com site