perhaps a more sophisticated response would be to accept the fact that
you don't know what you are doing and don't really want advice. we
only mock you not because you have an idea that didn't pan out ... but
because you won't shut up about "i don't know what i'm doing but i'll
type another page of crap". we don't do that here. well the teenagers
do.

brucee

On Sat, Mar 8, 2008 at 8:37 PM, Enrico Weigelt <[EMAIL PROTECTED]> wrote:
> * Wilhelm B. Kloke <[EMAIL PROTECTED]> wrote:
>
> > After this fact the colliding block is itself very interesting,
> > aand it is also very likely that theis block will be stored and
> > archived just for this reason.
>
> Which will increase the chance of a failure ;-O
>
> > In practice though, a filesystem relying on venti could just
> > change the block boundaries for this case or choose some other
> > escape from needing to store these special blocks.
>
> hmm, let's assume, the scientists will come up with (maybe
> artificially constructed) collissions long before they'll
> happen in practice, we could handle them specially. All we
> need to do is to leave enough room in the keyspace, so we
> can assign them to these special blocks, once they've been
> discovered.
>
> A simple way could simply be an additional bit, which tells
> us that the key isn't the data's hash, but an explicitly
> assigned dictionary entry.
>
> Maybe a more sophisticated approach: add an keytype prefix,
> which allows dropping in several types of keys. Default might
> be sha-1, but for special cases another keytype (eg. "dict")
> can be used.
>
>
>
> cu
> --
> ---------------------------------------------------------------------
>  Enrico Weigelt    ==   metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
>  Please visit the OpenSource QM Taskforce:
>        http://wiki.metux.de/public/OpenSource_QM_Taskforce
>  Patches / Fixes for a lot dozens of packages in dozens of versions:
>        http://patches.metux.de/
> ---------------------------------------------------------------------
>

Reply via email to