On Thursday 04 June 2009 17:09:51 sich wrote:
> Matthew Toseland a ?crit :
> > SSKs are 1KB and have rather high overheads. You need to insert a bunch of
> > CHKs under the SSK, and to make that safe you need the CHK data to be
> > encrypted. But also you need it for security, because *the SSK is
On Thursday 04 June 2009 17:09:51 sich wrote:
> Matthew Toseland a écrit :
> > SSKs are 1KB and have rather high overheads. You need to insert a bunch of
> > CHKs under the SSK, and to make that safe you need the CHK data to be
> > encrypted. But also you need it for security, because *the SSK is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland a ?crit :
> You should seriously consider working with infinity0, his searching plugin
> will provide distributed indexing.
good neews :)
> Why are you splitting the files up? Are you assuming that the key changes
> every time for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland a ?crit :
> SSKs are 1KB and have rather high overheads. You need to insert a bunch of
> CHKs under the SSK, and to make that safe you need the CHK data to be
> encrypted. But also you need it for security, because *the SSK is
> pre
On Wednesday 03 June 2009 23:25:38 Cl?ment wrote:
> On Wednesday 03 June 2009 23:25:56 Matthew Toseland wrote:
> > On Tuesday 02 June 2009 19:41:51 clement wrote:
> > > Hello,
> > >
> > > Here is some try from Sich and myself to think about the design for some
> > > insert on demand application bas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland a écrit :
> You should seriously consider working with infinity0, his searching plugin
> will provide distributed indexing.
good neews :)
> Why are you splitting the files up? Are you assuming that the key changes
> every time for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland a écrit :
> SSKs are 1KB and have rather high overheads. You need to insert a bunch of
> CHKs under the SSK, and to make that safe you need the CHK data to be
> encrypted. But also you need it for security, because *the SSK is
> pre
On Wednesday 03 June 2009 23:25:38 Clément wrote:
> On Wednesday 03 June 2009 23:25:56 Matthew Toseland wrote:
> > On Tuesday 02 June 2009 19:41:51 clement wrote:
> > > Hello,
> > >
> > > Here is some try from Sich and myself to think about the design for some
> > > insert on demand application bas
On Wednesday 03 June 2009 23:25:56 Matthew Toseland wrote:
> On Tuesday 02 June 2009 19:41:51 clement wrote:
> > Hello,
> >
> > Here is some try from Sich and myself to think about the design for some
> > insert on demand application based on the WoT plugin.
>
> You should seriously consider workin
On Tuesday 02 June 2009 19:41:51 clement wrote:
> Hello,
>
> Here is some try from Sich and myself to think about the design for some
> insert on demand application based on the WoT plugin.
You should seriously consider working with infinity0, his searching plugin will
provide distributed index
On Wednesday 03 June 2009 23:25:56 Matthew Toseland wrote:
> On Tuesday 02 June 2009 19:41:51 clement wrote:
> > Hello,
> >
> > Here is some try from Sich and myself to think about the design for some
> > insert on demand application based on the WoT plugin.
>
> You should seriously consider workin
On Tuesday 02 June 2009 19:41:51 clement wrote:
> Hello,
>
> Here is some try from Sich and myself to think about the design for some
> insert on demand application based on the WoT plugin.
You should seriously consider working with infinity0, his searching plugin will
provide distributed index
Hello,
Here is some try from Sich and myself to think about the design for some
insert on demand application based on the WoT plugin.
---
key structure :
ssk/filesharing/updates/inserts/x/inserts
ssk/f
Hello,
Here is some try from Sich and myself to think about the design for some
insert on demand application based on the WoT plugin.
---
key structure :
ssk/filesharing/updates/inserts/x/inserts
ssk/f
14 matches
Mail list logo
