> LoopbackOnly
> By default, WinVNC servers accept incoming connections on any
> network adapter address, since this is the easiest way of coping
> with multihomed machines. In some cases, it is preferable to listen
> only for connections originating from the local machine and aimed
> at the "localhost" adapter - a particular example is the use of VNC
> over SSH to provide secure VNC. Setting this registry entry to 1
> will cause WinVNC to only accept local connections - this
> overrides the AllowLoopback and AuthHosts settings. Setting this
> entry to zero causes WinVNC to accept connections on any
> adapter and is the default setting.Local machine-specific setting.
>
> from page http://www.uk.research.att.com/vnc/winvnc.html
>
> I had to install LoopbackOnly *and* AllowLoopback to get
> LoopbackOnly connects. Btw., is LoopbackOnly redundant with
> the possibility to ause AllowHost with 127.0.0.1?
>
> And a second note:
>
> In my setup I have AllowLoopback as REG_DWORD and
> LoopbackOnly as REG_SZ. Not very consistent ...
That will be why you have to set AllowLoopback manually - LoopbackOnly isn't
having any effect, since it is expected to be a DWORD and you have set it to
a zero-terminated string.
AuthHosts "-:+127.0.0.1" listens on all adaptors and rejects connections
from any external address other than 127.0.0.1. LoopbackOnly only listens
on the loopback adaptor, so the only possible address of a connecting
connection is 127.0.0.1. They are not the same thing.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
