[freenet-support] *.allowedHost does not work since update!!!!!!!

2002-09-05 Thread Thomas Goebel

Hello,

any setup with

destatus.allowedHosts, fproxy.allowedHosts, nodeinfo.allowedHost,
nodestatus.allowedHost, console.allowedHost
has no effect.

All hosts can access all freenet services.

Please tell this the developer.

Regards,
Thomas

___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support



Re: [freenet-support] *.allowedHost does not work since update!!!!!!!

2002-09-05 Thread Greg Wooledge

Thomas Goebel ([EMAIL PROTECTED]) wrote:

 any setup with
 
 destatus.allowedHosts, fproxy.allowedHosts, nodeinfo.allowedHost,
 nodestatus.allowedHost, console.allowedHost
 has no effect.
 
 All hosts can access all freenet services.

I cannot confirm this.  Please give more details (exactly which
build number you are running, actual contents of allowedHosts
parameters in the config file, IP address of node, IP address of
client machine you tested from).

 Please tell this the developer.

They seem to read [EMAIL PROTECTED] and not this list.  I
suggest you write to that address.  (You'll have to be subscribed;
Ian Clarke himself admitted that posts from non-subscribers go into
a black hole.)

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |



msg01081/pgp0.pgp
Description: PGP signature