[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-25 Thread nitrogen dream
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 viewer.
So adding type 2 in the proposed supported security types will solve this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-25 Thread Plurtu
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 Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-25 Thread Romano Giannetti
@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 sent unencrypted on
the local wire.

Will check SSVNC; but this is similar to what I am doing now, having a
ssh tunnel in the middle.

But again, the problem is in vino, which is offering as encrypted
transport one that nobody uses --- and that force you to go thru hoops
to have an almost safe connection.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-18 Thread Romano Giannetti
@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 clear** on the local network. All
what you type is sent as is.

I have worked around it wrapping the thing in a SSH tunnel, but still,
it's sensible to local attacks and I think it's not a solution for the
average user.

@Sebastian, I am not sure if this is a security thing --- after all,
before the switch, all the connections were silently made without
encryption, but it's scary nevertheless --- sniffing for traffic on port
5900 is easy enough.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-16 Thread Holger Mauermann
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 bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Sebastien Bacher
@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 Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Sebastien Bacher
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 link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Romano Giannetti
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 
distributionand simply paste the URL, but now I have an error (says I can't 
add another bug to the same distribution and in the dsitribution lists there is 
no gnome upstream to choose).  How am I supposed to add the upstream bug? 
 

** Bug watch added: GNOME Bug Tracker #728267
   https://bugzilla.gnome.org/show_bug.cgi?id=728267

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Romano Giannetti
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/ 
saucy/main i386 Packages
100 /var/lib/dpkg/status
 3.6.2-0ubuntu5 0
500 http://archive.ubuntu.com/ubuntu/ saucy/main i386 Packages

Anyone with stock 3.8 version?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Sebastien Bacher
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 authentication types need to be added. There is some
information about the protocol and security types at:

http://sourceforge.net/p/tigervnc/code/HEAD/tree/rfbproto/rfbproto.rst

I will not have time to add the security types in the near future.

** Changed in: vino
 Remote watch: Red Hat Bugzilla #981984 = GNOME Bug Tracker #728267

** Also affects: vino (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=981984
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Bug Watch Updater
** Changed in: vino
   Status: Unknown = Confirmed

** Changed in: vino
   Importance: Unknown = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Romano Giannetti
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 clients. The optimal solution would be to help
vino developers to add a more common encryption type; for the time
being, I will test the suggested viewer and comment.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-15 Thread Romano Giannetti
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 general VNC viewer tool.

So I think that the only option now is

a) having a VNC with almost no  interoperability with Windows

or

b) re-defaulting to no encryption

Really, I do not know which one of the two options is the worst one.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-14 Thread Sebastien Bacher
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 = High

** Also affects: vino (Ubuntu Trusty)
   Importance: High
   Status: Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-14 Thread Launchpad Bug Tracker
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 Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-14 Thread Romano Giannetti
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 support the new one.

The only solution now is disable the encryption completely; I resorted
to a loop back ssh connection so that there is no clear traffic on the
wifi, but I still need to do the local step with vino in clear way ---
almost safe for me because I do not have other local users, but you
never know...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-14 Thread Sebastien Bacher
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 Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-14 Thread Romano Giannetti
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 Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-14 Thread Romano Giannetti
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.

What I *suppose* happened is that the vino server upgraded the
encryption algorithm and the clients have still to catch up; the problem
is that there seems no way to say vino to use an old encryption --- it
just works with the type 18 or none.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-04-14 Thread Sampo Savola
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 only solution
for Mac OSX Screen Sharing to work was to build older Vino-server from
13.10.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1281250] Re: VNC accessible for Windows machines only with encryption disabled

2014-02-18 Thread Sebastien Bacher
** Changed in: vino (Ubuntu)
   Importance: Undecided = Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1281250

Title:
  VNC accessible for Windows machines only with encryption disabled

Status in GNOME Remote Desktop:
  Unknown
Status in “vino” package in Ubuntu:
  New

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp