Add support for custom keyring names on linux #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've implemented a way to use custom keyring names (on linux).
To let it compile on another OS than linux, every
keyring_<os>.go
file needs to implement thesecretServiceProvider
to allow a typecast in thekeyring.go
. This is required since there must be a way to set the keyringName in thekeyring_linux.go
fromkeyring.go
to pass the desired keyring name.I've successfully cross compiled a test application for every os
A test function for each function from the keyring interface is available as well.
To use it a
customKeyring
object must be created usingkeyring.NewCustomKeyring("name")
.Fixes #46