NSS and cryptoki both support UTF8 strings. The problem you described, though, seems to be an application layer problem. Signed data is strictly binary data. It doesn't matter if it is UTF8, ASCII7, UCS2, Enigma-Ciphered Data, EBCDIC, GIF, JPG etc. NSS does not interpret the strings in any way. It simply hashes the data and compares that hash data against the signatures.
bob Tak wrote: > Hi. > > I'm developing application which has digital signature function using > NSS3.31. > > When I decode the data which was signed by certificate including UTF8 > string, application error occurs. The data was made by CryptoAPI, > > Does NSS support UTF8 ? > If NSS support UTF8, what should I do ? > > Thank you. > > Tak
