>When using uwsgi, umask can be applied there.
Does that help anything? The init.d script also applies an appropriate
umask. The problem is that Radicale overrides it.
>I don't fell comfortable applying a backport when upstream don't want to
>carry it either, and unfortunately it seems I am
Quoting Forest (2020-08-31 21:03:28)
> Upstream have acknowledged the bug and stated that they no longer want
> to update Radicale 2.x. The bug is fixed in 3.x. Any chance Debian
> will move to the new version soon?
>
> https://github.com/Kozea/Radicale/pull/1096#issuecomment-683684617
Upstream have acknowledged the bug and stated that they no longer want to
update Radicale 2.x. The bug is fixed in 3.x. Any chance Debian will move to
the new version soon?
https://github.com/Kozea/Radicale/pull/1096#issuecomment-683684617
Package: radicale
Version: 2.1.11-6
Severity: normal
Dear Maintainer,
Radicale 2.x ignores its umask when creating .ics and .vcf files.
This interferes with backups, git diffs (when using the git hook), and
anything else that depends on group read permission to access those files.
The problem
4 matches
Mail list logo
