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

Authentication #5

wants to merge 25 commits into
base: 8.x-1.x


None yet
2 participants

fantastic91 commented Jun 12, 2016

No description provided.

$gpg = gnupg_init();
// @todo: Delete the old key from GPG keyring.
// gnupg_deletekey($gpg, $original->get('mailhandler_gpg_key')->fingerprint);

This comment has been minimized.


primsi Jun 14, 2016

Does GPG maintain it's own keyring? How it is used? How does it differentiate between users?

This comment has been minimized.


fantastic91 Jun 14, 2016


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.


This comment has been minimized.


fantastic91 commented Jun 16, 2016

Commits were cherry-picked and merged into the 8.x-1.x branch.

@fantastic91 fantastic91 deleted the features/authentication branch Jun 16, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment