----- Original Message -----
From: "Stefan Reich" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 11, 2001 2:34 PM
Subject: Re: [freenet-tech] Ideas for a FreeNet Process
> > > Not a problem; just write a function that can scan any arbitrary piece
> of
> > > code and determine whether it will eventually halt or not.
> >
> > Right in other words, the freenet could determine cancer nodes and deal
> with
> > them.
>
> Ahm... I think you missed out on the irony in that statement... it is
> IMPOSSIBLE to write an algorithm that decides if a given piece of code
will
> halt eventually (i think Turing proved that).
Allan lived in the world of abstraction.
I believe the real axiom is that a process cannot determine itself.
Which means that a process cannot determine whether itself will halt. It
cant predict itself.
The program IS the prediction.
Of course other programs could analyze any other program or expect certain
things from it.
For example. I am a progem. You write an infinite loop. I determine that
it will be infinite. I've just
predicted your program.
Freenet nodes would not work today if the nodes waited indefinitely for
other nodes to finish. The
good nodes also would not like to get 'bad' information from so called
cancerous nodes.
The same procedures would of course be applied. This not only helps
identify attacks, but more importantly identifies pieces of the process that
are not functioning properly, or in hacker terms buggy.
HKF
>
> I think you still don't understand the problem with the execution of
> untrusted code (is it so unobvious?).
>
> -Stefan
>
>
> _______________________________________________
> freenet-tech mailing list
> [EMAIL PROTECTED]
> http://lists.freenetproject.org/mailman/listinfo/tech
>
_______________________________________________
freenet-tech mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/tech
