UltraVNC 1.0.2 (bis) version is online for Testing

Post by **UltraSam** » 2006-05-30 21:06

http://sc.uvnc.com/UltraVNC-1.0.2-bis-Test-Setup.exe
http://sc.uvnc.com/UltraVNC-1.0.2-bis-Test-binaries.zip

** v1.0.2 Release

- Larger FileTransfer window (fits on 1024*768 screens, but no more on 800*600 screens)
- Improved cursor handling in viewer and javaviewer
- Improved Autoreconnect option in server
- Improved query-on-incoming-connection window in server
- MSLogon improvements
- MSLogon weak challenge vulnerability fix
- Server and viewer logging functions vulnerability fix

Are NOT included for now:
- New Nat2Nat connector
- Icons
- doc
- tabbed-viewer (modified .rc for FT not yet included)

Please test in priority the whole MSLogon authentication thing (also with the JavaViewer)
Please check that the FT window has no more cosmetics problems

As soon as these 2 things are validated we can put the v1.0.2 online and continue to fix more bugs for v1.0.3

Thanks for your help and feedback

Marscha · Post by **Marscha** » 2006-05-31 06:56

Please notice that the mslogon fix introduces a change in the protocol.
I.e. you cannot use a 1.0.1 (or older) viewer (vncviewer or JavaViewer) with a 1.0.2 winvnc using mslogon.
You can do it the other way round (1.0.1 winvnc with 1.0.2 viewer) but then you're still using the unsecure protocol.

roytam1 · Post by **roytam1** » 2006-05-31 09:05

I hope the changes of 1.0.2 bis can commit to CVS so that I can futher test them.

For the FT, progress bar/labels values don't reset if user pressed "Stop" button.

Post by **UltraSam** » 2006-05-31 09:44

roytam1 wrote:I hope the changes of 1.0.2 bis can commit to CVS so that I can futher test them.

Normally CVS should already be updated.

roytam1 wrote: For the FT, progress bar/labels values don't reset if user pressed "Stop" button.

Ok. I like it this way but if it's considered as a bug...

OPERATOR · Post by **OPERATOR** » 2006-05-31 09:50

The Translation dlls will be ignored.

Code: Select all

To have a german or french viewer interface, copy the corresponding
langauage dll as vnclang.dll in the same directory as the viewer

copy french.dll vnclang.dll
move it to the same directory as the viewer

/vncviewer.exe
/vnclang.dll

Post by **Rudi De Vos** » 2006-05-31 09:58

Name change from lang.dll to vnclang.dll.

This was needed because some systems had an existing lang.dll in the window directory ( from an other app).
Natural this would cause the viewer to start with no resources at all and generate a (!) error .

roytam1 · Post by **roytam1** » 2006-05-31 10:07

UltraSam wrote:
roytam1 wrote:I hope the changes of 1.0.2 bis can commit to CVS so that I can futher test them.
Normally CVS should already be updated.

If so that means my code is the latest. Great!

UltraSam wrote:
roytam1 wrote: For the FT, progress bar/labels values don't reset if user pressed "Stop" button.
Ok. I like it this way but if it's considered as a bug...

Oh I see. This is a feature... xD

prandal · Post by **prandal** » 2006-05-31 14:10

Marscha wrote:Please notice that the mslogon fix introduces a change in the protocol.
I.e. you cannot use a 1.0.1 (or older) viewer (vncviewer or JavaViewer) with a 1.0.2 winvnc using mslogon.
You can do it the other way round (1.0.1 winvnc with 1.0.2 viewer) but then you're still using the unsecure protocol.

Both the readme.txt and whatsnew.txt should have this information as near to the top as possible, preferately in capital letters so people notice it. Neither currently mention this.

Upgrading's going to be a nightmare

Phil

prandal · Post by **prandal** » 2006-05-31 14:15

prandal wrote:
Marscha wrote:Please notice that the mslogon fix introduces a change in the protocol.
I.e. you cannot use a 1.0.1 (or older) viewer (vncviewer or JavaViewer) with a 1.0.2 winvnc using mslogon.
You can do it the other way round (1.0.1 winvnc with 1.0.2 viewer) but then you're still using the unsecure protocol.
Both the readme.txt and whatsnew.txt should have this information as near to the top as possible, preferately in capital letters so people notice it. Neither currently mention this.

Upgrading's going to be a nightmare

Phil

Oh, and that alert box warning about password insecurity is going to be a right nuisance. We have to update all our users' vncviewers before we can update the servers, and people not in a position to update the servers are going to be nagged to death during the viewer rollout.... Which means my phone will be ringing nonstop... Arrrrgh...

Phil

Post by **UltraSam** » 2006-05-31 14:22

prandal wrote:
prandal wrote:
Marscha wrote:Please notice that the mslogon fix introduces a change in the protocol.
I.e. you cannot use a 1.0.1 (or older) viewer (vncviewer or JavaViewer) with a 1.0.2 winvnc using mslogon.
You can do it the other way round (1.0.1 winvnc with 1.0.2 viewer) but then you're still using the unsecure protocol.
Both the readme.txt and whatsnew.txt should have this information as near to the top as possible, preferately in capital letters so people notice it. Neither currently mention this.

Upgrading's going to be a nightmare

Phil
Oh, and that alert box warning about password insecurity is going to be a right nuisance. We have to update all our users' vncviewers before we can update the servers, and people not in a position to update the servers are going to be nagged to death during the viewer rollout.... Which means my phone will be ringing nonstop... Arrrrgh...

Phil

It's just a Test build...

We will underline the broken backward compatibility in the whatsnew.txt file.

What do you suggest instead of the popup ?
- No popup but connection rejected ?
- Another more accurate message ?

And if all your viewers use the DSMPlugin are are VPN tunneled upgrading to 1.0.2 is NOT mandatory as the 1.0.1 weak MSLogon challenge data is strongly encrypted anyway.

prandal · Post by **prandal** » 2006-05-31 14:50

This is one case where security via obscurity might be desirable... No warning at all.

Marscha · Post by **Marscha** » 2006-06-01 06:34

@Sam: the vncviewer still claims to be 1.0.1, could you please update the VERSIONINFO.
I tested MS-Logon with new vncviewer/Javaviewer against new winvnc. Seems to be OK.

@prandal: I'm not sure if obscurity is an option here.
There is already a tool available on the web that grabs the Windows password from the mslogon authentication.
I think there has to be some pressure to update insecure servers.
Otherwise you won't notice that you're still using the old insecure protocol even with the new vncviewer.

roytam1 · Post by **roytam1** » 2006-06-01 10:22

Old UltraVNC clients can't use FT with 1.0.2 server.
Is it a bug?

Post by **UltraSam** » 2006-06-01 13:23

Should work as with v1.0.1 version...

No modif at this level in v1.0.2

roytam1 · Post by **roytam1** » 2006-06-01 13:56

UltraSam wrote:Should work as with v1.0.1 version...

No modif at this level in v1.0.2

You're right. The FTv1 clients (prior to RC19) can't.

[EDIT] Typo. [/EDIT]

prandal · Post by **prandal** » 2006-06-07 10:23

Marscha wrote: @prandal: I'm not sure if obscurity is an option here.
There is already a tool available on the web that grabs the Windows password from the mslogon authentication.
I think there has to be some pressure to update insecure servers.
Otherwise you won't notice that you're still using the old insecure protocol even with the new vncviewer.

Yes, but you're nagging the people who aren't in control of the servers.... And I have to roll out the new VNC Viewer to everyone before I can touch any of the servers.

Nightmare.

In the real world, people won't bother with all the hassle and stay on 1.0.1, which is the worst possible scenario.

Just my 2p worth...

Phil

Marscha · Post by **Marscha** » 2006-06-07 15:38

ok, I'll consider this.
Maybe there's another way to inform the users.

Marscha · Post by **Marscha** » 2006-06-08 14:39

Now I changed the warning:
It's no longer a separate dialog window.
It's just a text integrated in the authentication dialog.
Requires no further buttons to be clicked.
Updated CVS and SVN.

Post by **UltraSam** » 2006-06-09 09:26

Ok. New pre-release binaries and setup will be put online this WE with the latest modifs:
- MS Logon fix adjustements
- Resizable FT window
- ...

redge · Post by **redge** » 2006-06-12 07:30

vncviewer + winvnc 1.0.2 built: 30.05.2006
OS: XP Home (uwinvnc) and XP Pro (uvncviewer)

"%programfiles%\UltraVNC\vncviewer.exe" -noauto -encoding hextile -connect 192.168.1.100

or

"%programfiles%\UltraVNC\vncviewer.exe" -noauto -encoding zlib -connect 192.168.1.100

depend of WLAN quality product or bug of winvnc/vncviewer ?

symptom:
winvnc reboot the broadband product WLAN immediately after connect or fews second later
or
winvnc close after 3-10 min unexpectly without any error message.

kger · Post by **kger** » 2006-06-12 15:51

UltraSam wrote:Ok. New pre-release binaries and setup will be put online this WE with the latest modifs:
- MS Logon fix adjustements
- Resizable FT window
- ...

Thanks for your continued work on this.

Available yet? URL?

Post by **UltraSam** » 2006-06-16 08:26

Not yet...
I had unplanned things to do on last WE.

Will be online by the end of the upcoming WE, this time...

Sorry for the delay...

kger · Post by **kger** » 2006-06-16 14:13

No problem. Weekends go that way sometimes.

sure · Post by **sure** » 2006-06-27 10:18

Is this version available for the online SC compiler?
What viewer can I use for the SC version?

What version is better to use for compiling SC and why?
The RC23 or the RL1.00 ? I can't find this info anywhere.
What version *should* be used to listen at either of those?

spuri · Post by **spuri** » 2006-06-27 13:14

where can i find more details about "Improved query-on-incoming-connection window in server" ?

i would like to get "query window" when somebody is logged on and free access when nobody loged in, is it possible?

Marscha · Post by **Marscha** » 2006-06-27 14:52

Could 1.0.2 finally be released?
There are several security fixes included and I think it's important to have it out now soon.
I don't see any showstoppers.

Post by **UltraSam** » 2006-06-27 21:38

Yep. The setup is ready, I have the latest DsmPlugins from Sean.

1.0.2 will be released hopefully tomorrow evening.

bevtech · Post by **bevtech** » 2006-06-28 16:18

Will is support a mutiple DSM stream??? Encyption on more then one tab without a crash???

jzhang · Post by **jzhang** » 2006-06-28 20:18

I have a question concerning 1.0.2, if some one can give me some help.

Release Version 1.0.1, autocaling is not working properly, I tested with tabbed_viewer 1.28; when I set autoscaling, then the image is stretched etc.
it is a very good feature I want to have;
My Questions are:

1) in the 1.0.2, do we have this feature;

2) I tried to implement myself, I used the memory copy of image to stretch to right size in the DoBlit() function, but it put whole screen to the small blocks; if I create my ower function just stretch the image if the WM_SIZE event has received, i can't see the update of mouse pointer;

I compared Release 1.0.1, and Release tabbed_viewer 1.28. there are a lot of differences;

could some one point me to a shortcut to do it?

I appreciate your help very much;

Jz

redndahead · Post by **redndahead** » 2006-06-30 17:56

UltraSam wrote:Yep. The setup is ready, I have the latest DsmPlugins from Sean.

1.0.2 will be released hopefully tomorrow evening.

Sorry to ask when is it going to be ready, but is there a major hang up at the moment? Also how much different is the newest beta going to be from the final version?

Adam

UltraVNC

UltraVNC 1.0.2 (bis) version is online for Testing

UltraVNC 1.0.2 (bis) version is online for Testing

vncviewer.exe" -noauto -encoding hextile -connect 192.1

Re: UltraVNC 1.0.2 (bis) version is online for Testing

Re: UltraVNC 1.0.2 (bis) version is online for Testing

Re: UltraVNC 1.0.2 (bis) version is online for Testing

Re: UltraVNC 1.0.2 (bis) version is online for Testing

Re: UltraVNC 1.0.2 (bis) version is online for Testing

Re: UltraVNC 1.0.2 (bis) version is online for Testing

Re: UltraVNC 1.0.2 (bis) version is online for Testing