Reverse connection & hashed passwords

[jamesthejust]

Great piece of software! Thanks for all the hard work.

Situation:

Server using reverse connection with DSM plugin enabled, no rc4.key provided. Automatically hashes regular VNC password into a key. <-- THIS WORKS

Viewer in listen mode with DSM plugin & no rc4.key. Viewer doesn't support '-password xyz' command in listen mode, doesn't hash password into a key and therefore doesn't connect. <-- THIS DOESN'T WORK

How do I make this work?

I'm automating VNC & want the users at each end (server & viewer) to enter the same (simple) password (which can change each session). This password is then hashed into an encryption key.

Help much appreciated!

[Rudi De Vos]

In reverse connection mode, dsm on viewer site ask passwd via popup.

[jamesthejust]

In reverse connection mode, dsm on viewer site ask passwd via popup.

Ah, thanks. That does the job.

Perhaps you can help me with another query?

When I generate a password using UltraVNC's 'Edit Settings' program the hex string is 18 characters long. vncpwd, on the other hand, generates a 16-character key from the same password.

Any idea why?

Thanks.

Edit: Nevermind. After a bit of searching I've found that the last 2 characters need to be there, but are ignored. In other words, simple appending '00' to the end of the 16-character hex key does the job.

Just to confirm...

Having rc4 keys generated by passwords is secure. The raw passwords don't get transmitted over the internet. Both server & viewer independently convert their own password into an rc4 key & it's those that must match up.

Is that correct? Ta.

[redge]

> Is that correct?
yes