History log of /titanic_53/usr/src/lib/libelfsign/common/elfcertlib.c (Results 1 – 5 of 5)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: titanic_53.0, titanic_51.4, titanic_52.1, titanic_51.3, titanic_52.0, titanic_50.16, titanic_51.2, titanic_50.15, titanic_51.1, titanic_51.0, titanic_50.14, titanic_50.13, titanic_50.12, titanic_50.11, titanic_50.10, titanic_50.9, titanic_50.8, titanic_50.7, titanic_50.6, titanic_50.5, titanic_50.4, titanic_50.3, titanic_50.2, titanic_50.1, titanic_50.0
# 9f0bc604 09-Jan-2010 Wyllys Ingersoll <wyllys.ingersoll@sun.com>

6914632 libkmf has unused functions that should be removed
6914613 libelfsign still uses deprecated libkmf API


# 73556491 07-Oct-2009 Anthony Scarpino <Anthony.Scarpino@Sun.COM>

PSARC/2009/447 Kernel Cryptographic Framework support for FIPS 140-2
6703950 Solaris cryptographic framework needs to implement changes for FIPS-140-2 compliance


# 8bab47ab 28-Sep-2009 John.Zolnowsky@Sun.COM <none@none>

6606040 elfsign should use new KMF APIs


# 2225707c 18-Jul-2009 Valerie Bubb Fenwick <Valerie.Fenwick@Sun.COM>

6852240 libelfsign should use pkcs11_softtoken instead of OpenSSL for FIPS-140 integrity checking
6851814 tools elfsign is unnecessarily linked against pkcs11_softtoken


# df8bdeb3 05-Oct-2007 johnz <none@none>

6592898 open elfsign, libelfsign