aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorsaturneric <[email protected]>2026-08-11 01:08:39 +0200
committersaturneric <[email protected]>2026-08-11 01:08:39 +0200
commit37786594af861d8cc7ac39eed13164f2a86d4fb2 (patch)
treed3f120f16af49ee0ecd72afe2a9aa3583b8f9025
parentci(workflows): bump docker-build workflow action (diff)
downloadmanual-37786594af861d8cc7ac39eed13164f2a86d4fb2.tar.gz
manual-37786594af861d8cc7ac39eed13164f2a86d4fb2.zip
docs(guides): clarify rPGP engine limitations
- remove note about hidden expiration options (rPGP lacks support) - simplify rPGP v5 caution; clarify it cannot use v5 keys - remove paragraph about engine reporting of key fields (redundant)
-rw-r--r--src/content/docs/guides/generate-key.md7
-rw-r--r--src/content/docs/guides/view-keypair-info.md10
2 files changed, 2 insertions, 15 deletions
diff --git a/src/content/docs/guides/generate-key.md b/src/content/docs/guides/generate-key.md
index adfc82a..1d0f61e 100644
--- a/src/content/docs/guides/generate-key.md
+++ b/src/content/docs/guides/generate-key.md
@@ -88,13 +88,6 @@ Only profiles that work with your current engine and key database are shown.
- **Primary Key With Subkey**: useful for keeping signing and encryption
separate.
-:::note
-
-When the rPGP engine is selected, the expiration options are hidden, because the
-engine has limited support for setting how long a key stays valid.
-
-:::
-
For full control over the algorithm, key length, and format, switch to Advanced
Mode (the **Primary Key** and **Subkey** tabs). The supported algorithms and
compatibility notes are below.
diff --git a/src/content/docs/guides/view-keypair-info.md b/src/content/docs/guides/view-keypair-info.md
index e26ee45..1c43e9b 100644
--- a/src/content/docs/guides/view-keypair-info.md
+++ b/src/content/docs/guides/view-keypair-info.md
@@ -100,17 +100,11 @@ tools support only one of the two.
:::caution[The rPGP engine cannot read v5 keys]
-rPGP follows RFC 9580 only. It can tell you that a key is v5, but it cannot
-open it. The key shows up in the list, but you cannot use it.
-
-If you work with v5 keys, use a GnuPG key database for them. See
-[Multi-Key Database](/advanced/key-database/).
+rPGP follows RFC 9580 only. It cannot use a v5 key. If you work with v5 keys,
+use a GnuPG key database for them. See [Multi-Key Database](/advanced/key-database/).
:::
-This field is shown only when the active engine can report it. The rPGP engine
-can; GnuPG cannot, so it is hidden for keys loaded through the GnuPG engine.
-
#### Last Update
When the key pair's content last changed. Adding a UID or subkey counts as a