This commit is contained in:
nicolson%netscape.com 2002-08-28 17:57:48 +00:00
Родитель 273e3f23ea
Коммит 1fc9da0bde
1 изменённых файлов: 2 добавлений и 7 удалений

Просмотреть файл

@ -68,15 +68,10 @@ import org.mozilla.jss.crypto.SecretKeyFacade;
* *
* <li>getCertificateChain only returns a single certificate. That's because * <li>getCertificateChain only returns a single certificate. That's because
* we don't have a way to build a chain from a specific slot--only from * we don't have a way to build a chain from a specific slot--only from
* the set of all slots. Kannan Bhoopathy has already indicated that he * the set of all slots.
* wants to get back whole chains from the KeyStore API, so this implementation
* is incorrect. Question: is it better to do an NSS-wide cert chain lookup
* and risk returning some certs from different tokens, or to only return
* the one cert that is guaranteed to be on the token? Probably the former,
* but I need confirmation.
* *
* <li>getCreationDate is unsupported because NSS doesn't store that * <li>getCreationDate is unsupported because NSS doesn't store that
* information. Hopefully nobody cares about this. * information.
* *
* <li>getKey first looks for a private/symmetric key with the given label. * <li>getKey first looks for a private/symmetric key with the given label.
* It returns the first one it finds. If it doesn't find one, it looks for a * It returns the first one it finds. If it doesn't find one, it looks for a