Hi, In my config I have
[auth] type = htpasswd htpasswd_filename = ~/.config/radicale/users I just followed recommendations on the radicale web page for this. I think that personal config file overrides the system-wide one, so there isn't really any need to worry about this. The logging issue is really an upstream bug : correct behaviour would be to check whether the user asked for different logging options, before setting up the system-wide logging. But really, I think you should create a special (system) user « radicale » for a system-wide service. No need for root to serve an addressbook, even if it is the system addressbook, no ? Unless you want to modify it, but do you really want to use radicale for changing the users on a system ? Then then you can give it write access to /var/log/radicale, and give it its own user config files, leaving /etc/radicale for only truly common options. You probably also want to make it a package configuration question if this service should be enabled no ? Or just leave it disabled by default, after all it will not work out of the box anyway I think... ? OK, these are just some thoughts. But really, unless there is a very good reason to run radicale as root, not doing so is a Good Idea(TM). Cheers, Itaï ----- Mail original ----- De: "Jonas Smedegaard" <[email protected]> À: [email protected], "Itai BEN YAACOV" <[email protected]> Envoyé: Mercredi 4 Mars 2020 13:57:52 Objet: Re: Bug#952870: radicale: Since 2.1.11-8 radicale cannot be started by non-root [ sent again, with 7bit headers to please Debian MTAs ] Hi Itaï, Quoting Itaï BEN YAACOV (2020-03-01 13:23:05) > Changes to the logging configuration in 2.1.11-8 make it impossible to > start by an ordinary user, who cannot write to /var/log/radicale (and > probably does not want to, either). Indeed, I forgot about that when tuning the config. ...but now, looking into how to redo that tuning while preserving the use case of running as a single user, it seems to me that I made other mistakes as well: How do you handle authentication when running as single-user? It seems to me that you would need to change from "remote_user" to some other scheme, right? Is there other tunings that would make for a more ideal default setup when running as single-user? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
