Re: [Jsdsi-users] Re: Identification in signature s-exp
Status: Pre-Alpha
Brought to you by:
sajma
From: Sudhanshu <sud...@ec...> - 2004-07-01 11:08:53
|
hi, i took these certs and their signatures from the interface directly, and didn't write any code in java (if that's what you mean). The version i'm using is 0.5, the latest one. Anyway, the certs on which these signatures are , are: (cert (issuer (public-key (rsa-pkcs1-md5 (e #010001#) (n |ALksH8+TZhac+r6O4avdCje8JISHNX4dOQESwxD+v7fX7OaNNu1nPAtkXpU hWS0JBGonGqfg7sNosa4/h/I/sNOZfqxggktIN+nC6faM1zqU1k76P1/4CQx 76kYNihtvz2dK79GC6RFMi/HhwZzIqjGqlXHmacxsQgLu2oOjZlr5|)))) (subject (name sandy)) (tag can_play_at_apollo) (valid (not-before "2004-06-02_12:23:34") (not-after "2005-06-02_12:23:34"))) (cert (issuer (name (public-key (rsa-pkcs1-md5 (e #010001#) (n |AOqFMTA5dbJ48Cscmert0dPQa2te1i8S+2dbgS47SuHH/U2DsnoYE4OlS cGzAZxs0Kta8ROeGuLnlRY1naPe9rmUztsK9TDCnT+ooLDVv9YQy6gRfEc hfDzyKqcegnWiPdBRH1W6Huia477i3AzHqzTnk18aSZeRf6h73b1abhhb| ))) "football gang")) (subject (name swarit)) (valid (not-before "2004-06-02_12:23:34") (not-after "2005-06-02_12:23:34"))) I don't think the certs could have caused the code to write MD5/RSA/PKCS#1 instead of rsa-pkcs1-md5. Also, can your code be used to directly work on a set of input files, rather than working from the interface. I couldn't make that happen, so i'm presently writing my own code in C, to parse certs, signatures, and compute closures. thanx, sudhanshu On Wed, 30 Jun 2004, Sean Radford wrote: > Hi, > > As far as I'm aware we are adhering to > draft-ietf-spki-cert-structure-06.txt at the url you mention. Your > signature algorythm you have is not in 'spki' format. > > It should be: rsa-pkcs1-md5 > > I imagine that this has occurred from the way you created your > signatures (you haven't done anything wrong as such, it is just JSDSI > hasn't sorted out its handling of algorithm names yet - there is a > prototype of it as a branch in cvs: branch-algo) > > Hmm... Just noticed that your public key algo is set to rsa-pkcs1-md5... > > Are you able to post snipets of the code you are using to generate your > keys and signatures? > > Sean > > On Wed, 2004-06-30 at 11:02, Sudhanshu wrote: > > Thanx, > > i decoded the base64 script and it turned out to be > > > > (14:MD5/RSA/PKCS#1) > > > > But are you using the same standard as i mentioned earlier, > > ie. the draft-spki.txt, or is there a separate list of grammer rules > > which have been defined by you and which you are using in your java > > implementation. > > > > > > sudhanshu > > > > > > On Tue, 29 Jun 2004, Sameer Ajmani wrote: > > > > > According to the grammar in http://theworld.com/~cme/spki.txt, that > > > field is the <pub-sig-alg-id> (signature algorithm identifier). It's > > > odd that it is base64-encoded in your example; this is probably > > > because your algorithm name contains characters that are not > > > considered SPKI token characters (such as '/'). > > > > > > Sameer > > > > > > On Tue, 29 Jun 2004 22:01:47 +0530 (IST), Sudhanshu > > > <sud...@ec...> wrote: > > > > > > > > > > > > The two signatures shown below were signed by different public keys > > > > but this parameter (as pointed out ) in both of them remains the same, > > > > - as given by the java interface for sdsi. > > > > Could you tell me what does this parameters stand for . > > > > > > > > (signature > > > > (hash md5 |82Ped/N2E6e1EEymDz85+A==|) > > > > (public-key > > > > (rsa-pkcs1-md5 > > > > (e #010001#) > > > > (n > > > > |ALksH8+TZhac+r6O4avdCje8JISHNX4dOQESwxD+v7fX7OaNNu1nPAtkXpUhWS0 > > > > JBGonGqfg7sNosa4/h/I/sNOZfqxggktIN+nC6faM1zqU1k76P1/4CQx76kYNiht > > > > vz2dK79GC6RFMi/HhwZzIqjGqlXHmacxsQgLu2oOjZlr5|))) > > > > ==> (|TUQ1L1JTQS9QS0NTIzE=| > > > > |SG6zQ2EXKJsHpPQsicx9Djkv6e4rImgdO55O1QoX8vN51qCsMOtw4M22HQlIgD8VKG2 > > > > sQLAj0BVRMcFTsSPi77f8yVuz9GrpmLqwN65M2rN8DlWmPMwcCIcKHb2lrTLpxNPXboJ > > > > PgFg1XUGGPnj0Z18RfkjLRwGwrY70ZddAxCE=|)) > > > > > > > > (signature > > > > (hash md5 |65x3g1fH6v9opEMqXC+LOA==|) > > > > (public-key > > > > (rsa-pkcs1-md5 > > > > (e #010001#) > > > > (n > > > > |AOqFMTA5dbJ48Cscmert0dPQa2te1i8S+2dbgS47SuHH/U2DsnoYE4OlScGzAZx > > > > s0Kta8ROeGuLnlRY1naPe9rmUztsK9TDCnT+ooLDVv9YQy6gRfEchfDzyKqcegnW > > > > iPdBRH1W6Huia477i3AzHqzTnk18aSZeRf6h73b1abhhb|))) > > > > ==> (|TUQ1L1JTQS9QS0NTIzE=| > > > > |YhoeMF8ogGe7sZ2m4XisPAuoxMXT25t70gLXgF6OsA4959pJ51pRA8wjtJ0EP3J5OVz > > > > 0sDhgTIGQZF8ZiuQ429OQAYmrJp0BK0+9YL/awCsgPIb9kQG9OdQBTXvc4OYoDMSfkMo > > > > BVDjxnkQKRrA+QcinXusPxKns7cKf6c/bGlA=|)) > > > > > > > > Also, could you tell me if there is any standard being followed for the > > > > current rules of sdsi, ie. the structure of the certs, signatures,etc. > > > > for eg. as the definition of a standard has been attempted in the > > > > draft-ietf-spki-cert-structure-06.txt. > > > > > > > > link for the draft is http://theworld.com/~cme/spki.txt > > > > > > > > Thanx, > > > > sudhanshu > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > 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 > > > _______________________________________________ > > > Jsdsi-users mailing list > > > Jsd...@li... > > > https://lists.sourceforge.net/lists/listinfo/jsdsi-users > > > > > > > > > > > ------------------------------------------------------- > > 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 > > _______________________________________________ > > Jsdsi-users mailing list > > Jsd...@li... > > https://lists.sourceforge.net/lists/listinfo/jsdsi-users > |