After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 162465 - Vino does not have a logging mechanism
Vino does not have a logging mechanism
Status: RESOLVED WONTFIX
Product: vino
Classification: Applications
Component: Server
unspecified
Other All
: Normal enhancement
: 3.2
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2004-12-29 13:46 UTC by Petter Sundlöf
Modified: 2020-11-12 12:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Petter Sundlöf 2004-12-29 13:46:08 UTC
Where does Vino/VNC store its log file?

RealVNC/regular VNC uses ~/.vnc. There ought to be a .log in ~/.vnc when a
session is started.

Currently I have Vino enabled for my desktop (:0). I can connect and I input a
password, but no window appears on the client side. I cannot debug this --
because there is no log file.
Comment 1 Pavel Šefránek 2008-02-25 19:01:11 UTC
Petter, can you review it again please? I do not use vino.
Comment 2 Jonh Wendell 2008-02-25 19:08:55 UTC
Pavel, why are you touching vino bugs when you don't even use it?
Comment 3 Pavel Šefránek 2008-02-25 19:37:35 UTC
Because it's pretty old and it was still without a response. I am just trying to help you.
Comment 4 Paul Eipper 2010-08-18 18:46:41 UTC
Any chance of seeing this fixed?
Comment 5 Paul Eipper 2010-08-25 16:27:39 UTC
Please refer to launchpad bug #330310 ( https://bugs.launchpad.net/ubuntu/+source/vino/+bug/330310 ) for other requests for this.
Comment 6 David King 2011-03-04 17:04:43 UTC
There is currently no logging facility in Vino, so retitling this bug. However, it would seem like a useful feature. I will look at this for 3.2.
Comment 7 Paul Eipper 2012-04-19 12:57:48 UTC
I suggest you bump the importance of this bug. Logging is a critical security issue, since having Vino enabled is a possible door for intrusion attacks and without logs there is no way to detect them after fact.
Comment 8 Bernd Wechner 2016-11-17 02:42:28 UTC
(In reply to Paul Eipper from comment #7)
> I suggest you bump the importance of this bug. Logging is a critical
> security issue, since having Vino enabled is a possible door for intrusion
> attacks and without logs there is no way to detect them after fact.

I will second this. I see it as a security critical issue that Vino have a clear logging option where it logs all connections and the source of the connection (IP and whatever other information), and in the ideal also support keystroke logging for security reasons if nought else. 

Moreover I would like to see a way to list clearly current connections and from which IP.

As the default server on MINT I admit I find lack of such security features puzzling and concerning.
Comment 9 Hashem Nasarat 2018-02-25 17:04:28 UTC
I recently discovered where to find vino logs:

journalctl --user -u vino-server
Comment 10 André Klapper 2020-11-12 12:24:49 UTC
Vino is not under active development anymore and unmaintained.

Please use gnome-remote-desktop instead.

Closing this report as WONTFIX to reflect reality.