9/6/2023 0 Comments Calibre server addresses![]() ![]() Please do not use your distribution provided calibre package, as those are often buggy/outdated. Either way, Canonical has not patched 4.99 to work with 20.04 yet in the official repositories. To make 4.99 work you would have to patch a file yourself as shown in the bug or you could download it from a different repository. However, I would be happy to have some more people testing it and providing feedback and recommendations.Unfortunately, at this moment the version of Calibre that is in the 20.04 repos is version 4.99 which does not work with Python 3. During initial testing, the filter did a good job in recognizing failed login attempts and did not get triggered by genuine user activity. The failregex in nf in this project uses a specific 401 167 http error in the calibre access log that pops up in case of failed login attempts. While the calibre-server does log failed login attempts, the original IP address is not perserved in proxy mode. Final remarksĬalibre-server also provides built in brute-force protection, however, I found this to be unreliable. Add calibre jail to /etc/fail2ban/jail.local - see jail.local for an example configuration with the calibre-server access log in /var/log/calibre/access.log. ![]() Fail2BanĬopy nf to /etc/fail2ban/filter.d. SSL/https is optional, make sure you add the certificate and key to the virtual host as well as the calibre-server-backend (calibre user needs read permission to cert files). You need to enable access logging for calibre-server to log ip addresses. Tested on Ubuntu Server 18.04.4 LTS, serving calibre-server over an apache2 virtual host using proxy. This will create a fail2ban filter and jail for failed login attemts for a calibre-server installation running on port 8180, with authentication enabled, to be served over a virtual host with proxy, for example.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |