526 
 527 
 528 
 529 
 530        +--------------------+-----------------+
 531        |  ATTRIBUTE TYPE    | ATTRIBUTE VALUE |
 532        +--------------------+-----------------+
 533        |Interface Stability | See below       |
 534        +--------------------+-----------------+
 535 
 536 
 537        The start, stop, and refresh options are Private interfaces.  All other
 538        options are Evolving. The utility name is Stable.
 539 
 540 SEE ALSO
 541        logadm(1M), svcadm(1M), syslogd(1M), libpkcs11(3LIB), exec_attr(4),
 542        prof_attr(4), attributes(5), smf(5), random(7D)
 543 
 544 
 545 
 546 
 547        Solaris Security for Developer's Guide
 548 
 549 NOTES
 550        If a hardware provider's policy was made explicitly (that is, some of
 551        its mechanisms were disabled) and the hardware provider has been
 552        detached, the policy of this hardware provider is still listed.
 553 
 554 
 555        cryptoadm assumes that, minimally, a 32-bit shared object is delivered
 556        for each user-level provider. If both a 32-bit and 64-bit shared object
 557        are delivered, the two versions must provide the same functionality.
 558        The same mechanism policy applies to both.
 559 
 560 
 561 
 562                                September 1, 2009                 CRYPTOADM(1M)

 526 
 527 
 528 
 529 
 530        +--------------------+-----------------+
 531        |  ATTRIBUTE TYPE    | ATTRIBUTE VALUE |
 532        +--------------------+-----------------+
 533        |Interface Stability | See below       |
 534        +--------------------+-----------------+
 535 
 536 
 537        The start, stop, and refresh options are Private interfaces.  All other
 538        options are Evolving. The utility name is Stable.
 539 
 540 SEE ALSO
 541        logadm(1M), svcadm(1M), syslogd(1M), libpkcs11(3LIB), exec_attr(4),
 542        prof_attr(4), attributes(5), smf(5), random(7D)
 543 
 544 
 545 

 546        Solaris Security for Developer's Guide
 547 
 548 NOTES
 549        If a hardware provider's policy was made explicitly (that is, some of
 550        its mechanisms were disabled) and the hardware provider has been
 551        detached, the policy of this hardware provider is still listed.
 552 
 553 
 554        cryptoadm assumes that, minimally, a 32-bit shared object is delivered
 555        for each user-level provider. If both a 32-bit and 64-bit shared object
 556        are delivered, the two versions must provide the same functionality.
 557        The same mechanism policy applies to both.
 558 
 559 
 560 
 561                                September 1, 2009                 CRYPTOADM(1M)