[topic=637][/topic]

[larjohns]

Thanks, Sergio. I was able to track down a download. It's odd, but the new mslogon2 does not appear to work for my Win2k box that is serving the connection. I'm still using RC18, in fact, as the readme suggests, all I did was stop WINVNC service, copy in the new executable, start the service, place the new DWORD value in the registry, and put the new dll in the installation directory. All I get when using mslogon is VNC Authentication failed!

I was closer with the other mslogon - again to reiterate my problem: we can authenticate, but we can't save the connections so that one-finger-typing curmudgeons can save three dozen little icons that prevent them from having to type their network logins over and over all day as they move from computer to computer via VNC.

Assistance please.

Jay

[larjohns]

In error, i created a new topic rather than appending the 'Can't Save Connection Topic' that I was using to get feedback on our problem.

[larjohns]

can you save the connection info including ms logon and password using mslogon1?

[Marscha]

mslogon2 does not save username/password in the connections info.
First I have to get mslogon2 reliable and stable, then I'll consider saving the username.
I don't know if saving the password is a good idea in terms of security.
Another related and maybe even more important feature is to just use the users logon credentials to authenticate a vnc connection, but I guess that this is more difficult to implement, requiring changes in the protocol.

[larjohns]

Yes, Marscha, that would be a great idea.

[quote]I don't know if saving the password is a good idea in terms of security.[/quote]

Agreed...in normal circumstances. In this case, all users are behind a pix firewall, and the computers currently have RealVNC on every box, running on the standard 5900 port, ALL using the exact same username.

Our idea with UltraVNC was to at least step up to requiring a network username and password. As I have mentioned, several in our group are resisting this as they can probably only type with one finger. I told them they would be able to save their usernames and passwords.

So my question remains unanswered: why can some people save the u/p and some can't?

[Marscha]

larjohns,

seems that you are in a similar situation like me, we also consider moving from an old vnc version to ultravnc ...
Regarding the info file, I checked the source and I can't see that username/password is saved, only password.

Martin

[larjohns]

That's odd, M. It seems to work for some of us but not others. Any idea what that is all about, or what variables I can provide to you that might help us determine why it works for some but not others?

[Marscha]

it's odd, I just looked at the code (in ClientConnectionFile.cpp):

Code: Select all

	int ret = WritePrivateProfileString("connection", "host", m_host, fname);
	char buf[32];
	sprintf(buf, "%d", m_port);
	WritePrivateProfileString("connection", "port", buf, fname);

	ret = WritePrivateProfileString("connection", "proxyhost", m_proxyhost, fname);
	sprintf(buf, "%d", m_proxyport);
	WritePrivateProfileString("connection", "proxyport", buf, fname);

	if (MessageBox(m_hwnd,
		sz_K3,  
		sz_K4, 
		MB_YESNO | MB_ICONWARNING) == IDYES) 
	{
		for (int i = 0; i < MAXPWLEN; i++) {
			sprintf(buf+i*2, "%02x", (unsigned int) m_encPasswd[i]);
		}
	} else
		buf[0] = '\0';
	WritePrivateProfileString("connection", "password", buf, fname);

So this is host, port, proxyhost, proxyport and password.
In addition a number of options is saved to the file, but no username.

[larjohns]

It appears that amongst our curmudgeons are also a pair that doesn't listen very well. After taking this info that you posted above, Marscha, I was able to weed out their claims. It appears that their 'saved' connections were not the the test box that is running the mslogon authentication.

My apologies for this misleading thread. I look forward to a version of mslogon that will allow us to save this connection info, for now, though, it seems, that our team will still share a common password.