summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Smith <luke@lukesmith.xyz>2022-05-25 13:21:25 +0000
committerGitHub <noreply@github.com>2022-05-25 13:21:25 +0000
commit81fac506d3518178a785a32e8bbec0f7425981ee (patch)
treeceb29fe13432ca6a54c91428ab95c638bbdfff87
parent3d2a4e1baafd4ac1b1c3106d06187bf86da4532c (diff)
parent14094ed87cb2490c28eaf28937208987fa978296 (diff)
Merge pull request #183 from marhu98/radicale-correction
Usind md5 is insecure. Bcrypt is better
-rw-r--r--radicale.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/radicale.html b/radicale.html
index 029de7c..85bbf14 100644
--- a/radicale.html
+++ b/radicale.html
@@ -26,14 +26,14 @@ hosts = 0.0.0.0:5232, [::]:5232
[auth]
type = htpasswd
htpasswd_filename = /etc/radicale/users
-htpasswd_encryption = md5
+htpasswd_encryption = bcrypt
[storage]
filesystem_folder = /var/lib/radicale/collections</code></pre>
<p>As you can see under [auth] we use htpasswd to manage the users. Execute the following command to add a new user to Radicale.</p>
<pre><code>htpasswd -c /etc/radicale/users <strong>username</strong></code></pre>
- <p>As Radicale stands now it is fully functional and after starting it by executing its binary, can be accessed under example.org:5232. But there are two additional things we can do to make using and managing Radicale way easier.</p>
+ <p>As Radicale stands now it is fully functional and after starting it by executing its binary, can be accessed under example.org:5232. But there are two additional things we can do to make using and managing Radicale way easier.</p>
<h3>Setting up a Nginx reverse proxy</h3>
<p>Because the URL of your Radicale server is an URL you will have to remember and enter it on any device you want to use your calendar on it is advised to set up a reverse proxy.</p>
<pre><code>server {