On Mon, May 07, 2001 at 08:49:59AM -0500, Scott Gregory Miller wrote: > > > On Sun, May 06, 2001 at 02:19:48AM -0400, Tavin Cole wrote: > > > The Public-key is a hex-encoded DSA public key as in 0.3, but > > > the DSA group is now appended after a comma, always, so you > > > get Public-key=y,p,q,g. If that's a problem I > > > can go back to using the optional Group field. > > > > Why? Does Scott think that reusing the groups is a risk? It's > > certainly possible to generate groups for every message (last I heard > > fred took several minutes to do this, wrose can do it in a couple of > > seconds thou) but it's a bit of a waste of time&space unless needed. > > Not really. I think is probably a good idea to have a different group per > SSK, but not really a requirement. KSKs are so insecure anyway that we > shouldn't bother using a different group for each one, but since a person > needs to create an SVK private key for their website, why not make them > take the time to generate a group as well. > > > Storable.Public-key=15102b30436e41a6c9b52d6146d2f3862a84e7b51e28db943d125dbd180ac0088e91167fb04bcbd73ac9cac18d77587718000838ee1a3ffdd7fe1dccb9d2d3159297fae239ab82e3635c2889cfa82ee7c1e0d5ec6bd829395db3d04b6fa80f360b3bd8cfec7e9494332b029ba2aae0fe590c144eb14adb8e16ba0a25c20ad8d0,a21a980fc9ae82b90344e8e2490da9c9765f80bc07f3bf832af1bc68c25608cb3676313de1178082929481f08996fab332d11abc832d646b4190dcd4053a560798767a2b01f413511d637166098f602bf785dbed49486771a6d542a78f54fa34f7055f0c3f11829fbec3624b9273f8f987670dd6453a6fb313c7466848b2a23f,3c88434bf33b1a74ef91c2394783a5eab326dbe5c633b58f766dd18210e0eaa4c104e9df1404c3f685239d95df014bf7835fe3b50ceeeab1ef2df69368bfe79deaa0153eeae2f4e5a18410623a27d61bc4808ae80bfd2961b0ed1d9054eecd69bf55938e3b05852f6031ed2fe5ebe747520fc0fff69af2536f42ee27b9fa4d7b,d99d5fff8862230d8aa205e973a3bdf45638ddd1 > > > > Thats a real y,p,g,q set - and that's a big header. > > I can see the reason we want all of them included, its so that hashing is > consistent. But perhaps hashing in the optional Public-key.Group field if > it isn't present is a better solution.
Ok, I want to go with Adam's other suggestion of using Storable.Public-key.[ypgq] -- all required, but split into 4 fields in a subset so we can better stay within the 1024 byte limit. -- # tavin cole # # "The process of scientific discovery is, in effect, # a continual flight from wonder." # - Albert Einstein _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
