ahh, I was looking in stracker 3.4.1 which had no docs. ![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
The normal user pages functions normal.500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Traceback (most recent call last):
File "site-packages\cherrypy\_cperror.py", line 422, in handle
File "site-packages\cherrypy\lib\auth_digest.py", line 358, in digest_auth
File "site-packages\cherrypy\lib\auth_digest.py", line 184, in __init__
ValueError: Digest Authorization header: Not all required parameters are present.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "stracker_lib\http_server.py", line 81, in my_auth_digest
File "site-packages\cherrypy\lib\auth_digest.py", line 358, in digest_auth
File "contextlib.py", line 66, in __exit__
File "site-packages\cherrypy\_cperror.py", line 424, in handle
cherrypy._cperror.HTTPError: (400, 'The Authorization header could not be parsed.')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "site-packages\cherrypy\_cprequest.py", line 667, in respond
File "site-packages\cherrypy\_cprequest.py", line 114, in run
File "site-packages\cherrypy\_cprequest.py", line 104, in run
File "site-packages\cherrypy\_cprequest.py", line 63, in __call__
File "stracker_lib\http_server.py", line 83, in my_auth_digest
File "site-packages\cherrypy\lib\httputil.py", line 371, in __getitem__
KeyError: 'Www-Authenticate'
Powered by CherryPy unknown
Do you mean the Lap Times page? What changes are you trying to make? You need to edit the stracker ini file in your stracker folder on your server.
did you restart stracker after applying the changes?hi guys, sorry if that was discussed before. I would like to apply changes on "lapstat" page. I was hopping all I need is to modify "tmpl_laptymes.py" file. I did modify, but changes are not applying. We are hosting AC on rackservice org. So I see to reasons: 1)modifying tmpl_laptymes.py is not right place or 2)stracker on rackservice org is not getting my updates. Thanks for any help!
it is hosted on rackservice org. So we don't have an access to the app in console, everything is wrapped by web interface to AC and pluggins folders. Below is screenshot. Might be 2 problems 1) it is not restarted when I'm doing service restart from the rackservice web admin 2)rackservice ignores my changes in http_templatesdid you restart stracker after applying the changes?
do you get any suspicous notifications in stracker.log?
maybe it's an issue with browser cache?
but my direction is correct, right? I mean modifying tmpl_laptymes.py is enough?Hmm I fear I'm not going to be of any more help here...
Hi,
the one or the other might have heard about the new EU privacy policy (GDPR). We already have had some discussions here: https://www.assettocorsa.net/forum/...olicy-a-show-stopper-for-tracking-apps.49496/. I believe that this is or at least might be a problem for stracker. There is a lot of uncertainty out there, and I am not willing to be a "beta tester" of this new law for the sake of a computer game.
I hope you understand that I take no responsibility for data processing on 3rd party servers, even if the data processing is performed by a software which was mostly written by me. You as server admins are fully responsible for the software running on your servers and you have to judge for yourself if this is or is not a legal issue in your specific usecase.
Nevertheless, I have made some changes to stracker, so that
1. stracker does not store plain steam GUID's anymore in the database. I don't know whether steam ID's are personal data, nor do I know whether the sha256 hashes of steam ID's are personal data. There might be more personal data stored in the stracker database. Judge for yourself please.
2. users can anonymize their data by using the new chat command "/st anonymize on". This deletes also their chat messages from the database. I don't know if this is enough to provide users the right to delete their personal data or not. You have to judge that for yourself.
3. admin can choose to block those users from entering the server via stracker auth
Informing the user is under responsibility of the server admins.
I'm not saying that running stracker 3.5.0 is enough to comply to the GDPR. I'm not even saying that the changes made in 3.5.0 have the purpose to comply to GDPR.
This is the full change log for stracker 3.5.0. The version is available on n-e-y-s.de for download, it is labeled as experimental for the time being. Note that I am going to shut down my web services before GDPR is enforced starting at May 25th, leaving you with the race department downloads afterwards.
core:
http:
- add config option HTTP_CONFIG/auth_ban_anonymized_players (default: False)
- remove options HTTP_CONFIG/enable_paypal_link and BLACKLIST/blacklist_file
- upgrade database to version 24, convert steam ID's to sha256 hashes
- anonymize steam ID's saved in the server database by sha256 hashes
- provide a user command to anonymize his personal data. Results in deletion of his chat messages, and his name will be replaced with an anonymous name, which is not updated anymore until the user chooses to exit this mode. Admins can choose to automatically block those players
- Updates in README.txt, mention the EU GDPR dilemma and make sure that the server admin takes responsibility
Regards
- fix sort order of drivers in drrivers page for postgres databases
- changes in some of the http templates
Neys