----- Original Message ----- From: "Ian Clarke" <[email protected]>
> On Sat, May 12, 2001 at 06:44:11PM -0500, Mathew Ryden wrote: > > Actually it was a deficiency in the FCP specs. GenerateSVKKeypair returns a > > keypair without the last three bytes -- the keysize and keytype. This was > > not accidental, although the docs are lacking in what exactly is returned. > > So the question is whether the spec needs changing. I think it does, > FCP should be easy to use, this is unnescessarily awkward. The question is how. A SVK keypair is a public and private key. When you insert a SVK with the private key, you get the private key back along with the inserted public key. That public key has the keytype attached to it as well -- it is even possible to put it on automatically in 0.4 I think. The problem is that 0.3 also has the size (i guess). That means that a call to GenerateSVKKeypair would have to take in a file so it would know the size and encode that in correctly. It's impossible to do it in this method cleanly, since the real use of GenerateSVKKeypair is to get just that--the SVK public and private keypair for which other inserts can be done. Perhaps a SVKPublicKeygen could be made which took in a private key and a filesize, but it's a hack anyway you look at it IMHO. > Ian. -Mathew _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
