Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demonstrate usage of macOS keychain to store passwords #70

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ktf
Copy link

@ktf ktf commented Jan 15, 2025

In case you are interested, this is what I use to store the password in the macos keychain. While it should not be complicated, my haskell-fu is not large enough to support both linux and macOS in the same sourcecode.

Copy link
Owner

@pdobsan pdobsan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the information. Might use it later.

@pdobsan
Copy link
Owner

pdobsan commented Mar 11, 2025

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 is different. I incorporated
your solution of using the security utility in macOS to deal with keyring into
one of these external packages (secret-tools).

You can build oama in macOS using this method by issuing:

make build-with-tools

For more details see the Readme. The corresponding external package used in this
case is https://github.com/pdobsan/secret-tools

Would you mind to test the new oama in your macOS environment?

@pdobsan
Copy link
Owner

pdobsan commented Mar 13, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants