BSD Portsmail/oama 0.18 DragonFly
OAuth credential Manager
- System
- DragonFly
- Repository
- DPorts
- Maintainer
- [email protected] (as in FreeBSD)
- License
- BSD3CLAUSE
- Categories
- Package size
- 6608.4 KiB, 46081.5 KiB installed
Description
Many IMAP/SMTP clients, like msmtp, fdm, isync, neomutt or mutt can use OAuth2 access tokens but lack the ability to renew and/or authorize OAuth2 credentials. The purpose of oama is to provide these missing capabilities by acting as a kind of smart password manager. In particular, access token renewal happens automatically in the background transparent to the user.
The OAuth2 credentials are kept in a keyring provided by any password manager with a FreeDesktop.org Secret Service compatible API. Some examples of such password managers are:
Gnome keyring
KDE Wallet Manager
KeePaasXC
Alternatively GNU PG encrypted files can also be used as a backend for storing credentials.
In the other systems
| System | Port | Version |
|---|---|---|
| DragonFly | mail/oama | 0.18 |
| FreeBSD | mail/oama | 0.21.0 |
| HardenedBSD | mail/oama | 0.21.0 |
| GhostBSD | mail/oama | 0.21.0 |
Install
Binary package:
pkg install oamaFrom DPorts:
cd /usr/dports/mail/oama && make install cleanDependencies
Run dependencies 7
No port depends on this one.
Configuration
No options to configure.
- Service scripts
- none
Message after installing
When the GPG backend is used the encrypted credentials now are stored in the $XDG_STATE_HOME/oama directory. If the XDG_STATE_HOME environment variable is not set then it defaults to $HOME/.local/state. That is a breaking change! If you use the GPG backend you need to manually move your credential ~/.local/var/oama/*.oama files into the new directory.