Johnny Gonzalez wrote:
so if the edit code works fine - this looks like there is a problem in the pkcs#10 parsing and handling code which introduces the #130Well, with the edit code I can see the garbage characters and I'm able to correct them in each certificate, one by one, but to be able to correct all new requests before signing, I will have to do some coding, maybe in Java, because I know nothing about perl :-(
Sounds for me like a double encoding. This happens if utf8 answer stream is interpreted like a latin1 stream and then somebody tries to use utf8 aware code to interpret this stream. The result is that stream is encoded twice. I fixed such problem over the whole das in CVS HEAD ... and now the approve mechanism blocks :(
Perhaps I have a better trim on monday ;) Have a nice weekend Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
