Michael Konietzka wrote:
Michael Bell schrieb:
Michael Konietzka wrote:
Michael Bell schrieb:
Michael Konietzka wrote:
I have the same problem here:
Signing of CSR, CRR don't work correctly.
CSRs are working now for me. There were three nice reasons:
1. SQL databases can have problems with umlau
Michael Bell schrieb:
Michael Konietzka wrote:
Michael Bell schrieb:
Michael Konietzka wrote:
I have the same problem here:
Signing of CSR, CRR don't work correctly.
CSRs are working now for me. There were three nice reasons:
1. SQL databases can have problems with umlauts like "ü".
2. REQ.pm ha
Michael Konietzka wrote:
Michael Bell schrieb:
Michael Konietzka wrote:
I have the same problem here:
Signing of CSR, CRR don't work correctly.
CSRs are working now for me. There were three nice reasons:
1. SQL databases can have problems with umlauts like "ü".
2. REQ.pm has a wrong regex for the
Michael Bell schrieb:
Michael Konietzka wrote:
I have the same problem here:
Signing of CSR, CRR don't work correctly.
CSRs are working now for me. There were three nice reasons:
1. SQL databases can have problems with umlauts like "ü".
2. REQ.pm has a wrong regex for the extraction of the BODY.
Michael Bell schrieb:
Michael Konietzka wrote:
I have the same problem here:
Signing of CSR, CRR don't work correctly.
CSRs are working now for me. There were three nice reasons:
1. SQL databases can have problems with umlauts like "ü".
2. REQ.pm has a wrong regex for the extraction of the BODY.
Michael Konietzka wrote:
I have the same problem here:
Signing of CSR, CRR don't work correctly.
CSRs are working now for me. There were three nice reasons:
1. SQL databases can have problems with umlauts like "ü".
2. REQ.pm has a wrong regex for the extraction of the BODY.
3. crypot-utils.lib mer
Michael Konietzka wrote:
I have the same problem here:
Signing of CSR, CRR don't work correctly.
Example view the CRR there is Invalid signature reported.
Browser message:
Error 560
General Error. Signature Object not returned, check
the openca-verify command. Canno
Michael,
On Wednesday 07 July 2004 12:39, Michael Bell wrote:
> I tested with Mozilla 1.5 (SECCLAB) and Mozilla 1.7 (crypto.signText).
> Can you output text and signature in test_cert and send it to the list
> or directly to me? I need some material to analyze the problem.
OK, I edited the "verif
Chris Covell schrieb:
Guys,
On Tuesday 06 July 2004 15:45, Michael Bell wrote:
I commited a second big bugfix today which should now fix the problem
with the signature verification for roles and PIN (CRINs) too. I worked
some time ago on a telco software and remembered me that the linebreak
of http
Chris Covell wrote:
I have just been and checked out a fresh CVS version, installed it and I am
still getting the same signing verification problems in Signing a CSR and
User "testing a certificate". I am using IE 6. The error I see is:
Error 6206
General Error. Cannot build PKCS#7-object from e
Guys,
On Tuesday 06 July 2004 15:45, Michael Bell wrote:
> I commited a second big bugfix today which should now fix the problem
> with the signature verification for roles and PIN (CRINs) too. I worked
> some time ago on a telco software and remembered me that the linebreak
> of http is \r\n.
I
Hi,
I commited a second big bugfix today which should now fix the problem
with the signature verification for roles and PIN (CRINs) too. I worked
some time ago on a telco software and remembered me that the linebreak
of http is \r\n.
We (OpenCA) uses only \n\n for example to seperate the conten
Hi Dalini,
I have now a fix for the problem but it requires again the test of CSR
and CRR signing. It looks like the browsers have problems with LF. I
updated HTML.pm so that it replaces now LF always by CRLF. The result is
that verifySignature has no longer any problems with test_cert.
Our req
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(
Michael Konietzka wrote:
Ives Steglich schrieb:
Ives Steglich wrote:
actually - i'm that far, that the code itself seemes to be fine in
most cases, since i got the pub-user-test certificate working
the problem there was: the signing text had a \n at the end, but the
text used to verify against d
Ives Steglich schrieb:
Ives Steglich wrote:
actually - i'm that far, that the code itself seemes to be fine in
most cases, since i got the pub-user-test certificate working
the problem there was: the signing text had a \n at the end, but the
text used to verify against didn't have \n at the end
Ives Steglich wrote:
actually - i'm that far, that the code itself seemes to be fine in most
cases, since i got the pub-user-test certificate working
the problem there was: the signing text had a \n at the end, but the
text used to verify against didn't have \n at the end - so the verify
fails.
17 matches
Mail list logo
