Diffusion GnuPG 66eb953f4380

gpg: The first key should be in candidates.
66eb953f4380
Actions

Tags

None

Subscribers

None

Description

gpg: The first key should be in candidates.

* g10/getkey.c (get_best_pubkey_byname): Handle the first key
as the initial candidate for the selection.

Cherry-picked from master commit:
7535f1d47a35e30f736f0e842844555f7a4a9841

GnuPG-bug-id: T4713
Signed-off-by: NIIBE Yutaka <gniibe@fsij.org>

Details

Provenance

Authored on Oct 9 2019, 2:45 AM

Parents

rG2924ac374eb8: gpg: Fix a memory leak in get_best_pubkey_byname.

Branches

Unknown

Tags

Unknown

Reverted By

rG2906636b929f: Revert "gpg: The first key should be in candidates."

Tasks

T4713: Bug in get_best_pubkey_byname

Event Timeline

• gniibe committed rG66eb953f4380: gpg: The first key should be in candidates. (authored by • gniibe).Oct 15 2019, 2:47 AM

• gniibe added a task: T4713: Bug in get_best_pubkey_byname.

• gniibe added a reverting change: rG2906636b929f: Revert "gpg: The first key should be in candidates.".Oct 15 2019, 1:54 PM

• gniibe mentioned this in rG2906636b929f: Revert "gpg: The first key should be in candidates.".

Changes (1)

Path

Size

g10/

rG66eb953f4380

g10/getkey.c

Loading...