Netscape Security Services (NSS) A set of libraries designed to support
cross-platform development of security-enabled communications applications.
Applications built using the NSS libraries support the Secure Sockets Layer (SSL)
protocol for authentication, tamper detection, and encryption, and the PKCS #11
protocol for cryptographic token interfaces. Netscape uses NSS to support these
features in a wide range of products, including Certificate Management System.
NSS is also available separately as a software development kit.
nonrepudiation The inability by the sender of a message to deny having sent the
message. A digital signature provides one form of nonrepudiation.
object signing A technology that allows software developers to sign Java code,
JavaScript scripts, or any kind of file and allows users to identify the signers and
control access by signed code to local system resources.
object-signing certificate A certificate whose associated private key is used to
sign objects using the technology known as object signing.
one-way hash A number of fixed length generated from data of arbitrary length
with the aid of a hashing algorithm. The number (also called a message digest) has
two characteristics: (1) It is unique to the hashed data. Any change in the data, even
deleting or altering a single character, results in a different value. (2) The content of
the hashed data cannot, for all practical purposes, be deduced from the hash.
password-based authentication Confident identification by means of a name
and password. See also authentication, certificate-based authentication.
PKCS #7 The public-key cryptography standard that governs signing and
encryption.
PKCS #10 The public-key cryptography standard that governs certificate
requests.
PKCS #11 The public-key cryptography standard that governs cryptographic
tokens such as smart cards.
PKCS #11 module A driver for a cryptographic device that provides
cryptographic services, such as encryption and decryption, via the PKCS #11
interface. A PKCS #11 module (also called a cryptographic module or cryptographic
service provider) can be implemented in either hardware or software. A PKCS #11
module always has one or more slots, which may be implemented as physical
hardware slots in some form of physical reader (for example, for smart cards) or as
Glossary
845
Need help?
Do you have a question about the NETSCAPE MANAGEMENT SYSTEM 4.5 and is the answer not in the manual?