Igor:
I think we're saying the same thing. :) Please see my
#1 thru #4 below, from Saturday 04 May 2002.
I agree that once Kaboodle sets AllowLoopback, it doesn't
need to erase it. However, even if it does erase it, the problem
is simply to restart the server. Please see #2 from that 04 May
email: when the user activates "Enable Kaboodle Tunnels" for the
first time, the "Let Kaboodle auto-start..." checkbox should then
activate, automatically, by default, whenever the WinVNC.exe search
is non-empty. Please confirm that this is your understanding too.
If we implement it this way, the user would have to
*de-select* the auto-start checkbox, and then answer "I'll Do It
Later" to the subsequent MessageBox.
-Scott
On Tue, 7 May 2002, Igor Kotelevsky wrote:
> Hello Scott.
>
> In my last e-mail I said you about following case.
> 1) - Kaboodle on PC1 have checked "Enable Kaboodle Tunnels for VNC"
> 2) - Kaboodle on PC1 have not checked "Let Kaboodle auto start and restart
> the VNC Server..."
> 3) - PC1 is running an independent VNC Server
>
> User on PC2 push "Connect through Kaboodle(more secure)".
>
> Kaboodle on PC1 see #3.
> Kaboodle on PC1 must do following
> a)change VNC Server key AllowLoopback, without this change independent VNC
> Server will not work propertly.
> b) restart VNC Server.
> But because of #2 Kaboodle on PC1 cannot do #b.
>
> Now I have other suggestion.
> Every time when user check "Enable Kaboodle Tunnels for VNC",
> then Kaboodle save VNC Server key AllowLoopback.
> Kaboodle never not restore this change.
> This offer has the following advantages.
> - Above situation is not possible,
> - When there is checked "Let Kaboodle auto start and restart the VNC
> Server...", and
> there is running an independent VNC Server, Kaboodle no needs to restart VNC
> Server
> (if there is not checked "All VNC use must be through a Kaboodle tunnel").
> VNC connection will be more faster.
> It seems to me that this suggestion not worsen security of VNC.
>
> -Igor
>
>
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> Sent: Tuesday, May 07, 2002 10:44 AM
> Subject: Re: Independent VNC server problem
>
>
> > Igor:
> > I don't think this additional MessageBox is needed.
> > If Kaboodle on MyMachine is not running an independent VNC
> > server, and if I don't have that Checkbox selected, then we
> > should update the other Kaboodle instances on the LAN so
> > that they cannot initiate a VNC session to MyMachine. That
> > is, its status should change from active to inactive server,
> > so the Connect buttons won't work.
> >
> > That and one other VNC feature are still pending.
> > So, for this week, lets finish:
> >
> > 1. The VNC algorithm you described last week
> > 2. VNC Server Status column added into the list in the
> > VNC Service Icon.
> > 3. The log file Checkbox I described last week.
> >
> > Please confirm when you can. Thanks!
> >
> > -Scott
> >
> >
> > On Mon, 6 May 2002, Igor Kotelevsky wrote:
> >
> > > Hello Scott.
> > > We have to insert additional MessageBox when
> > > independent VNC server not running and user have not checked the
> Kaboodle
> > > option.
> > > <Let Kaboodle auto start and restart the VNC Server\nwhen it needs to>
> > >
> > > "A Kaboodle user on <IP address"
> > > "has tried to connect to this machine with VNC"
> > > "You have not checked the Kaboodle option"
> > > "<Let Kaboodle auto start and restart the VNC Server\nwhen it needs to>"
> > > There are two buttons "Let Kaboodle restart VNC Server now", "Cancel
> > > connection"
> > >
> > > -Igor
> > >
> > >
> > > ----- Original Message -----
> > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > Cc: <[EMAIL PROTECTED]>
> > > Sent: Saturday, May 04, 2002 12:31 AM
> > > Subject: Re: Independent VNC server problem
> > >
> > >
> > > > Igor:
> > > > Some thoughts on what you're seeing:
> > > >
> > > > 1. If PC1 is running an independent VNC server with Kaboodle, and
> > > > "Enable Kaboodle Tunnels for VNC" is set, then AllowLoopback
> > > > should be set. That's what "Enable Kaboodle Tunnels" is
> > > > supposed to do: set that registry key. Whenever Kaboodle is
> > > > running and this Checkbox is selected, that key should be set.
> > > >
> > > > 2. Let's change the Checkbox which reads "Use Kaboodle to startup
> > > > VNC Server only when it's needed" to read "Let Kaboodle auto
> > > > start and restart the VNC Server when it needs to". If this
> > > > box is selected, Kaboodle won't prompt the user when it makes
> > > > a change to the VNC registry and restarts the VNC service.
> > > > When the user first activates the "Enable Kaboodle Tunnels"
> > > > checkbox, we should activate this checkbox by default if
> > > > Kaboodle finds a WinVNC.exe server.
> > > >
> > > > 3. If Kaboodle makes any changes to the VNC registry, and the
> > > > user clicks "Okay", and the "Let Kaboodle..." checkbox from #2
> > > > is not selected, it should prompt the user with "Your VNC
> > > > Server needs to be restarted for these Kaboodle settings to
> > > > take effect." We can have two buttons: "Let Kaboodle Do this
> > > > Now" and "I'll Do This Later".
> > > >
> > > > 4. If Kaboodle is started up with some VNC Server settings that
> > > > require changes to the VNC Registry, we'll need to prompt the
> > > > user in the same way as #3 if the "Let Kaboodle..." checkbox
> > > > of #2 is not selected. If it is selected, we can just make
> > > > the changes and quietly restart the VNC service.
> > > >
> > > > Sound good?
> > > >
> > > > -Scott
> > > >
> > > >
> > > > On Fri, 3 May 2002, Igor Kotelevsky wrote:
> > > >
> > > > > Hello Scott.
> > > > > I have found a following problem of the independent VNC server.
> > > > > PC1 is running independent VNC server and Kaboodle.
> > > > > Kaboodle on PC1 is "Enable Kaboodle Tunnels for VNC".
> > > > > User on PC2 checks radio button "Connect through Kaboodle (more
> secure)"
> > > and
> > > > > push button "Connect".
> > > > > Then user on PC2 see MessageBox("Local loop-back connection are
> > > disabled").
> > > > > The caption of this MessageBox is "VNC info".
> > > > > In this case Kaboodle on PC1 tries to connect with own VNC server on
> IP
> > > > > address of the LAN interface,
> > > > > and if it failed, then on loopback IP address...
> > > > >
> > > > > I have checked the source code of WinVNC server.
> > > > > I have found that in above case Kaboodle have to set VNC server
> registry
> > > key
> > > > > *AllowLoopback*.
> > > > > It is not difficult. But Kaboodle have to show MessageBox("The VNC
> > > Service
> > > > > needs to be restarted...").
> > > > >
> > > > > I have following suggestion.
> > > > > - Kaboodle checks VNC server registry key *AllowLoopback*.
> > > > > - If there is not above key, then Kaboodle show next MessageBox
> > > > > "Kaboodle have to put VNC server registry key *AllowLoopback* and
> > > restart
> > > > > VNC server."
> > > > > "Kaboodle don't will restore above key at the finishing of the VNC
> > > session".
> > > > > There are two buttons: "Let Kaboodle do this now", "Cancel VNC
> session".
> > > > >
> > > > > -Igor
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
