Index of /pub/security/nss/releases/ Type Name Size Last Modified; Dir. Dir: NSS310RTM/ Dir: NSS3111RTM/ Dir: NSS3112RTM/. Previous Post NSS Mathematics In Action 5A FULL SOLUTION. DOWNLOAD LINK ↓ ↓ ↓ CLICK HERE →CH 1 CLICK HERE →CH 2 CLICK HERE →CH 3 CLICK HERE →CH 4 CLICK HERE →CH 5. Nuclear Decay Workbook Answers Nube Noviembre Calf. Nse5 Fmg 5 4 Certification Torrent Fortinet Fortimanager. Nss Mathematics In Action 6b Answer. Download New Star Soccer 5 1.12 for Windows for free, without any viruses, from Uptodown. Try the latest version of New Star Soccer 5 2012 for Windows.
You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content ishighly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. Ifthere are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.
Primary Newsgroup: mozilla.dev.tech.crypto
Alternate Newsgroup: mozilla.dev.tech.crypto
Network Security Services (NSS) is a set of libraries designed to supportcross-platform development of security-enabled client and server applications. Applicationsbuilt with NSS can supportSSLv2 and v3, TLS,PKCS#5, PKCS #7,PKCS#11, PKCS #12, S/MIME,X.509v3 certificates, and other security standards. For detailed informationon standards supported, see Overview of NSS.
NSS is available under the Mozilla Public License, the GNU General PublicLicense, and the GNU Lesser General Public License. For information ondownloading NSS releases as tar files, see Download PKI Source.
To participate in ongoing technical discussions related to NSS, tunein to the newsgroup using one of the above links.
NSS 3.11.4 has been released. We are working on NSS 3.12.
NSS 3.11.4 is the version that we submitted to NIST for FIPS 140-2 validation.The CVS tag is NSS_3_11_4_RTM. NSS 3.11.4 may be used with NSPR 4.6.4 (CVS tagNSPR_4_6_4_RTM) or later.
NSS 3.11.4 is a patch release for NSS 3.11. For the list of the bugs thathave been fixed in NSS 3.11.4, seeNSS 3.11.4 Release Notes.
NSS 3.10 was completed on 27 April 2005. The CVS tag is NSS_3_10_RTM. It isthe first release in which the DBM library (mozilla/dbm andmozilla/security/dbm) became part of the NSS source tree. NSS 3.10 may beused with NSPR 4.5.1 (CVS tag NSPR_4_5_1_RTM) or later. We will post therelease notes here soon.
NSS 3.9.5 is the latest patch release for NSS 3.9. The CVS tag isNSS_3_9_5_RTM.
The new features and enhancements in NSS 3.9 include GeneralizedTimesupport, RFC 3280 compliant name constraints, and the ability to listduplicate certificate instances in multiple tokens. NSS 3.9 passesall the NISCCSSL/TLSand S/MIMEtests (1.6 million test cases of invalid input data) without crashesor memory leaks. We recommend that all NSS customers upgrade to NSS3.9 in the next release of your product. For details, seeNSS 3.9 Release Notes.
NSS 3.7.7 is a patch release for NSS 3.7. For the list of the bugs thathave been fixed in NSS 3.7.7, see NSS 3.7.7 Release Notes.
NSS 3.7.5 is a patch release for NSS 3.7. For the list of the bugs thathave been fixed in NSS 3.7.5, seeNSS 3.7.5 Release Notes.
The new features and enhancements in NSS 3.8 include the SHA-256, SHA-384,and SHA-512 algorithms, enhanced smartcard support, and the elliptic curvecryptography code (not compiled by default) contributed by Sun Labs. Fordetails, see NSS 3.8 Release Notes.
NSS 3.7.3 is a patch release for NSS 3.7. For the list of the bugs thathave been fixed in NSS 3.7.3, see NSS 3.7.3 Release Notes.
NSS 3.7.2 is a patch release for NSS 3.7. For the list of the bugs thathave been fixed in NSS 3.7.2, seeNSS 3.7.2 Release Notes.
NSS 3.4.3 is a patch release for NSS 3.4. For the list of the bugs thathave been fixed in NSS 3.4.3, seeNSS 3.4.3 Release Notes.
Recently a timing-based attack on SSL/TLS implementations of CBC mode blockcipher suites was disclosed. At present the implementation of SSL and TLS in NSS issusceptible to this method. The flaw is exploited on the recipient ofsensitive data, which is normally servers. Servers are vulnerable tothe attack only if they implement all of the following:
We have implemented a countermeasure and will release NSS patch releasessoon. Until updated NSS libraries are available, we recommend the followingaction:
For more information, please see our article on this security flaw.
NSS 3.7.1 is a patch release for NSS 3.7. For the list of the bugs thathave been fixed in NSS 3.7.1, seeNSS 3.7.1 Release Notes.
The new features and enhancements in NSS 3.7 include a new version of theNSS certificate database that supports large CRLs and multiple emailaddresses for the subject of a certificate. For details, seeNSS 3.7 Release Notes.
NSS 3.6.1 is a patch release for NSS 3.6. For the list of the bugs thathave been fixed in NSS 3.6.1, seeNSS 3.6.1 Release Notes.
The new features and enhancements in NSS 3.6 include new certificate handlingand SSL functions, better certificate path construction, significantlyimproved CRL performance and memory usage, better SSL client authenticationperformance, and PKCS #11 session logging. For details, seeNSS 3.6 Release Notes.
NSS 3.5 is an interim release created for Mozilla 1.0.1 and Netscape 7.We recommend that other NSS clients upgrade to NSS 3.6.
NSS 3.4.2 is a patch release for NSS 3.4. For the list of the bugs thathave been fixed in NSS 3.4.2, seeNSS 3.4.2 Release Notes.
NSS 3.4.1 is a patch release for NSS 3.4. For the list of the bugs thathave been fixed in NSS 3.4.1, seeNSS 3.4.1 Release Notes.
NSS 3.4 contains a partial implementation of the core NSS 4.0 (code name Stan)functions and supports the new TLS AES ciphersuites. For details, seeNSS 3.4 Release Notes.
NSS 3.3.2 is a patch release for NSS 3.3. For the list of the bugsthat have been fixed in NSS 3.3.2, see NSS3.3.2 Release Notes.
NSS 3.3.1 is a patch release for NSS 3.3. For the list of the bugsthat have been fixed in NSS 3.3.1, see NSS3.3.1 Release Notes.
NSS 3.3 enables JSS (3.1 or newer) to use NSS shared libraries and implementsfive new DHE cipher suites for SSL/TLS on the client side. For details,see NSS 3.3 Release Notes.
Source code for a Java interface to NSS is available in the MozillaCVS tree. For details, see Network Security Servicesfor Java.
NSS 3.3 source is available via CVS and maybe viewed in HMTL (via the LXR tool) at http://lxr.mozilla.org/mozilla/source/security/nss/.
NSS 3.2.1 provides improved SSL performance and fixes bugs in pk12utiland some certificate query operations. For details, see NSS3.2.1 Release Notes.
NSS 3.2.1 also facilitates simplified build instructions. For details,see Build Instructions for NSS 3.2.1 Release.For background information on the build system and proposals for futurechanges, see The NSS Build System: Historyand Future Directions.
NSS 3.2 provided support for shared libraries for the first time. For details,see NSS 3.2 Release Notes.
Applications that use only the NSS 3.2Public Functions exported by the NSS 3.2 DLLs are guaranteed to workwith future versions of the shared libraries.
See S/MIME Toolkit for information about NSS librariesdesigned to support cross-platform development of S/MIME applications.Originally created to support S/MIME in Communicator 4.x and Personal SecurityManager (PSM), these libraries form the basis of a new S/MIME Toolkit forcross-platform development of S/MIME applications.
See SSL/TLS for information about NSS libraries designedto support cross-platform development of SSL- and TLS-enabled applications.These libraries form the basis of the SSL module.
Background information:
History:
NSS APIs:
Tools, testing, and other technical details:
cert7.db
database.cert7.db
.PKCS #11 information for implementors of cryptographic modules:
CA certificates pre-loaded into NSS
NSS is built on top of Netscape Portable Runtime (NSPR); developers usingNSS must call some NSPR functions. For information on NSPR, see the following:
The CVS tags for various NSS releases can be found in theNSS release notes.
NSS source code is in the mozilla/security/coreconf/
andmozilla/security/nss/
directories.
News: NewSoftSerial is in the core! Starting with Arduino 1.0 (December, 2011), NewSoftSerial has replaced the old SoftwareSerial library as the officially supported software serial library. This means that if you have 1.0 or later, you should not download this library. To port your code to 1.0, simply change all NewSoftSerial references to SoftwareSerial.
NewSoftSerial is the latest of three Arduino libraries providing “soft” serial port support. It’s the direct descendant of ladyada’s AFSoftSerial, which introduced interrupt-driven receives – a dramatic improvement over the polling required by the native SoftwareSerial.
Without interrupts, your program’s design is considerably restricted, as it must continually poll the serial port at very short, regular intervals. This makes it nearly impossible, for example, to use SoftwareSerial to receive GPS data and parse it into a usable form. Your program is too busy trying to keep up with NMEA characters as they arrive to actually spend time assembling them into something meaningful. This is where AFSoftSerial’s (and NewSoftSerial‘s) interrupt architecture is a godsend. Using interrupt-driven RX, your program fills its buffer behind the scenes while processing previously received data.
NewSoftSerial offers a number of improvements over SoftwareSerial:
Print
, eliminating some 4-600 bytes of duplicate code*But see below for an important caveat on multiple instances.
**Be circumspect about using 300 and 1200 baud though. The interrupt handler at these rate becomes so lengthy that timer tick interrupts can be starved, causing millis() to stop working during receives.
There has been considerable support for an library that would allow multiple soft serial devices. However, handling asynchronously received data from two, three, or four or more serial devices turns out to be an extremely difficult, if not intractable problem. Imagine four serial devices connected to an Arduino, each transmitting at 38,400 baud. As bits arrive, Arduino’s poor little processor must sample and process each of 4 incoming bits within 26 microseconds or else lose them forever. Yikes!
It occurred to me, though, that multiple instances could still be possible if the library user were willing to make a small concession. NewSoftSerial is written on the principle that you can have as many devices connected as resource constraints allow, as long as you only use one of them at a time. If you can organize your program code around this constraint, then NewSoftSerial may work for you.
What does this mean, exactly? Well, you have to use your serial devices serially, like this:
In this example, we assume that read_gps_data()
uses the gps
object and read_thermometer_data()
uses the therm
object. Any time you call the listen() method, it becomes the “active” object, and the previously active object is deactivated and its RX buffer discarded. An important point here is that object.available()
always returns 0 unless object
is already active. This means that you can’t write code like this:
This code will never do anything but activate one device after the other.
“Normal” TTL serial signaling defines a start bit as a transition from “high” to “low” logic. Logical 1 is “high”, 0 is “low”. But some serial devices turn this logic upside down, using what we call “inverted signaling”. As of version 10, NewSoftSerial supports these devices natively with a third parameter in the constructor.
Library Version
You can retrieve the version of the NewSoftSerial library by calling the static member library_version().
Linking the NewSoftSerial library to your application adds approximately 2000 bytes to its size.
The latest version of NewSoftSerial is available here: NewSoftSerial12.zip. Note: don’t download this if you have Arduino 1.0 or later. As of 1.0, NewSoftSerial is included in the Arduino core (named SoftwareSerial).
Many thanks to David Mellis, who wrote the original SoftwareSerial, and to the multi-talented ladyada, whose work with AFSoftSerial is seminal. Ladyada also provided the “Goodnight, moon” example sketch, fixed a problem with the interrupt naming (see v6) and tested NSS with the 328p.
Thanks also to rogermm and several other forum users who have tested NewSoftSerial and given useful feedback.
The diligent analysis of forum user etracer yielded the root cause of a tricky problem with NSS on OSX. A bug in avr-gcc 4.3.0 causes the compiler to fail to generate the proper entry and exit sequences for certain interrupt handlers. etracer identified the problem and provided an inline workaround. etracer’s fix is in NSS 5.
User jin contributed a large body of work based on NSS and identified a potential problem that could result in data loss (fixed in NSS 5). jin also made a variant of NSS that supports 4-pin serial, with the additional pins providing a very nice RTS/CTS flow control. We may see this in NSS in the near future.
Thanks to Garret Mace, who contributed the delay tables for 20MHz processors and claims that he can send and receive at 115K baud. Cool!
Thanks to Paul Stoffregen, both for his fine work with Teensy and Teensy++, and for contributing some useful suggestions that help NewSoftSerial run on them without modification.
I appreciate any and all input.
Mikal Hart