Authentication #5
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $gpg = gnupg_init(); | ||
|
|
||
| // @todo: Delete the old key from GPG keyring. | ||
| // gnupg_deletekey($gpg, $original->get('mailhandler_gpg_key')->fingerprint); |
There was a problem hiding this comment.
Does GPG maintain it's own keyring? How it is used? How does it differentiate between users?
There was a problem hiding this comment.
It uses the system's keyring. Each imported public key gets a Key ID. In case a signature is verified, the user's fingerprint (with its data) is returned. By looking at the key info for the returned fingerprint we can get more information like name, email etc.
|
Commits were cherry-picked and merged into the 8.x-1.x branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.