You want to check which correspondents' keys you already hold before encrypting anything. Type the gpg command, using its long option and no key arguments, that lists the public keys in your keyring.

LPIC-1 Exam 102-500, objective 110. Security easy

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

Answer

Type the answer.

Accepted answers

Case sensitive — Linux is, and grading LS as ls would teach a falsehood.

Why

gpg --list-keys, abbreviated -k, prints the public keyring: for each key a pub line with the algorithm, key ID and creation date, and one or more uid lines with the associated names and addresses. The counterpart --list-secret-keys, or -K, shows the private keys you hold, which is how you confirm you can actually decrypt or sign. Both read from the GnuPG home directory, ~/.gnupg by default or whatever --homedir names.

Where this comes from

Cited
manual page gpg(1)

Practise this

Reading one question is not practice. The trainer will draw a short set from objective 110 and space the ones you get wrong.

Practise LPIC-1 Exam 102-500

More questions on this objective

All questions on Security

Practise LPIC-1 Exam 102-500