Skip Navigation Links | |
Exit Print View | |
![]() |
Developer's Guide to Oracle Solaris Security Oracle Solaris 10 8/11 Information Library |
1. Oracle Solaris Security for Developers (Overview)
2. Developing Privileged Applications
3. Writing PAM Applications and Services
4. Writing Applications That Use GSS-API
7. Writing Applications That Use SASL
8. Introduction to the Oracle Solaris Cryptographic Framework
9. Writing User-Level Cryptographic Applications and Providers
10. Using the Smart Card Framework
A. Sample C-Based GSS-API Programs
D. Source Code for SASL Example
F. Packaging and Signing Cryptographic Providers
Packaging Cryptographic Provider Applications and Modules
Complying with U.S. Government Export Laws
Packaging User-Level Provider Applications
Packaging Kernel-Level Provider Modules
Adding Signatures to Providers
To Request a Certificate for Signing a Provider
The following example demonstrates verification with the assumption that the certificate is in the default directory, /etc/crypto/certs/MyCompany.
% elfsign verify \ -e /path/to/MyProvider.so.1 elfsign: verification of /path/to/MyProvider.so.1 passed
The following example demonstrates storage of the certificate in a non-default directory.
% elfsign verify \ -c /path/to/MyCerts \ -e /path/to/MyProvider.so.1 elfsign: verification of /path/to/MyProvider.so.1 passed
The following example demonstrates verification of a provider that has been signed with a restricted certificate.
% elfsign verify \ -e /path/to/MyRestrictedProvider.so.1 elfsign: verification of /path/to/MyRestrictedProvider.so.1 passed, \ but restricted.