From 3a0bcb0fb2d556326d1867bce28c89b6347275ec Mon Sep 17 00:00:00 2001 From: "glen.beasley%sun.com" Date: Thu, 4 Jul 2002 00:36:52 +0000 Subject: [PATCH] verify certificate in memory method --- .../jss/org/mozilla/jss/CryptoManager.java | 89 ++++++++---- security/jss/org/mozilla/jss/PK11Finder.c | 135 +++++++++++++----- 2 files changed, 156 insertions(+), 68 deletions(-) diff --git a/security/jss/org/mozilla/jss/CryptoManager.java b/security/jss/org/mozilla/jss/CryptoManager.java index 4eccbc910a83..2dca6305e762 100644 --- a/security/jss/org/mozilla/jss/CryptoManager.java +++ b/security/jss/org/mozilla/jss/CryptoManager.java @@ -1,27 +1,27 @@ -/* +/* * The contents of this file are subject to the Mozilla Public * License Version 1.1 (the "License"); you may not use this file * except in compliance with the License. You may obtain a copy of * the License at http://www.mozilla.org/MPL/ - * + * * Software distributed under the License is distributed on an "AS * IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or * implied. See the License for the specific language governing * rights and limitations under the License. - * + * * The Original Code is the Netscape Security Services for Java. - * + * * The Initial Developer of the Original Code is Netscape - * Communications Corporation. Portions created by Netscape are + * Communications Corporation. Portions created by Netscape are * Copyright (C) 1998-2000 Netscape Communications Corporation. All * Rights Reserved. - * + * * Contributor(s): - * + * * Alternatively, the contents of this file may be used under the * terms of the GNU General Public License Version 2 or later (the - * "GPL"), in which case the provisions of the GPL are applicable - * instead of those above. If you wish to allow use of your + * "GPL"), in which case the provisions of the GPL are applicable + * instead of those above. If you wish to allow use of your * version of this file only under the terms of the GPL and not to * allow others to use your version of this file under the MPL, * indicate your decision by deleting the provisions above and @@ -52,12 +52,12 @@ import org.mozilla.jss.provider.java.security.JSSMessageDigestSpi; * Initialization is done with static methods, and must be done before * an instance can be created. All other operations are done with instance * methods. - * @version $Revision: 1.8 $ $Date: 2002/07/03 23:46:02 $ + * @version $Revision: 1.9 $ $Date: 2002/07/04 00:36:51 $ */ public final class CryptoManager implements TokenSupplier { /** - * CertUsage options for validation + * CertUsage options for validation */ public final static class CertUsage { private int usage; @@ -74,7 +74,7 @@ public final class CryptoManager implements TokenSupplier public String toString() { return name; } - + // certUsage, these must be kept in sync with nss/lib/certdb/certt.h public static final CertUsage SSLClient = new CertUsage(0, "SSLClient"); public static final CertUsage SSLServer = new CertUsage(1, "SSLServer"); @@ -126,7 +126,7 @@ public final class CryptoManager implements TokenSupplier /** * This class enumerates the possible modes for FIPS compliance. */ - public static final class FIPSMode { + public static final class FIPSMode { private FIPSMode() {} /** @@ -439,8 +439,8 @@ public final class CryptoManager implements TokenSupplier public String ocspResponderURL = null; /** - * The nickname of the cert to trust (expected) to - * sign the OCSP responses. + * The nickname of the cert to trust (expected) to + * sign the OCSP responses. * Only checked when the OCSPResponder value is set. */ public String ocspResponderCertNickname = null; @@ -461,7 +461,7 @@ public final class CryptoManager implements TokenSupplier * be initialized. Only the Java portions of JSS will be * initialized. This should only be used if NSS has been initialized * elsewhere. - * + * *

Specifically, the following components will not be * configured by CryptoManager.initialize if this flag is set: *