WPIntell

Source evidence

Password safety

WP-CalDav2ICS · support · 2023-03-26T10:58:00+00:00

mixedsentiment
highseverity
0.95relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 36 rows with source links

19.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
paulzuurbier resolved
I have a question about how the passwords are stored. When I used a previous version of WP mail SMTP (years go) my password was hacked within days. It used a plain field to enter the password, just like your plugin. They tackled the problem and the password is now set by changing the wp-config.php file. No hacking problems since then. How do you secure the passwords? It is important because the calendar credentials are the same as my server credentials. Hi Paul, you are right in that the Password for the CalDav Server is stored inside the WP Database as plain Text, although the latest Version uses a password type input Field, which prevents at least to be seen by someone looking over your shoulder 🙂 The Problem is: it cannot be stored as an e.g. md5 hash, because it is not used inside WP (which would allow that) but must be sent to the CalDav Server (usually via https, which is secure) as plain Text. So, I guess, there is no way to improve this. so, well, I once again had a look at WP smtp Plugin, and yes, that has the Option to store Credentials as Constants in the wp-config.php File. The problems with wp-caldav2ics w.r. to do the same are: as there can be multiple servers/accounts, the credentials are not simple Constants, but arrays someone would have to implement this (if possible) and that one will not be me 🙂 – see also https://hoernerfranzracing.de/werner/blog/2023-wp-caldav2ics-reloaded so, I’m closing this now as WONT’FIX Thank you for looking into this. Maybe I will create a seperate account with only calendar permission and then share the calendars of interest with this restricted account read only. yes, I think that is a viable Option – read only access is all what the Plugin needs.

Comments

4 shown
hoernerfranz 2023-03-27T11:40:00+00:00

Hi Paul, you are right in that the Password for the CalDav Server is stored inside the WP Database as plain Text, although the latest Version uses a password type input Field, which prevents at least to be seen by someone looking over your shoulder 🙂 The Problem is: it cannot be stored as an e.g. md5 hash, because it is not used inside WP (which would allow that) but must be sent to the CalDav Server (usually via https, which is secure) as plain Text. So, I guess, there is no way to improve this.

hoernerfranz 2023-03-28T16:45:00+00:00

so, well, I once again had a look at WP smtp Plugin, and yes, that has the Option to store Credentials as Constants in the wp-config.php File. The problems with wp-caldav2ics w.r. to do the same are: as there can be multiple servers/accounts, the credentials are not simple Constants, but arrays someone would have to implement this (if possible) and that one will not be me 🙂 – see also https://hoernerfranzracing.de/werner/blog/2023-wp-caldav2ics-reloaded so, I’m closing this now as WONT’FIX

paulzuurbier 2023-03-28T16:54:00+00:00

Thank you for looking into this. Maybe I will create a seperate account with only calendar permission and then share the calendars of interest with this restricted account read only.

hoernerfranz 2023-03-28T17:00:00+00:00

yes, I think that is a viable Option – read only access is all what the Plugin needs.