Network Security Services

Shopping on line can be easy, simple and save you lots of money. It can also take a lot of your time, frustrate you, and result in unwanted purchases. Now the same can be said for regular high street shopping, but with the vast opportunity presented by the Internet it will pay you to spend a few minutes reading this and understanding how to better optimize your Network Security Services shopping experience:

1. Compare - without doubt the biggest advantage that the Network Security Services offers shoppers today is the ability to compare thousands of Network Security Services at a time. This is a great thing, but not necessarily all the time! Too much can be daunting at times so take advantage of the great comparison sites and where possible let them do the hard work for you.

2. Research - if it has been said it will be on the internet. Ignorance is no longer a justifiable reason for buying the wrong thing. Take the time to research in detail everything that you could possible want to know about

3. Testimonials - don't know anybody that has bought a Network Security Services? Wrong! If the Network Security Services is good the internet will let you know. Use the Internet as a friend and get testimonials before you buy.

4. Questions - Got a question about Network Security Services then search the Forums, FAQ's, Blogs etc. Don't be afraid to ask .....

5. Reputation - Never heard of the company selling Network Security Services? Don't worry, no reason why you should know every company in the world, but you know someone that does! Use the internet to find out what people are saying about Network Security Services and build up a picture of their reputation for sales, returns, customer service, delivery etc.

6. Returns - still worried that even after all of the above your Network Security Services wont be what you want? Check out the returns policy. There is so much competition now that someone, somewhere is bound to offer the terms that you are comfortable with.

7. Feedback - happy with your Network Security Services then let people know, after all you are depending on others people input in your buying decision, so why not give a little back.

8. Security - check for the yellow padlock on the Network Security Services site before you buy, and the s after http:/ /i.e. https:// = a secure site

9. Contact - got a question about Network Security Services, or want to leave a comment then check out the sites contact page. Reputable companies have them and respond.

10. Payment - ready to pay for your Network Security Services, then use your credit card or PayPal! Be aware of companies that don't accept them, there may be genuine reasons but given the huge amount of choice you have when buying online there is no reason at all not to buy via credit card or PayPal.

Network Security Services (NSS) is a set of Library (computing) designed to support cross-platform development of security-enabled client and server applications. NSS provides a complete open-source implementation of crypto libraries supporting Secure Sockets Layer and S/MIME.

History NSS is a descendant of the libraries developed when Netscape invented the SSL security protocol.

Applications that use NSS NSS is used by AOL, Red Hat, Sun Microsystems, and other companies in a variety of products, including the following:

Mozilla client products, including Mozilla Firefox, and Mozilla Thunderbird.
Netscape Browser
AOL Communicator and AOL Instant Messenger
Open source client applications such as Novell Evolution, Pidgin (software), and OpenOffice.org 2.0.
Server products from Red Hat: Red Hat Directory Server, Red Hat Certificate System, and the mod nss SSL module for the Apache web server.
Sun Java products from the Sun Java Enterprise System, including Sun Java System Web Server, Sun Java System Directory Server, Sun Java System Portal Server, Sun Java System Messaging Server, and Sun Java System Application Server.

Technology NSS includes a framework to which developers and OEMs can contribute patches, such as assembler code, to optimize performance on their platforms. NSS 3.x has been certified on 18 platforms.

For more detailed information about NSS, see the NSS Project Page and NSS FAQ.

Source code for a Java interface to NSS is available in the Mozilla CVS tree. For details, see Network Security Services for Java.

NSS makes use of Netscape Portable Runtime (NSPR), a platform-neutral open-source API for system functions designed to facilitate cross-platform development. Like NSS, NSPR has been battle-tested in multiple products. For more information, see NSPR Project Page.

The latest source code is available for free worldwide from http://www.mozilla.org and its mirror sites.

NSS comes with an extensive and growing set of documentation, including introductory material, API references, man pages for command-line tools, and sample code.

NSS is available as source and shared (dynamic) libraries. Every NSS release is backward compatible with previous releases, allowing NSS users to upgrade to the new NSS shared libraries without recompiling or relinking their applications.Open-Source Licensing and Distribution

Complete Software Development KitIn addition to libraries and APIs, NSS provides security tools required for debugging, diagnostics, certificate and key management, cryptography module management, and other development tasks.

Interoperability and Open Standards NSS supports a range of security standards, including the following:

Transport Layer Security v2 and v3. The Secure Sockets Layer (SSL) protocol allows mutual authentication between a client and server and the establishment of an authenticated and encrypted connection.
Transport Layer Security v1 (RFC 2246). The Transport Layer Security (TLS) protocol from the Internet Engineering Task Force will eventually supersede SSL while remaining backward-compatible with SSL implementations.
The following PKCS standards are supported in NSS:

PKCS #1. RSA standard that governs implementation of public-key cryptography based on the RSA algorithm.
PKCS #3. RSA standard that governs implementation of Diffie-Hellman key agreement.
PKCS #5. RSA standard that governs password-based cryptography, for example to encrypt private keys for storage.
PKCS #7. RSA standard that governs the application of cryptography to data, for example digital signatures and digital envelopes.
PKCS #8. RSA standard that governs the storage and encryption of private keys.
PKCS #9. RSA standard that governs selected attribute types, including those used with PKCS #7, PKCS #8, and PKCS #10.
PKCS #10. RSA standard that governs the syntax for certificate requests.
PKCS #11. RSA standard that governs communication with cryptographic tokens (such as hardware accelerators and smart cards) and permits application independence from specific algorithms and implementations.
PKCS #12. RSA standard that governs the format used to store or transport private keys, certificates, and other secret material.

S/MIME (RFC 2311 and RFC 2633). IETF message specification (based on the popular Internet MIME standard) that provides a consistent way to send and receive signed and encrypted MIME data.
X.509. International Telecommunication Union standard that governs the format of certificates used for authentication in public-key cryptography.
Online Certificate Status Protocol (RFC 2560). The Online Certificate Status Protocol (OCSP) governs real-time confirmation of certificate validity.
PKIX Certificate and CRL Profile (RFC 3280). The first part of the four-part standard under development by the Public-Key Infrastructure (X.509) working group of the IETF (known as PKIX) for a public-key infrastructure for the Internet.
RSA, Digital Signature Algorithm, Elliptic Curve DSA, Diffie-Hellman key exchange, EC Diffie-Hellman, Advanced Encryption Standard, Triple DES, Data Encryption Standard, RC2, RC4, SHA hash functions, MD2, MD5, HMAC: Common cryptographic algorithms used in public-key and symmetric-key cryptography.
Federal Information Processing Standard 186-2 pseudorandom number generator.

For complete details, see the Encryption Technologies page of the NSS site.

FIPS 140 Validation and NISCC Testing The NSS software crypto module has been validated three times (1997, 1999, and 2002) for conformance to FIPS 140 at Security Levels 1 and 2.

NSS was the first open source cryptographic library to receive FIPS 140 validation.

The NSS libraries passed the NISCC TLS/SSL and S/MIME test suites (1.6 million test cases of invalid input data).

For more information (including certificate numbers and links), see the NSS FIPS page.

Hardware support NSS supports the PKCS11 interface for hardware acceleration. Since leading accelerator vendors such as SafeNet Inc. and nCipher also support this interface, NSS-enabled applications can support a wide variety of hardware accelerators.

NSS supports the PKCS #11 interface for smart card integration. Applications that use the PKCS #11 interface provided by NSS will therefore support smart cards from leading vendors such as ActivIdentity, Inc., Litronic, and SecureID Technologies that also support the PKCS #11 interface.

Java support Network Security Services for Java (JSS) is a Java interface to NSS. It supports most of the security standards and encryption technologies supported by NSS. JSS also provides a pure Java interface for ASN.1 types and BER/DER encoding.

License NSS is triple-licensed under the Mozilla Public License, the GNU General Public License, and the LGPL.

External links

NSS Introduction
NSS Overview
SSL Reference
NSS tools
NSS test suite
S/MIME toolkit
SSL toolkit
JSS toolkit

Mozilla client products, including Mozilla Firefox, and Mozilla Thunderbird.
Netscape Browser
AOL Communicator and AOL Instant Messenger
Open source client applications such as Novell Evolution, Pidgin (software), and OpenOffice.org 2.0.
Server products from Red Hat: Red Hat Directory Server, Red Hat Certificate System, and the mod nss SSL module for the Apache web server.
Sun Java products from the Sun Java Enterprise System, including Sun Java System Web Server, Sun Java System Directory Server, Sun Java System Portal Server, Sun Java System Messaging Server, and Sun Java System Application Server.

Transport Layer Security v2 and v3. The Secure Sockets Layer (SSL) protocol allows mutual authentication between a client and server and the establishment of an authenticated and encrypted connection.
Transport Layer Security v1 (RFC 2246). The Transport Layer Security (TLS) protocol from the Internet Engineering Task Force will eventually supersede SSL while remaining backward-compatible with SSL implementations.
The following PKCS standards are supported in NSS:

PKCS #1. RSA standard that governs implementation of public-key cryptography based on the RSA algorithm.
PKCS #3. RSA standard that governs implementation of Diffie-Hellman key agreement.
PKCS #5. RSA standard that governs password-based cryptography, for example to encrypt private keys for storage.
PKCS #7. RSA standard that governs the application of cryptography to data, for example digital signatures and digital envelopes.
PKCS #8. RSA standard that governs the storage and encryption of private keys.
PKCS #9. RSA standard that governs selected attribute types, including those used with PKCS #7, PKCS #8, and PKCS #10.
PKCS #10. RSA standard that governs the syntax for certificate requests.
PKCS #11. RSA standard that governs communication with cryptographic tokens (such as hardware accelerators and smart cards) and permits application independence from specific algorithms and implementations.
PKCS #12. RSA standard that governs the format used to store or transport private keys, certificates, and other secret material.

S/MIME (RFC 2311 and RFC 2633). IETF message specification (based on the popular Internet MIME standard) that provides a consistent way to send and receive signed and encrypted MIME data.
X.509. International Telecommunication Union standard that governs the format of certificates used for authentication in public-key cryptography.
Online Certificate Status Protocol (RFC 2560). The Online Certificate Status Protocol (OCSP) governs real-time confirmation of certificate validity.
PKIX Certificate and CRL Profile (RFC 3280). The first part of the four-part standard under development by the Public-Key Infrastructure (X.509) working group of the IETF (known as PKIX) for a public-key infrastructure for the Internet.
RSA, Digital Signature Algorithm, Elliptic Curve DSA, Diffie-Hellman key exchange, EC Diffie-Hellman, Advanced Encryption Standard, Triple DES, Data Encryption Standard, RC2, RC4, SHA hash functions, MD2, MD5, HMAC: Common cryptographic algorithms used in public-key and symmetric-key cryptography.
Federal Information Processing Standard 186-2 pseudorandom number generator.

NSS Introduction
NSS Overview
SSL Reference
NSS tools
NSS test suite
S/MIME toolkit
SSL toolkit
JSS toolkit