1
0
Fork
You've already forked radicale-bsdauth
0
OpenBSD's authenticate(3) for https://radicale.org/
  • Python 100%
Nick 6f5304b814
All checks were successful
Publish Package / Publish Package (release) Successful in 2m22s
Update for plugin API change.
I'm not sure exactly when this broke, sorry,
but I know it's broken with radicale>=3.5.
2026年04月17日 17:00:56 -04:00
.forgejo/workflows Move CI to Codeberg. 2026年04月17日 17:00:56 -04:00
src/radicale_bsdauth Update for plugin API change. 2026年04月17日 17:00:56 -04:00
.gitignore Packaging 2022年04月20日 03:38:09 +02:00
CONTRIBUTING.md Move CI to Codeberg. 2026年04月17日 17:00:56 -04:00
pyproject.toml Move CI to Codeberg. 2026年04月17日 17:00:56 -04:00
README.md Move CI to Codeberg. 2026年04月17日 17:00:56 -04:00

OpenBSD Authentication plugin for Radicale

This connects a radicale install to the local OpenBSD's authenticate(3) system that it is installed on. It means you can access your calendars with the same password you use for ssh and, perhaps, email, chat, etc.

Installation

This has only been tested against radicale>=3, which is not yet packaged for OpenBSD, so you must install that version manually (below) if it's not already.

Then install the plugin:

doas uv tool install 'radicale>=3' --with radicale-bsdauth

In order to function, you also need to grant radicale access to authenticate(3):

usermod -G auth _radicale

And then tell radicale to use it by editing /etc/radicale/config or /var/lib/radicale/.config/radicale/config to add

[auth]
type = radicale_bsdauth

And restart:

doas rcctl restart radicale

Install Radicale 3 on OpenBSD

(these have been tested for OpenBSD 7.7, but may need adjusting for a different version)

If you are currently using version 2, you should backup your calendars before proceeding because upgrading risks breaking something. It's unlikely, but possible.

doas -u _radicale tar -jcvf - /var/lib/radicale/collections | (umask 027; cat > radicale-collections.tgz) # for example

Then install radicale 3:

doas pkg_add uv
doas UV_TOOL_DIR=/usr/local/lib UV_TOOL_BIN_DIR=/usr/local/bin uv tool install "radicale>=3"
# Set up radicale's environment
# ( these rest of these steps would normally be handled by pkg_add(1) )
doas useradd -d /var/lib/radicale -m -L daemon -r 1..999 _radicale # if you don't already have this user

You need to put this in /etc/rc.d/radicale:

daemon="/usr/local/bin/radicale"
daemon_user="_radicale"
. /etc/rc.d/rc.subr
pexp=".*/python(3)? ${daemon}${daemon_flags:+ ${daemon_flags}}"
rc_reload=NO
rc_bg=YES
rc_cmd 1ドル

and

doas chmod +x /etc/rc.d/radicale

Finally turn it on:

doas rcctl enable radicale
doas rcctl start radicale

You can monitor it with:

tail -f /var/log/daemon | grep radicale
  • radicale-auth-PAM:

    OpenBSD's authenticate(3) is like Linux's PAM(8): a way to enable multiple ways to prove your identity, from passwords to LDAP to YubiKeys.

    So radicale-auth-PAM provides the same basic feature to radicale as radicale-bsdauth, and if you're using Linux you should use it.