Peter Dobsan
Peter Dobsan
I have significantly refactored `oama` by moving the low level details of dealing with secrets into two external packages. They provide the same high level interface but the internal implementation...
Meanwhile I moved secret management into the Crypto.Manager internal module. There are no external packages any more. `cabal build` or `make build-with-tools` should work in macOS.
Indirectly used the method in the new Crypto.Manager module. Thank you
On Mon, Jul 22, 2024 at 07:02:04PM GMT, githubbbie wrote: > Spent some good time to get oama building on alpine linux with minimal > configuration and have worked thru...
On Sat, Aug 17, 2024 at 09:48:04AM GMT, Liam Hupfer wrote: > > It's weird that it uses secret-tool instead of using the libsecret > > API, which would doubtlessly...
I am relying on github's email service to monitor issues and somehow I have not received email about this issue. I have just discovered it now. Anyway, it looks to...
I have made the credential storage location configurable through the `XDG_STATE_HOME` envvar. For details please see the README. New release coming soon.
On Sat, Mar 22, 2025 at 11:15:50PM -0700, AlexanderTheGrey wrote: > @keithbowes Can you post your `config.yaml`? Instead, both of you, please post the output of the command oama printenv
On Sun, Mar 23, 2025 at 01:46:22AM -0700, AlexanderTheGrey wrote: > client_id: 9e5f94bc-e8a4-4e73-b8be-63364c29d753 > client_secret: '' Where does the `client_id` comes from? That is what kind of `client_id` this is?...
On Sun, Mar 23, 2025 at 07:00:58AM -0700, AlexanderTheGrey wrote: > The `client_id` is from Thunderbird. It's essentially a default value, > since Microsoft does not provide one, and does...