jsdsi-devel Mailing List for JSDSI (Page 2)
Status: Pre-Alpha
Brought to you by:
sajma
Menu
▾
▴
jsdsi-devel — JSDSI Developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(45) |
Mar
(60) |
Apr
(12) |
May
(18) |
Jun
(14) |
Jul
(8) |
Aug
(10) |
Sep
|
Oct
(12) |
Nov
(16) |
Dec
(15) |
| 2005 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
|
From: Sean R. <sra...@ae...> - 2004-11-10 09:34:52
|
Sameer, Just put a quick implementation together in CVS. Is this the sort of thing you want? If so I'll write a test class for it and then convert KeyPairFactory to use it but remain a 'static singleton class' to cache key pair generators for performance if people want it. Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sean R. <sra...@ae...> - 2004-11-08 12:21:33
|
Sameer Ajmani wrote:
>Sean,
>
>In answering Will's question, I noticed that jsdsi.util.KeyPairFactory
>is does not implement a standard Java interface. Instead, it offers
>myriad create() routines and keeps and internal cache of
>KeyPairGenerators. Why is this? Perhaps we discussed this when you
>first implemented this class, but now I think there's a cleaner way to
>do it:
>
>Instead let's have a class jsdsi.util.RSAKeyPairGeneratorSpi that
>implements java.security.KeyPairGeneratorSpi. Instead of having so
>many different create() routines, the parameters for creation are
>passed via java.security.KeyPairGeneratorSpi.initialize(...). The
>parameter to initialize() is an instance of a new class,
>jsdsi.util.RSAKeyGenParameterSpec, which is a subclass of
>java.security.spec.RSAKeyGenParameterSpec; our subclass contains extra
>fields for URIs, etc.
>
>With this class, users can generate KeyPairs in the standard Java way:
>KeyPairGenerator kpg = KeyPairGenerator.getInstance("RSA", new
>jsdsi.Provider()) ;
>kpg.initialize(new RSAKeyGenParameterSpec(keysize, exponent, uris));
>KeyPair kp = kpg.genKeyPair();
>assert(kp.getPublic() instanceof jsdsi.RSAPublicKey);
>assert(kp.getPrivate() instanceof java.security.interfaces.RSAPrivateKey);
>
>I believe jsdsi.util.RSAKeyPairGeneratorSpi will be somewhat easier to
>maintain than jsdsi.util.KeyPairFactory and will be more useful to
>users. I apologize for not thinking of this long ago :)
>
>If you have a good reason for why jsdsi.util.KeyPairFactory is better,
>please let me know!
>
>
I can't recollect myself. The only thing I remember was the issue with
the Sun implementation giving the same key pairs on consecutive calls
when using the 'defaults'. I'll look into it this, or next week.
Sean
--
Dr. Sean Radford, MBBS, MSc
sra...@ae...
http://www.aegeus-technology.com/
|
|
From: Sean R. <sra...@ae...> - 2004-11-08 12:18:32
|
Guys, As discussed, I have merged the BRANCH-ALGO into the HEAD. All the tests continue to pass, so I hope/trust that all is ok. Please check yourselves over the next few days and raise any problems. If there are no issues/objections, I would plan to release another snapshot at the end of the week. Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sameer A. <aj...@gm...> - 2004-11-03 23:30:31
|
Yes, this should be fine. On Wed, 03 Nov 2004 23:30:25 +0000, Sean Radford <sra...@ae...> wrote: > Sameer Ajmani wrote: > > >I agree we should postpone 1.5 until our known users are using it. > > > > > Shall I merge my 'algorythm branch code' into the HEAD then? > > -- > > > Dr. Sean Radford, MBBS, MSc > sra...@ae... > http://www.aegeus-technology.com/ > > -- Sameer Ajmani http://ajmani.net |
|
From: Sean R. <sra...@ae...> - 2004-11-03 23:23:35
|
Sameer Ajmani wrote: >I agree we should postpone 1.5 until our known users are using it. > > Shall I merge my 'algorythm branch code' into the HEAD then? -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Michael J. <mij...@in...> - 2004-11-03 21:07:49
|
Well, I worked on a project using SPKI in a MANET environment. From my point of view the decentralized nature of SPKI fits very well into this environment. But maybe I'm the only one thinking this way ;-). Unfortunately, I have not much time these days to work on this topic, but I'm planning to do this in future... Bye, Mi. On Wednesday 03 November 2004 18:51, Sameer Ajmani wrote: > I agree we should postpone 1.5 until our known users are using it. > I'm not sure why we want to port to J2ME -- can you provide some > motivation on this? > > > On Wed, 03 Nov 2004 17:16:23 +0000, Sean Radford > > <sra...@ae...> wrote: > > Michael A. Jaeger wrote: > > >Hi, > > > > > >I would find it interesting to do the porting, but I don't think that we > > >really need it as I find other things (like J2ME) more important. > > > > I agree - there are more important things to spend time on currently. > > And we don't want to upset existing users and limit newer potential ones > > by stipulating 1.5. > > > > > > > > -- > > Dr. Sean Radford, MBBS, MSc > > sra...@ae... > > http://www.aegeus-technology.com/ > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: > > Sybase ASE Linux Express Edition - download now for FREE > > LinuxWorld Reader's Choice Award Winner for best database on Linux. > > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > > _______________________________________________ > > Jsdsi-devel mailing list > > Jsd...@li... > > https://lists.sourceforge.net/lists/listinfo/jsdsi-devel |
|
From: Sameer A. <aj...@gm...> - 2004-11-03 17:51:59
|
I agree we should postpone 1.5 until our known users are using it. I'm not sure why we want to port to J2ME -- can you provide some motivation on this? On Wed, 03 Nov 2004 17:16:23 +0000, Sean Radford <sra...@ae...> wrote: > Michael A. Jaeger wrote: > > >Hi, > > > >I would find it interesting to do the porting, but I don't think that we > >really need it as I find other things (like J2ME) more important. > > > > > > > I agree - there are more important things to spend time on currently. > And we don't want to upset existing users and limit newer potential ones > by stipulating 1.5. > > > > -- > Dr. Sean Radford, MBBS, MSc > sra...@ae... > http://www.aegeus-technology.com/ > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Jsdsi-devel mailing list > Jsd...@li... > https://lists.sourceforge.net/lists/listinfo/jsdsi-devel > > -- Sameer Ajmani http://ajmani.net |
|
From: Sean R. <sra...@ae...> - 2004-11-03 17:09:40
|
Michael A. Jaeger wrote: >Hi, > >I would find it interesting to do the porting, but I don't think that we >really need it as I find other things (like J2ME) more important. > > > I agree - there are more important things to spend time on currently. And we don't want to upset existing users and limit newer potential ones by stipulating 1.5. -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Michael A. J. <mic...@ac...> - 2004-11-03 16:58:36
|
Hi, I would find it interesting to do the porting, but I don't think that we really need it as I find other things (like J2ME) more important. Mi. On Wednesday 03 November 2004 17:13, Sean Radford wrote: > Guys, > > Do we want to make a final decision on JDK 1.5? > > I think that we should vote ourselves, and if we decide that we would > like to move to 1.5 then put it to 'the community' to have the final > say... Thoughts? > > I myself think that we should stick with 1.4 > > Sean -- + Michael A. Jaeger, Berlin University of Technology + Intelligent Networks and Management of Distributed Systems + http://ivs.tu-berlin.de/mjaeger |
|
From: Sean R. <sra...@ae...> - 2004-11-03 16:06:50
|
Guys, Do we want to make a final decision on JDK 1.5? I think that we should vote ourselves, and if we decide that we would like to move to 1.5 then put it to 'the community' to have the final say... Thoughts? I myself think that we should stick with 1.4 Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sean R. <sra...@ae...> - 2004-10-26 21:40:56
|
Michael Jaeger wrote: > >I agree. Another thing I find very interesting is a port to J2ME we should >consider in my opinion. > > That sounds interesting. Has anyone here ever looked at J2ME? -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: <lp...@ne...> - 2004-10-26 09:31:53
|
=20 Hi, I'm using JSDSI in production!=20 =BB-----Original Message----- =BBFrom: jsd...@li... =BB[mailto:jsd...@li...] On Behalf Of = =BBMichael Jaeger =BBSent: segunda-feira, 25 de Outubro de 2004 21:45 =BBTo: jsd...@li... =BBSubject: Re: [Fwd: [Jsdsi-devel] Re: [Fwd: Branch-algo]] =BB =BBOn = Monday 25 October 2004 20:20, Sean Radford wrote: =BB> That's what I would have thought. I would guess that 1.5 language = =BB> features, such as the new style 'for loop' might though.=20 =BBI'm still in =BB> 2 minds. For us moving to 1.5 could be a real problem in some = =BB> organisations... =BB =BBHas anybody already asked this question on the user-list? I = =BBmean, if there is nobody using JSDSI in production there =BBwould be no problem, = or am I wrong? =BB =BB> Also, isn't there so much other functionality that could be done = to =BB> make JSDSI more useful - and so be a better use of our time =BBat = present? =BB =BBI agree. Another thing I find very interesting is a port to = =BBJ2ME we should consider in my opinion. =BB =BBBye, =BBMichael. =BB =BB =BB------------------------------------------------------- =BBThis SF.net email is sponsored by: IT Product Guide on = =BBITManagersJournal Use IT products in your business? Tell us =BBwhat you think of them. = Give us Your Opinions, Get Free =BBThinkGeek Gift Certificates! Click to find = out more =BBhttp://productguide.itmanagersjournal.com/guidepromo.tmpl =BB_______________________________________________ =BBJsdsi-devel mailing list =BBJ...@li... =BBhttps://lists.sourceforge.net/lists/listinfo/jsdsi-devel =BB |
|
From: Michael J. <mij...@in...> - 2004-10-25 20:44:51
|
On Monday 25 October 2004 20:20, Sean Radford wrote: > That's what I would have thought. I would guess that 1.5 language > features, such as the new style 'for loop' might though. I'm still in 2 > minds. For us moving to 1.5 could be a real problem in some > organisations... Has anybody already asked this question on the user-list? I mean, if there is nobody using JSDSI in production there would be no problem, or am I wrong? > Also, isn't there so much other functionality that could be done to make > JSDSI more useful - and so be a better use of our time at present? I agree. Another thing I find very interesting is a port to J2ME we should consider in my opinion. Bye, Michael. |
|
From: Sameer A. <aj...@gm...> - 2004-10-25 18:49:44
|
Yes, there are plenty more features to implement. I just like the 1.5 features :) Hell, I just like beutifying code :) S On Mon, 25 Oct 2004 19:20:22 +0100, Sean Radford <sra...@ae...> wrote: > Sameer Ajmani wrote: > > >It turns out 1.5 classes *cannot* be used by 1.4 JRE. What this means > >is, if we want JSDSI to be usable by 1.4 clients, we cannot port JSDSI > >to 1.5 (unless we want to maintain two versions, which I don't think > >we want). Sorry for my misstatements earlier! > > > >Sameer > > > > > That's what I would have thought. I would guess that 1.5 language > features, such as the new style 'for loop' might though. I'm still in 2 > minds. For us moving to 1.5 could be a real problem in some organisations... > > Also, isn't there so much other functionality that could be done to make > JSDSI more useful - and so be a better use of our time at present? > > > > Sean > > -- > Dr. Sean Radford, MBBS, MSc > sra...@ae... > http://www.aegeus-technology.com/ > > -- Sameer Ajmani http://ajmani.net |
|
From: Sean R. <sra...@ae...> - 2004-10-25 18:15:15
|
Sameer Ajmani wrote: >It turns out 1.5 classes *cannot* be used by 1.4 JRE. What this means >is, if we want JSDSI to be usable by 1.4 clients, we cannot port JSDSI >to 1.5 (unless we want to maintain two versions, which I don't think >we want). Sorry for my misstatements earlier! > >Sameer > > That's what I would have thought. I would guess that 1.5 language features, such as the new style 'for loop' might though. I'm still in 2 minds. For us moving to 1.5 could be a real problem in some organisations... Also, isn't there so much other functionality that could be done to make JSDSI more useful - and so be a better use of our time at present? Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sameer A. <aj...@gm...> - 2004-10-25 17:48:01
|
It turns out 1.5 classes *cannot* be used by 1.4 JRE. What this means is, if we want JSDSI to be usable by 1.4 clients, we cannot port JSDSI to 1.5 (unless we want to maintain two versions, which I don't think we want). Sorry for my misstatements earlier! Sameer On Sun, 17 Oct 2004 13:42:40 -0400, Sameer Ajmani <aj...@gm...> wrote: > Sean, > > I took a look through the diff between branch and head: > cvs diff -N -u -r HEAD -r branch-algo > > Your changes look good, but there has been a fair bid of code cleanup > sinc eyou branched (so there's a lot in HEAD that ought to be kept). > Also, since 1.5 offers enums as a language feature, it makes sense to > represent algos with 1.5 enums. > > Here's what I suggest: rather than doign a traditional merge of your > branch into the mainline, consider reimplementing your algo stuff > using 1.5 enums in the mainline, just using your branched code as a > guide.. That way, you'll preserve all the recent changes and get a > chance to make the algo stuff as clean as it can be. > > Thanks for the contribution -- it looks good! > Sameer > > On Sun, 17 Oct 2004 17:38:47 +0100, Sean Radford > <sra...@ae...> wrote: > > > > -- > > > > Dr. Sean Radford, MBBS, MSc > > sra...@ae... > > http://www.aegeus-technology.com/ > > > > > > > > ---------- Forwarded message ---------- > > From: Sean Radford <sra...@ae...> > > To: Sameer Ajmani <aj...@gm...>, jsdsi devel <jsd...@li...> > > Date: Fri, 13 Aug 2004 14:44:24 +0100 > > Subject: [Jsdsi-devel] Re: [Fwd: Branch-algo] > > Sameer Ajmani wrote: > > > > >Sameer Ajmani wrote: > > > > > > Can you tell me how to check out that branch? I'll be out of town > > >next week, but I'll check it out when I get the chance. > > > > > >Sameer > > > > > > > > > > > Sorry, but looks like I didn't get round to answering this one... > > > > Take a look at: > > > > https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_5.html#SEC57 > > > > (the branch is called 'branch-algo') > > > > Sean > > > > -- > > > > Dr. Sean Radford, MBBS, MSc > > sra...@ae... > > http://www.aegeus-technology.com/ > > > > ------------------------------------------------------- > > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > > _______________________________________________ > > Jsdsi-devel mailing list > > Jsd...@li... > > https://lists.sourceforge.net/lists/listinfo/jsdsi-devel > > > > > > > > > -- > Sameer Ajmani > http://ajmani.net > -- Sameer Ajmani http://ajmani.net |
|
From: Sean R. <sra...@ae...> - 2004-10-17 22:02:01
|
Sameer Ajmani wrote: >Sean, > >I took a look through the diff between branch and head: >cvs diff -N -u -r HEAD -r branch-algo > >Your changes look good, but there has been a fair bid of code cleanup >sinc eyou branched (so there's a lot in HEAD that ought to be kept). >Also, since 1.5 offers enums as a language feature, it makes sense to >represent algos with 1.5 enums. > >Here's what I suggest: rather than doign a traditional merge of your >branch into the mainline, consider reimplementing your algo stuff >using 1.5 enums in the mainline, just using your branched code as a >guide.. That way, you'll preserve all the recent changes and get a >chance to make the algo stuff as clean as it can be. > >Thanks for the contribution -- it looks good! >Sameer > >On Sun, 17 Oct 2004 17:38:47 +0100, Sean Radford ><sra...@ae...> wrote: > > >>-- >>Dr. Sean Radford, MBBS, MSc >>sra...@ae... >>http://www.aegeus-technology.com/ >> >> >> >>---------- Forwarded message ---------- >>From: Sean Radford <sra...@ae...> >>To: Sameer Ajmani <aj...@gm...>, jsdsi devel <jsd...@li...> >>Date: Fri, 13 Aug 2004 14:44:24 +0100 >>Subject: [Jsdsi-devel] Re: [Fwd: Branch-algo] >>Sameer Ajmani wrote: >> >> >> >>>Sameer Ajmani wrote: >>> >>> Can you tell me how to check out that branch? I'll be out of town >>>next week, but I'll check it out when I get the chance. >>> >>>Sameer >>> >>> >>> >>> >>> >>Sorry, but looks like I didn't get round to answering this one... >> >>Take a look at: >> >>https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_5.html#SEC57 >> >>(the branch is called 'branch-algo') >> >>Sean >> >> >> If the consensus is to move to 1.5 then that seems the sensible thing to do. -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sameer A. <aj...@gm...> - 2004-10-17 17:48:55
|
I don't really see the point of this article. The claim that Generics made it harder for the guy to see his design flaw is, IMHO, ludicrous. I think the fact that he used "Set<Map.Entry<String, Object>>" as a return type is a clear signal that something was wrong, so in this case Generics definitely help with maintenance. His suggests that this would have been easier to spot without generics, but I don't believe him -- without generics, the return type would have been simply "Set", which looks far more legitimate I'm a fan of self-documenting code, and generics are a strong step in that direction (along with sensible variable and method names). Sameer On Sun, 17 Oct 2004 18:32:33 +0100, Sean Radford <sra...@ae...> wrote: > You may want to have a think about this: > > http://www.javaspecialists.co.za/archive/Issue095b.html > > (though probably good to have a quick look at > > http://www.javaspecialists.co.za/archive/Issue095.html > > first) > > -- > Dr. Sean Radford, MBBS, MSc > sra...@ae... > http://www.aegeus-technology.com/ > > -- Sameer Ajmani http://ajmani.net |
|
From: Sean R. <sra...@ae...> - 2004-10-17 17:28:58
|
You may want to have a think about this: http://www.javaspecialists.co.za/archive/Issue095b.html (though probably good to have a quick look at http://www.javaspecialists.co.za/archive/Issue095.html first) -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sean R. <sra...@ae...> - 2004-10-17 15:18:17
|
Sameer Ajmani wrote: >Hi guys, > >I might finally be able to spare a few cycles for JSDSI again :) >Do we have any interest in porting JSDSI to JDK 1.5? I really like >the new JDK features, but I understand that those of you using JSDSI >in your businesses probablye want it to remain compatible with your >current JDKs. Any thoughts? > > > What features of 1.5 are you thinking about? Would you have any time to look at the algorythm CVS branch? How did the PhD write-up go? Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Luis P. <lp...@ne...> - 2004-10-17 12:17:28
|
Hi Sameer,
=20
I really didn't had the time, yet, to look at JDK 1.5!=20
But i will, i have to use it on my new project.
=20
I think that JSDSI should be ported to JDK 1.5 but slowly=20
and i also think that the current release should be=20
kept for now.
=20
-- Lu=EDs Pedro
=20
|
|
From: Sameer A. <aj...@gm...> - 2004-10-17 04:14:13
|
Hi guys, I might finally be able to spare a few cycles for JSDSI again :) Do we have any interest in porting JSDSI to JDK 1.5? I really like the new JDK features, but I understand that those of you using JSDSI in your businesses probablye want it to remain compatible with your current JDKs. Any thoughts? -- Sameer Ajmani http://ajmani.net |
|
From: Sean R. <sra...@ae...> - 2004-08-27 18:40:51
|
Dav Coleman wrote: >Hi, when using jsdsi.ObjInputStream I am unable to read a previously >written AclEntry, using both the jsdsi-0.5.jar and the snapshot jar. >I'm attaching a java source that shows this. > >Here's the exception: >jsdsi.sexp.SexpParseException: expected list > at jsdsi.sexp.SexpUtil.check(SexpUtil.java:109) > at jsdsi.sexp.SexpUtil.getList(SexpUtil.java:133) > at jsdsi.sexp.SexpUtil.getList(SexpUtil.java:142) > at jsdsi.sexp.SexpUtil.getNextList(SexpUtil.java:171) > at jsdsi.AclEntry.parseAclEntry(AclEntry.java:181) > at jsdsi.Obj.parseObj(Obj.java:195) > at jsdsi.Obj.parseObj(Obj.java:182) > at jsdsi.sexp.ObjInputStream.readObj(ObjInputStream.java:52) > at test.read(test.java:45) > at test.main(test.java:67) > >For convenience, here's the javac and java cmds to test. > >javac -classpath extlib/jsdsi-0.5.jar test.java > >java -classpath .:extlib/cryptix32.jar:extlib/jsdsi-0.5.jar test write test.acl >cat test.acl >java -classpath .:extlib/cryptix32.jar:extlib/jsdsi-0.5.jar test read test.acl > >Is this a bug? > > > Sure looks like from your description. Most probably because no-one has yet used Acl objects really yet. I'll try to look into it tomorrow afternoon and hopefully get a fix into CVS. Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sean R. <sra...@ae...> - 2004-08-24 23:10:47
|
Still haven't managed to get the fix into CVS yet I'm afraid guys... (some other work cropped up). I want to improve the unit test first - I'll do that in the morning, and then commit. Regards, Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
|
From: Sean R. <sra...@ae...> - 2004-08-24 13:51:11
|
Sameer Ajmani wrote: >Thanks, Sean! My guess would have been something in DateFormat. What >did it turn out to be? > >On Tue, 24 Aug 2004 13:54:53 +0100, Sean Radford ><sra...@ae...> wrote: > > >>Sean Radford wrote: >> >> >> >>>Definately looking like a threading issue to me. I have a junit test >>>that creates 100 certificates and stores them as a List of byte >>>arrays. I then have a number of Threads that iterate through the list >>>and I intermittently get stack traces like the following (the input >>>string varies): >>> >>>... >>> >>> >>Found the problem - will get the fix into CVS in an hour or so. >> >>:-) >> >> That was exactly it -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com/ |
2 messages has been excluded from this view by a project administrator.
