forked from deskflow/deskflow
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Labels
bugSomething isn't workingSomething isn't workingcriticalFor critical bugsFor critical bugshelp wantedExtra attention is neededExtra attention is neededlinuxRelated to LinuxRelated to Linux
Description
Operating Systems
Server: Ubuntu 19.10
Client: Ubuntu 19.04, Ubuntu 19.04
Barrier Version
2.3.1+dfsg-1
Steps to reproduce bug
- Launch barriers
- Connect to barriers with a client
- Observe for a few minutes that memory usage is not growing substantially
- Launch a second client attempting to connect to barriers with the same name
- Watch memory usage grow substantially (~2MB/minute)
- Disable the second client, and observe that memory usage growth stops
Other info
- Downstream Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/barrier/+bug/1840483
- Is there a way to work around it? Yes, restart barriers
- Does this bug prevent you from using Barrier entirely? No
This is arguably a DOS attack vector from users on my network; if they know the names of my screens (which are just hostnames in my configuration, so not hard to work out), they can exhaust memory on the host running barriers.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingcriticalFor critical bugsFor critical bugshelp wantedExtra attention is neededExtra attention is neededlinuxRelated to LinuxRelated to Linux