Ives Steglich wrote:
i have deaktivated the unlink of the temp files, so i could verfiy at least this problem:
\n is usaly put as: 0x0A
the used data for verification contains: 0x0D0A which is equivalent to \r\n so somewhere happens this conversation step... but i don't know where right now ;o( - at least the data i find at the temporary file, and this is uses for verification
Ok, I will start searching for the conversion - test_Cert was a good hint.
when i use a hexeditor and remove the additional byte: 0x0D than the message can be verified as correct
and the digest matches...
Good to know.
BTW you can activate global debugging in etc/log.xml. The debug value on top of the file activates global debugging. Only the crypto debugging must be activated seperately in etc/token.xml. The debug output goes to STDERR which is in var/log/stderr.log. Please be really careful with this debug option because stderr.log can raise very quickly.
If you write new code please always debug to STDERR which goes to stderr.log
Michael -- ------------------------------------------------------------------- Michael Bell Email: [EMAIL PROTECTED] ZE Computer- und Medienservice Tel.: +49 (0)30-2093 2482 (Computing Centre) Fax: +49 (0)30-2093 2704 Humboldt-University of Berlin Unter den Linden 6 10099 Berlin Email (private): [EMAIL PROTECTED] Germany http://www.openca.org
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel
