Re: are CN=.# and CN== valid?

It looks like: CN=\#. as well. scanVal() strips off the \ leaving '#', ParseRFC1485AVA(), seeing a leading '#' then wrongly concludes it is the hex encoded BER. On Tue, 1 Oct 2019 at 16:27, Andrew Cagney wrote: > > CERT_AsciiToName() rejects both because the '=' and '#' appear > un-escaped in

[ANNOUNCE] NSS 3.44.2 and 3.46.1 Releases

The NSS Development Team announces multiple patch releases: * NSS 3.44.2 for NSS 3.44 * NSS 3.46.1 for NSS 3.46 No new functionality is introduced in these releases. The following fixes are included in both releases. Users are encouraged to upgrade. * 1582343 - Soft token MAC verification not c