Re: [freenet-dev] Breaking CHK compatibility in 0.6?

2003-07-21 Thread Toad
On Mon, Jul 21, 2003 at 08:54:43PM -0400, Nick Tarleton wrote: > On Monday 21 July 2003 08:24 pm, Nick Tarleton wrote: > > To me, it looks like a CHK contains log2 of the (padded) size of the data. > > From ClientCHK.encode: > > chk = new CHK(storables, Util.log2(getPaddedLength())); > > In about a

Re: [freenet-dev] Breaking CHK compatibility in 0.6?

2003-07-21 Thread Nick Tarleton
On Monday 21 July 2003 03:39 pm, [EMAIL PROTECTED] wrote: > >it does not, for a CHK, indicate the overall size of the > >key. > > All client writers will be eternally grateful if you add this. I can see > half of the spam attacks against frost dissapearing once we have this. Hmm. How? Frost uses K

Re: [freenet-dev] Breaking CHK compatibility in 0.6?

2003-07-21 Thread Nick Tarleton
On Monday 21 July 2003 08:24 pm, Nick Tarleton wrote: > To me, it looks like a CHK contains log2 of the (padded) size of the data. > From ClientCHK.encode: > chk = new CHK(storables, Util.log2(getPaddedLength())); > In about an hour expect some code to pull that out of a text CHK. ;-) And here it

Re: [freenet-dev] Breaking CHK compatibility in 0.6?

2003-07-21 Thread Nick Tarleton
On Monday 21 July 2003 03:29 pm, Toad wrote: > The next Freenet release, with NGRouting, will be Freenet 0.6 (or 0.7, > that's a whole debate in itself). AFAICS, after talking to oskar, > current Freenet keys include a byte indicating how big the verification > chunks are - it does not, for a CHK,

[freenet-dev] Breaking CHK compatibility in 0.6?

2003-07-21 Thread zbalevsk
>it does not, for a CHK, indicate the overall size of the >key. All client writers will be eternally grateful if you add this. I can see half of the spam attacks against frost dissapearing once we have this. ___ devl mailing list [EMAIL PROTECTED] htt

[freenet-dev] Breaking CHK compatibility in 0.6?

2003-07-21 Thread Toad
The next Freenet release, with NGRouting, will be Freenet 0.6 (or 0.7, that's a whole debate in itself). AFAICS, after talking to oskar, current Freenet keys include a byte indicating how big the verification chunks are - it does not, for a CHK, indicate the overall size of the key. If I am wrong a