Working out whether or not a design is vulnerable to various attacks is
complicated... When hashed file storage is isolated from Freenet into a
separate network of nodes ostensibly devoted to research into hash
collisions (call it SETHC, the Search for Extra Terrestrial Hash
Collisions), we need
Regarding node specialization, I think that given enough nodes, duplicate
specialization areas should appear while covering a wide spectrum of keys.
On a graph of CHKs [x-axis] (if I understand things correctly) over
concentration [y-axis] of keys for multiple nodes, that would appear as
At 18.58 29/04/2003 -0700, you wrote:
>It is increasingly obvious that the fact that several of the indexes we
I waited till now, when the flame is over, to post my
2 eurocent.
I personally agree with the index link directly in the
fproxy page, but think that their presence is not
a main
On Sun, 2003-05-04 at 15:46, jrandom wrote:
> > I argue that Freenet must provide an interface to automatically
> > accept DMCA notices demanding suppression of particular CHK's,
> > or else it will be shut down once it becomes popular enough to
> > warrant attention.
>
> Understandable
This is the weekly Freenet Project job jar update.
Comments to devl at freenetproject.org or jobjar at hawk.freenetproject.org
OPEN JOBS
-
* Incorporate an official bug tracking system into the main
freenetproject.org web site. Candidates are Adam's FNBTS,
the SourceForge bug
On Sun, 2003-05-04 at 12:20, Ian Clarke wrote:
> > Moglen points out exactly what my "legal" compression is
> > intended to make obvious: the law must treat some numbers
> > differently than others, and this is absurd.
>
> What if I send my friend a signed email saying "If you kill Oskar, I
>
On Sat, 2003-05-03 at 19:35, Toad wrote:
> I am not sure that we could safely allow a get file closest to
> this key command... it might allow some kinds of probing/mapping that
> might lead to attacks we would want to avoid. On the other hand, it is
> an interesting idea.
>
Thanks for taking
