Thank you for taking the time to report this bug and helping to make
Ubuntu better. 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
Thank you for bringing this bug to our attention. However, a paper cut
should be a small usability issue, in the default Ubuntu install, that
affects many people and is quick and easy to fix. So this bug can't be
addressed as part of this project.
- Though this is a security flaw , we do not
Confirmed, a remote user connecting to vino actually controls the
physical computer's screen.
** Changed in: vino (Ubuntu)
Status: New = Confirmed
** Changed in: vino (Ubuntu)
Importance: Undecided = Wishlist
--
local screen unlocked by remote connection via VNC
I am actually speaking about vino the vnc server (yes, it speaks vnc
protocol) that comes with KK as default.Do you think the average user has the
skills to install his own alternate vnc server? Think about the average Windows
user...
IMHO the average user should have the same functionalities
** Package changed: ubuntu = vino (Ubuntu)
--
local screen unlocked by remote connection via VNC
https://bugs.launchpad.net/bugs/484476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi, actually I did not start the vnc server from commandline, I started it as a
normal user would do, from System - Preferences - Remote desktop.
The way this utility (vino) behaves expose the average user accustomed to
Microsoft's remote desktop to a serious security breach.
I wasn't able to
There's no weird way for vnc server in KK. You just have to install it :
sudo apt-get install vnc4server
or
sudo apt-get install tightvncserver
at your option.
There won't be a vnc service: each user can run as many vncserver he
needs.
--
local screen unlocked by remote connection via VNC
In fact, it depends on the way you launched you vnc server.
When I launch a new vnc server (command vncserver), it starts a new X server
with a virtual screen. This is really secure, because there are no physical
screen attached to it, so a bad guy in front of the workstation can't access
it.
I think you're using x11vnc to access your real X server. There's an answer
about this in its FAQ:
http://www.karlrunge.com/x11vnc/faq.html#faq-blockdpy
--
local screen unlocked by remote connection via VNC
https://bugs.launchpad.net/bugs/484476
You received this bug notification because you
** Also affects: ubuntu
Importance: Undecided
Status: New
--
local screen unlocked by remote connection via VNC
https://bugs.launchpad.net/bugs/484476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
10 matches
Mail list logo
