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 693608 - Logging DOS fills ~/.cache/gdm/session.log
Logging DOS fills ~/.cache/gdm/session.log
Status: RESOLVED DUPLICATE of bug 641811
Product: vino
Classification: Applications
Component: Server
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-02-11 18:27 UTC by nathanael
Modified: 2013-09-12 09:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nathanael 2013-02-11 18:27:00 UTC 
I have vino set to require a password. The system is on a publicly accessible machine. One morning I arrived to find / full and vino-server using inordinate amounts of CPU. In trying to find free space I also noticed that soon after freeing space, it would get used up. (Which is when I looked at what processes were running and found vino using too much CPU for not having a client connected).

In the end I found that ~/.cache/gdm/session.log was 669G. A message was repeated "AM Authentication deferred - ignoring client message". 

It was repeating 80 000 per second in the log file.

Thus Vino should introduce some form of rate limiting or other related features to help avoid this situation. It would also be nice if it could detect something like this and add a setting for blacklisting IPs that make more than X requests per second or some such. I realize though that some of that could be done via a firewall so perhaps not on that second part. However rate limiting the logs would be very useful to avoid this situation
Comment 1 David King 2013-09-12 09:34:58 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 641811 ***