Issue 63058 - add signature does not work
Summary: add signature does not work
Status: CLOSED DUPLICATE of issue 62684
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0.2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: OOo 2.0.4
Assignee: joachim.lingner
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-11 18:01 UTC by hizuya
Modified: 2006-05-22 09:34 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description hizuya 2006-03-11 18:01:26 UTC
I can't add a certificate when there is comma(,) in the certificate's subject.
e.g.
CN=Test
O=ABC, Inc.
C=US
Comment 1 Olaf Felka 2006-03-13 08:26:06 UTC
@ fst:  please have a look.
Comment 2 frank 2006-03-13 09:01:30 UTC
Hi Joachim,

please have a look at this one and target as needed.

Frank
Comment 3 joachim.lingner 2006-03-13 09:17:19 UTC
.
Comment 4 joachim.lingner 2006-03-24 15:02:21 UTC
jl->hizuya: Are you sure that you mean the subject and not the issuer? I could
not reproduce this bug with a subject name containing a ",". The string type of
respective RDN was PrintableString. 
Another problem could be that the certificate uses other string types for the
RDN values in the issuer name. If this is the case, then this may be fixed in
cws jl32 (issue 62684).
Comment 5 hizuya 2006-03-24 17:56:52 UTC
Hi jl,

As you say, issuer is right.  I had mistaken because I was trying to use the
self signed certificate.  I think that PrintableString contains ",". 
I fixed "replaceTagSWithTagST" function in
xmlsecurity\source\xmlsec\mscrypt\x509certificate_mscryptimpl.cxx.
I don't know whether modification is right. But, I am satisfied.
Comment 6 joachim.lingner 2006-03-27 15:58:42 UTC
Hi hizuya,

Would you mind to add your modified function? BTW, the issuer name was used to
locate the certificate in the local certificate store. But this does not work
very well. Therefore we will use the whole certifcate in the future. In other
words, the issuer name will only have an informative purpose. This was done in
the fix for 62684.
Comment 7 joachim.lingner 2006-05-22 09:33:17 UTC
Should the problem still exist in the current OOo milestone, then reopen this issue.

*** This issue has been marked as a duplicate of 62684 ***
Comment 8 joachim.lingner 2006-05-22 09:34:04 UTC
.