MSRC4 + Ubuntu (as viewer) + Single click = Problem

[Kasutajakene]

Hello from Estonia. I have a problem with getting Single Click working with msrc4 plugin. I created singleclick.exe file with newest MSRC4 plugin and 128 bit rc4.key in it. Also multiple hosts with or without -plugin (for testing). So after messing with tightvncviewer, ultravnc_dsm_helper and Singleclick.exe for a day I tested in Windows to Windows without encryption, which was succesful. Then also worked with Encryption. Then went back to Linux-to-Windows system and tried with tightvncviewer

Code: Select all

ssvnc/bin$ ./tightvncviewer -listen -encodings "hextile"

and on the singleclick I chose without -plugin. Once again, worked fine. So I can connect to windows single click server within ubuntu using ssvnc with no problems at all. But here comes to problem: I can´t get it to work with encryption.

Code: Select all

ssvnc/bin$ ./tightvncviewer -ultradsm -listen 1 -encodings "hextile"

Code: Select all

ssvnc/bin/Linux.i686# ./ultra_vnc_helper msrc4_sc ./rc4.key 5500 localhost:5501

rc4.key is same as was in singleclick.zip archieve. So what happens when I try to acces it without with or without -plugin:
ultradsm section
ultravnc_dsm_helper: waiting for connection on port: 5500
ultravnc_dsm_helper: got connection: 4
ultravnc_dsm_helper: encrypt - WARNING: MSRC4 mode and IGNORING random salt
ultravnc_dsm_helper: encrypt - WARNING: and initialization vector!!
ultravnc_dsm_helper: decrypt finished

ultravnc_dsm_helper: decrypt - close sock_to
ultravnc_dsm_helper: decrypt - close sock_tr
ultravnc_dsm_helper[12020]: decrypt - killed my partner: 12022
tightvncviewer
Not a valid VNC server: '�(�~qw��R�X'
ShmCleanup called

VNC Viewer exiting


So basically what I am trying to do is use ultravnc_dsm_helper (udh for shorter) as middleman. So udh listens to sc server and then delivers info to tightvncviewer. As soon as tightvncviewer gets a knock knock from udh, it should send message back to udh and that to sc server. Few questions:
1) Are commands right?
2) The last text, have I misunderstood the operation or?
3) what version is msrc4_sc in ultravnc_dsm_helper? (and it should be same as in singleclick.exe)?
Sorry for my English and waiting for response. Thanks in advance

[krunge]

Try running with:

Code: Select all

./ultra_vnc_helper rev:msrc4_sc ./rc4.key 5500 localhost:5501

i.e. add the "rev:" tag.

Does it work for you via the SSVNC gui? If, so then you can use 'ps' to find the commands running and their cmdline arguments. That's how I was reminded "rev:" is needed for reverse connections.

BTW, it seems the SSVNC gui sets SSVNC_ULTRA_DSM=1 in the environment instead of using -ultradsm, but both should be equivalent.

[Kasutajakene]

Thanks for response. I never actually got gui to work (I have understood that ssvnc in linux is purely on CLI, because:)

Code: Select all

it@it-laptop:~/Desktop/ssvnc/Unix$ ls
sshvnc  ssvnc  tsvnc
it@it-laptop:~/Desktop/ssvnc/Unix$ ./ssvnc 
exec: 3: wish: not found

. I thought I have tried with rev, but it seams that I should document what I have done and what I haven´t (a week ago I tried rev:msrc4 not rev:msrc4_sc, so thats why I gave up on rev.
So for the first time I ssvnc nor udh doesn´t shut down.

ssvnc
Proto: RFB 003.016

Setting RFB version to 3.3 for UltraVNC Single Click.

Connected to RFB server, using protocol version 3.3

ultravnc_dsm_helper
ultravnc_dsm_helper: waiting for connection on port: 5500
ultravnc_dsm_helper: got connection: 4
ultravnc_dsm_helper: encrypt - WARNING: MSRC4 mode and IGNORING random salt
ultravnc_dsm_helper: encrypt - WARNING: and initialization vector!!
ultravnc_dsm_helper: decrypt - WARNING: MSRC4 mode and IGNORING random salt
ultravnc_dsm_helper: decrypt - WARNING: and initialization vector!!

So things are looking better, but I don´t get screen of the remote host and singleclick.exe in tray is still waiting for connection to come in. And when I close singeclick in remote host then ssvnc viewer says: VNC Server closed connection and
udh says:
ultravnc_dsm_helper: decrypt - input stream finished: n=0, err=0
ultravnc_dsm_helper: decrypt - close sock_to
ultravnc_dsm_helper: decrypt - close sock_fr
ultravnc_dsm_helper[6240]: decrypt - killed my partner: 5819
Terminated

So basically, now I´m totally lost as I don´t undestand how singleclick doesn´t understand that viewer is connected to him and why don´t I get remote hosts screen (it might be involved to last issue)

[krunge]

it@it-laptop:~/Desktop/ssvnc/Unix$ ./ssvnc

exec: 3: wish: not found

You need to add the 'tk' package. E.g. 'apt-get install tk' or if that doesn't work 'apt-get install tk8.4'.

Then try it from the ssvnc gui: 'Options -> Reverse VNC Connections' and 'Options -> Advanced -> UltraVNC DSM Encryption Plugin' Report back what happens.

[Kasutajakene]

I tried without encryption just to try the GUI out and it worked. So I chose UltraVNC DSM Encryption Plugin,where I chose exacly same rc4.key file as in my singleclick.exe and selected UVNC_SC as Type of Key and after that I started "Listening". Program itself putted:

Code: Select all

ultravnc_dsm_helper rev:msrc4_sc /path/to/rc4.key 5500 localhost:5530 and &

aka exacly same line as I tried before, but it continues...

Code: Select all

open: Permission denied

???

Code: Select all

vncviewer -noraiseonbeep -encodings copyrect tight zrle zlib hextile -listen 30

and the final part:

Code: Select all

vncviewer -listen: Listening on port 5530
vncviewer -listen: Cmdline error are not reported until a connection comes in. 

I double checked singleclick.exe ports and they were correct (5500 that is) and asap as start singleclick.exe the viewer doesn´t get any connection!!!

[krunge]

Code: Select all

ultravnc_dsm_helper rev:msrc4_sc /path/to/rc4.key 5500 localhost:5530 and &

aka exacly same line as I tried before, but it continues...

Code: Select all

open: Permission denied

???

I'm pretty sure this means the ultravnc_dsm_helper process could not read the /path/to/rc4.key file.

I think you will need to open up the permissions on it (is it owned by root and have perms 600?)

[Kasutajakene]

Thanks for response. Permission denied was indead caused by lack of permissions (I thought that it was caused by server). Well, but the sad story here is that it gives me exacly same thing as when I run ./ultravnc_dsm_helper & ./tightvncviewer

Code: Select all

 Profo: RFB 003.016
Settting RFB version to 3.3 for UltraVNC Single Clcik

Connected to RFB server, using protocol 3.3

And still singleclick.exe tray thinks that nothing has even tried to connect to it. Basically as much as I understand is that:
1) tightvncviewer starts listening to port 30
2) ultravnc_dsm_helper starts listening to port 5500 and then remote to 5530
3) singeclick.exe starts and chooses the port 5500
4) ultravnc_dsm_helper catches to incoming connection and tells to vncviewer
5) vncviewer succesfully connects to udh
udh won´t connect back to singleclick.exe computer...

[krunge]

Well, but the sad story here is that it gives me exacly same thing as when I run ./ultravnc_dsm_helper & ./tightvncviewer

It works fine for me. I am using a sc exe I built a year ago. Are you using some sort of newer/latest version of UltraVNC SC app and/or builder? Would the changes be incompatible with older viewers???

In my next post I give you a complete example.

1) tightvncviewer starts listening to port 30

Not quite, tightvncviewer listens on port 5530.

2) ultravnc_dsm_helper starts listening to port 5500 and then remote to 5530

Yes, once it gets one on 5500 it redirects to the viewer on 5530. This is only after SC connects to it (i.e. after your steps 3 & 4)

3) singeclick.exe starts and chooses the port 5500
4) ultravnc_dsm_helper catches to incoming connection and tells to vncviewer

Yes. udh connects to vncviewer at this point.

5) vncviewer succesfully connects to udh

No, other way around: udh connects to vncviewer. (unless by 'connect' you mean something broader than TCP connection handshake.)

udh won´t connect back to singleclick.exe computer...

No, udh never connects back to SC.

The TCP connect steps look like this:

Code: Select all

ultravnc_sc.exe --> (network...) --> ultravnc_dsm_helper --> vncviewer

Of course, once this is established data flows in both directions.

[krunge]

Here is a complete example. ultravnc_sc.exe was built about a year ago with this 'helpdesk.txt' entry:

Code: Select all

[HOST]
Internet support B -plugin -connect 192.168.100.15:5500 -noregistry
-plugin -connect 192.168.100.15:5500 -noregistry

and the rc4.key in the same directory.

Sorry but it has been a long time since I built one so I don't remember the site I used, etc. Point me to the site you used and your helpdesk.txt settings. EDIT: I used http://www.uvnc.com/addons/singleclick.html and nothing seems to have changed there in the past couple years. Did you use this same site?

192.168.100.15 is the Linux machine that will run SSVNC.

On that Linux machine SSVNC is run:

Options -> Reverse VNC Connection (-LISTEN)

Options -> Advanced -> UltraVNC DSM Encryption Plugin

In that dialog these are set:

Ultra DSM Keyfile: set to identical rc4.key file.

Type of Key: 'UVNC SC'

Click Done.

Click on Listen.

Next, back on Windows that 'Internet Support B' entry is double clicked.

Then on Linux SSVNC ultravnc_dsm_helper is connected to by SC and udh in turn automatically connects to vncviewer. The Windows desktop appears in the SSVNC vncviewer, and everything works as expected.

Here is the complete output that SSVNC prints out so you can look for any differences:

Code: Select all

+ ssvnc_cmd -listen :0 -noraiseonbeep

Using UltraVNC DSM Plugin key for encryption:

  ultravnc_dsm_helper rev:msrc4_sc /home/runge/ultraSC/custom_rc4/rc4.key PORT HOST:PORT


NOTE: Press Ctrl-C to terminate viewer LISTEN mode.

NOTE: The ultravnc_dsm_helper only runs once.  So after the first LISTEN
      ends, you may have to Press Ctrl-C and restart for another connection.

Running:

ultravnc_dsm_helper rev:msrc4_sc /home/runge/ultraSC/custom_rc4/rc4.key 5500 localhost:5530 &

ultravnc_dsm_helper: waiting for connection on port: 5500
vncviewer -noraiseonbeep -encodings copyrect tight zrle zlib hextile -listen 30

vncviewer -listen: Listening on port 5530
vncviewer -listen: Cmdline errors are not reported until a connection comes in.
ultravnc_dsm_helper: got connection: 5

(LISTEN) Reverse VNC connection from IP: 127.0.0.1
                               Hostname: localhost

ultravnc_dsm_helper: encrypt - WARNING: MSRC4 mode and IGNORING random salt
ultravnc_dsm_helper: encrypt - WARNING: and initialization vector!!


vncviewer -listen: Listening on port 5530
vncviewer -listen: Cmdline errors are not reported until a connection comes in.

ultravnc_dsm_helper: only 12 bytes read. Assuming UVNC Single Click server.
ultravnc_dsm_helper: decrypt - WARNING: MSRC4 mode and IGNORING random salt
ultravnc_dsm_helper: decrypt - WARNING: and initialization vector!!

Proto: RFB 003.016

Setting RFB version to 3.3 for UltraVNC Single Click.

Connected to RFB server, using protocol version 3.3
Security-Type: 1 (rfbSecTypeNone)  Latency: 11.41 ms
No VNC authentication needed

Desktop name "WinVNC"

VNC server default format:
  32 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using default colormap which is TrueColor.  Pixel format:
  16 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
geometry: 1024x768+446+204 ycrop: 0
create_image()
Using shared memory (PutImage ycrop=0, Size 1024x768)
created shm image: 1024x768

Unknown encoding 'tight'
tight encoding does not yet work with ultraDSM, skipping it.
Unknown encoding 'zlib'
zlib  encoding does not yet work with ultraDSM, skipping it.
guessed: -compresslevel 2
guessed: -qualitylevel  8
enabling 'delay_sync' mode for faster local drawing,
disable via env SSVNC_DELAY_SYNC=0 if there are painting errors.
ShmCleanup called

VNC Viewer exiting.

SSVNC_LISTEN_ONCE: Trying to kill Listening Parent: 12755
SSVNC_LISTEN_ONCE: Press Ctrl-C if it continues to Listen.

ultravnc_dsm_helper: encrypt - input stream finished: n=0, err=0
ultravnc_dsm_helper: encrypt - close sock_to
ultravnc_dsm_helper: encrypt - close sock_fr
Terminated

Terminating background ultravnc_dsm_helper process
kill -TERM 12752
[1]+  Terminated              $cmd
+ set +xv

Done. You Can X-out or Ctrl-C this Terminal if you like. Use Ctrl-\ to pause.

sleep 5

Quit

[Kasutajakene]

what version of MSRC4Plugin are you using. It´s highly unlikely that the fault is there, but I would like to check every option as I have done everything exacly for like 10 times as you said in the last post. Althought I don´t´get as much of message as you do. Can you please give me links for:
SSVNC
MSRC4Plugin
Thanks in advance

[krunge]

what version of MSRC4Plugin are you using. It´s highly unlikely that the fault is there Can you please give me links for:
SSVNC
MSRC4Plugin

SSVNC: I've used these, but I am pretty sure earlier ones work too:

http://downloads.sourceforge.net/ssvnc/ ... se_mirror=
http://ssvnc.sourceforge.net/dev/ssvnc_ ... .25.tar.gz

For SC I used the builder:

http://www.uvnc.com/pchelpware/sc/creator.html

both 'RC23' and 'REL1.00' flavors work well (and also an older one I built a over year ago.)

I am not sure what version of MSRC4Plugin.dsm is used in the SC creator. Do you know how I can find out? I built the 'RC23' and 'REL1.00' ones just a few days ago to test that SSVNC still works with the lastest ones (it does.)

Outside of SC, I know ssvnc+udh works with MSRC4Plugin v1.2.2 and 1.2.4 from the ultravnc binary distributions. Of course in SSVNC I select 'MSRC4' instead of 'UVNC SC' as the key type.

but I would like to check every option as I have done everything exacly for like 10 times as you said in the last post. Althought I don´t´get as much of message as you do.

Why don't you paste the full output you get? It will be much easier if I look for differences.

If you don't know how to copy and paste the full ssvnc output in its xterm I can tell you how.

[Kasutajakene]

linkforLOG
copy/paste in xterm is pretty bad with mid mouse click etc, you know any better way to do it?
Anyways:
on my sc.exe - the msrc4plugin.dsm is version 1.2.2.0
you can check it, when you go to properties (at least in Windows) and "Version" tab, but I cannot check the one in ssvnc as it integrated to the program as you should know.
Anyway, as you can see our logs are pretty much different, which is weird to be honoust. Any thoughts?

[krunge]

copy/paste in xterm is pretty bad with mid mouse click etc, you know any better way to do it?

1. Click and release Left mouse button at the desired start position.
2. Scoll down (either Middle mouse button drag on scrollbar or use Shift+PgDown)
3. Click and release Right mouse button at the desired end position
4. Text is now selected and copied and ready for pasting into other apps via Middle button press.

[krunge]

Anyways: on my sc.exe - the msrc4plugin.dsm is version 1.2.2.0 you can check it, when you go to properties (at least in Windows) and "Version" tab, but I cannot check the one in ssvnc as it integrated to the program as you should know. Anyway, as you can see our logs are pretty much different, which is weird to be honoust. Any thoughts?

Please tell me the exact recipe you are using for building your sc.exe (links, choices, helpdesk.txt, etc. and everything else you did.)

I am using http://www.uvnc.com/pchelpware/sc/creator.html and am having no problems doing SC -plugin connections to ssvnc.

Also from the SSVNC documentation:

The choice "UVNC SC" enables a special workaround for use with UltraVNC
Single Click and the MSRC4 plugin. It may not be needed on recent SC.

so maybe try ''MSRC4' instead of 'UVNC SC' as the key type.

Even if that works, please send your exact sc.exe recipe since it will be of use to me. Thanks.

[Kasutajakene]

okey, I got it to work with msrc4, but "no VNC authentication needed" means no password needed or?
Is this right log?
Now I´m somekind of confused. Why didn´t work msrc4_sc ? Was there really a mismatch (aka in my exe fail was integrated msrc4 not msrc4_sc?)
I used the same place to create sc.exe
In my helpdesk.txt -

Code: Select all

[HOST]
Internet support B 
-plugin -connect ip.ip.ip.ip:5500 -noregistry

The only importnant line

[krunge]

okey, I got it to work with msrc4.

Good, glad it is working for you now.

but "no VNC authentication needed" means no password needed or?

Yes, viewer is telling you no VNC password was asked for.

Is this right log?

Yes, it looks very good.

Now I´m somekind of confused. Why didn´t work msrc4_sc ? Was there really a mismatch (aka in my exe fail was integrated msrc4 not msrc4_sc?)

Sure. ultravnc_dsm_helper is a complete reimplementation: it doesn't use any of the UltraVNC code. So it needs to work around all of the goofy quirks in UltraVNC (there are many.) Old SC+plugin did one thing new SC+plugin does something else.

I used the same place to create sc.exe
In my helpdesk.txt -

I don't remember seeing that 'UltraVncSC update 2009' when I did it last week. I either missed it or it is new. I assume you used 'UltraVncSC update 2009' because I used http://support1.uvnc.com/cgi-bin/upload4.pl (link found mentioned in a forum) and that seems to be the same thing. When I used this new one I got the same problem you did and saw that it was fixed by using 'MSRC4' insead of 'UVNC SC'.

[Kasutajakene]

so this is my final post right now. Thanks Krunge for all your help. I couldn´t have got it to work without you. I also wish you best of luck for the future (everyone needs luck you know). So thanks again.