Logging function #710
Replies: 1 comment 1 reply
-
The Syncplay server doesn't have built-in logging because it's not something we use for our public server which is one of the main use cases we have developed around. The issue of successful/unsuccessful logins isn't really relevant for our public servers because they are not password protected, and instead the room names become the de facto passwords. The regular Syncplay server application notes failed login attempts by printing something along the following lines to the console: Depending on your OS, you might be able to pipe these messages to some sort of log file. This will not tell you about successful login attempts. If you want that then you would need to modify the Syncplay server source code and either build your own version or run from the source code. The password checking function is within protocol.py and is called If you are logging personal information then will probably need to consider the relevant legal requirement of the countries in which you operate. For example if you have logging then you may wish to specify this in your server MOTD (to complement the longstanding warning in the Syncplay client which states: "Do not use Syncplay to send sensitive information."). If you want usage states then you can specify a |
Beta Was this translation helpful? Give feedback.
-
Hello, is there a way to enable a log of successful and unsuccessful login attempts and messages in the server part of the syncplay? I'd like to know what's going on under the hood.
Beta Was this translation helpful? Give feedback.
All reactions