When the viewer specifies using a dsmplugin, if connecting to a server not using encryption, the viewer should pop up a warning window of "Accept insecure connection". However, this feature is broken on 1.0.9.5 and 1.0.9.6, the connection is established without this warning. Even worse, when checking the viewer's Connection Info, it reported the configured dsmplugin was being used.
Both normal and reverse connection have this problem.
Have verified with 1.0.8.2 viewer, no such bug.
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
VNCviewer Bug -- No Warning when connecting to a Non-encrypt
Re: VNCviewer Bug -- No Warning when connecting to a Non-enc
bug confirmed
uvnc 1.0.9.6 release vncviewer date 4.4.2011 and winvnc 1.4.2011
vnc viewer status HOSTNAME
Status: Connected (SecureVNCPlugin-v2.3.0.0)
In progress (no encryption)
viewer use encryption plugin but not server
options.vnc
UseDSMPlugin=1
DSMPlugin=SecureVNCPlugin.dsm
AutoAcceptIncoming=0
AutoAcceptNoDSM=0
RequireEncryption=0
uvnc 1.0.9.6 release vncviewer date 4.4.2011 and winvnc 1.4.2011
vnc viewer status HOSTNAME
Status: Connected (SecureVNCPlugin-v2.3.0.0)
In progress (no encryption)
viewer use encryption plugin but not server
options.vnc
UseDSMPlugin=1
DSMPlugin=SecureVNCPlugin.dsm
AutoAcceptIncoming=0
AutoAcceptNoDSM=0
RequireEncryption=0
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: VNCviewer Bug -- No Warning when connecting to a Non-enc
vncviewer 10961 (15 April)
winvnc 10961 (16 April)
short test
winvnc NO plugin
vncviewer with securevncplugin.dsm
vncviewer
ok direct connection, message and prompt pwd + conexion OK
ok via repeater ID message and connection OK
not tested from comand line, tested only from vncviewer GUI
(no encryption)
winvnc 10961 (16 April)
short test
winvnc NO plugin
vncviewer with securevncplugin.dsm
vncviewer
ok direct connection, message and prompt pwd + conexion OK
ok via repeater ID message and connection OK
not tested from comand line, tested only from vncviewer GUI
(no encryption)
Last edited by redge on 2011-04-18 18:51, edited 1 time in total.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: VNCviewer Bug -- No Warning when connecting to a Non-enc
Still a minor defect.
The viewer's Connection Info still showing a plugin is used, in fact not.
The viewer's Connection Info still showing a plugin is used, in fact not.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: VNCviewer Bug -- No Warning when connecting to a Non-enc
Technical, plugin is used even without encryption.
Message
Status: Connected (SecureVNCPlugin-v2.3.0.0)
In progress (no encryption)
Older plugins get unloaded,
SecureVNCPlugin-v2.3.0.0 stay loaded, even when not used.
This change in behaviour caused the initial error.
Message
Status: Connected (SecureVNCPlugin-v2.3.0.0)
In progress (no encryption)
Older plugins get unloaded,
SecureVNCPlugin-v2.3.0.0 stay loaded, even when not used.
This change in behaviour caused the initial error.