@nitrogen dream: reading here:
https://sourceforge.net/p/tigervnc/code/HEAD/tree/rfbproto/rfbproto.rst
#vnc-authentication, with type 2 the only thing that is encrypted is the
VNC password, which is, honestly, my least worry. All the keystrokes in
the session (including your bank password) is then
Enhanced TightVNC Viewer (SSVNC) works with vino's ANONTLS encryption on
Windows.
http://www.karlrunge.com/x11vnc/ssvnc.html
Don't expect to connect in a hurry though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Guys,
The problem is simple.
If you take a Wireshark trace you immediately see the issue.
You will have to filter on VNC.
The supported security type which is given for 14.04 is "type 18, TLS".
For 13.10 we see two types, "type 18, TLS" and "type 2, VNC".
The "type 2, VNC" is used by your VNC vie
@Holger: yes --- I just noticed it too.
I humbly suggest that Canonical or Redhat help the vino developers to
add a more common encryption type to the vino server. It is the default
(and the facto only) remote vnc server in our system, and in its current
state forces everyone to connect **in clea
This doesn't affect only Windows, but Android too. I tried two different
apps ("VNC Viewer" from RealVNC Limited and "Jump Desktop" from Phase
Five Systems), but since upgrading my Ubuntu Desktop to Trusty both fail
with error messages related to incompatible security types.
--
You received this
Well, downloaded it (virt-viewer, I mean). Tried to connect to a remote
machine but no dice --- it just show a window, asking for a connection
URI, I tried 200 combinations... No documentation handy available
either. Seems to be thought just for managing virtual machines, so it
doesn't seem a gener
Upstream comment:
"I think that the TLS security type (18) is rather uncommon, but gtk-vnc
supports it. I think that virt-viewer uses gtk-vnc and should work:
http://virt-manager.org/download/
"
so basically the problem is that vino is using an encryption type which
is supported only by few clie
** Changed in: vino
Status: Unknown => Confirmed
** Changed in: vino
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281250
Title:
VNC accessible for Windows
Upstream comment
"I guess that the problem occurs after the default was changed to
require encryption:
https://git.gnome.org/browse/vino/commit/?id=f37ca213fda500ea2f93d005e945644c2f2e5721
For whatever reason, that fails with some clients. If you want Vino to work
with those clients new authenti
Can please people with the problem state their version? Mine is
[:~] 127 % apt-cache policy vino
vino:
Installed: 3.10.0-0ubuntu1~saucy1
Candidate: 3.10.0-0ubuntu1~saucy1
Version table:
*** 3.10.0-0ubuntu1~saucy1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/
sa
Ok, I have reported it upstream at
https://bugzilla.gnome.org/show_bug.cgi?id=728267
--- but I am unable to add it to the bug. I used to choose älso affect
distribution"and simply paste the URL, but now I have an error (says I can't
add another bug to the same distribution and in the dsitribut
The issue you are reporting is an upstream one and it would be nice if
somebody having it could send the bug to the developers of the software
by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the lin
@Sampo: ok, unduplicated, please send upstream, we don't have macOS
systems to test your specific issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281250
Title:
VNC accessible for Windows machin
Rmano, I dont think this is a duplicate:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1307084
If you read my bug raport...I disabled the encryption with dconf trick
but still it didnt work from Mac OSX Screen Sharing application. Dconf
trick makes other vnc clients work such as TightVNC but
Sebastian: no. the default is to use encryption. But after updating vino
(do not remember at which point), vino changed the security type to a
new one (at least, I think); the connection stopped to work with the
error reported above and the only solution to have it back was to
disable encryption.
I reported the thing to TigerVNC bug tracker too:
https://sourceforge.net/p/tigervnc/bug-tracker/148/ let's see if a
solution can be found...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281250
Titl
Did the security level change or was the old default to accept unsecure
login (which seems a buggy default)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281250
Title:
VNC accessible for Windows m
I agree that the best possible solution would be for the Windows clients
(at least TigerVNC and TightVNC) to catch up. Unfortunately this has not
happened; for the time being it would be much better if vino could offer
the option to go back to the previous Security Type when the client does
not sup
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vino (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281250
Title:
VNC a
Thank you for your bug report. Not sure if that's a bug or just
increased security config by default. It might mean that you should fix
your client to use a secure correction...
** Changed in: vino (Ubuntu)
Status: Confirmed => Triaged
** Changed in: vino (Ubuntu)
Importance: Low => Hig
** Changed in: vino (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281250
Title:
VNC accessible for Windows machines only with encryption disabled
To manage
21 matches
Mail list logo