Conversation

Notices

1. aab (aab@khp.ignorelist.com)'s status on Wednesday, 09-Feb-2022 08:09:31 UTC aab

   • CryptPad
   Hi @cryptpad Recently I've been working on a cryptpad setup on apache (I know, I know...). Decided to get it working over nginx, and finally I've been able to update it (it was 2 versions behind, and I was starting to get nervous). Everything is working fine, and even the checkup page gives 21/21 tests passed.
   What I don't get is why it says I'm using v4.13.0. Does it mean that this version is already published although the release note is not? I'm using "main" branch.
   Anyway, thanks a lot for your work!
   • aab (aab@khp.ignorelist.com)'s status on Wednesday, 09-Feb-2022 10:20:22 UTC aab

     • CryptPad
     I'll keep an eye for the release notes. Thanks a lot! 😊
   • aab (aab@khp.ignorelist.com)'s status on Tuesday, 15-Feb-2022 12:29:34 UTC aab

     • CryptPad
     I've just applied the changes mentioned in https://github.com/xwiki-labs/cryptpad/releases/tag/4.13.0, and... everything seems to be working fine. Thanks for your work! https://khp.ignorelist.com/url/2409357
   • aab (aab@khp.ignorelist.com)'s status on Tuesday, 15-Feb-2022 12:37:20 UTC aab

     • CryptPad
     What do you think of adding something like this at the end of the example.nginx.conf?
     
     location ^~ /.env {
     deny all;
     return 444;
     }
     
     "/.env" is just a example, based on the several times I've seen bots (or malicious people) trying to find something interesting. Setting nginx like that allows to create a "catch-all" filter file for fail2ban.