ActivityWatch / ActivityWatch/activitywatch

ActivityWatch doesn't behave well on multiuser systems

Offen
#75 16 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
!pinned improves: security priority: low type: bug
Vorherrschende Sprache
Python
Sterne
18.9k
Forks
1k
Ø Merge
1 T. 4 Std.
Gemergte PRs (30 T.)
28

Beschreibung

Tried starting two instances of ActivityWatch today on the same computer (different users, Windows).

I was surprised to see the other users data when I opened localhost:5600, then I realized that it's not that strange since they use the same port.

What did surprise me was that I got no error about the server being unable to bind the port. I guess things work differently in the Windows world.

So this has a few issues:

- Users could read the data from other users running ActivityWatch.
- Two users cannot run ActivityWatch **on the same port** (well, they can, but only the person first starting the server will store all the data since the second server will crash on start when it can't bind the port)

This issue is present with other software as well, such as Syncthing. **The basic workaround seems to be to just add the ability to run it on different ports.** But this has some privacy issues if we don't also add the ability to password-protect the server.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/46340818-activitywatch-doesn-t-behave-well-on-multiuser-systems?utm_campaign=plugin&utm_content=tracker%2F35920020&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F35920020&utm_medium=issues&utm_source=github).

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.