zeripath b82293270c Add option to provide signature for a token to verify key ownership (#14054) ... * Add option to provide signed token to verify key ownership Currently we will only allow a key to be matched to a user if it matches an activated email address. This PR provides a different mechanism - if the user provides a signature for automatically generated token (based on the timestamp, user creation time, user ID, username and primary email. * Ensure verified keys can act for all active emails for the user * Add code to mark keys as verified * Slight UI adjustments * Slight UI adjustments 2 * Simplify signature verification slightly * fix postgres test * add api routes * handle swapped primary-keys * Verify the no-reply address for verified keys * Only add email addresses that are activated to keys * Fix committer shortcut properly * Restructure gpg_keys.go * Use common Verification Token code Signed-off-by: Andrew Thornton <art27@cantab.net>		2021-07-13 15:28:07 +02:00
..
admin_user.go
attachment.go
commit_status.go
cron.go
doc.go
fork.go
git_blob.go
git_hook.go
hook.go
issue.go
issue_comment.go
issue_label.go
issue_milestone.go
issue_reaction.go
issue_stopwatch.go
issue_tracked_time.go
lfs_lock.go
miscellaneous.go
notifications.go
org.go
org_member.go
org_team.go
org_type.go
pull.go
pull_review.go
release.go
repo.go
repo_branch.go
repo_collaborator.go
repo_commit.go
repo_file.go
repo_key.go
repo_refs.go
repo_tag.go
repo_topic.go
repo_tree.go
repo_watch.go
settings.go
status.go
task.go
user.go
user_app.go
user_email.go
user_gpgkey.go
user_key.go