From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-doc@vger.kernel.org
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Jonathan Corbet" <corbet@lwn.net>,
"Alessia Mantegazza" <amantegazza@vaga.pv.it>,
linux-kernel@vger.kernel.org
Subject: [PATCH] docs: it_IT: maintainer-pgp-guide: Fix reference to "Nitrokey Pro 2"
Date: Wed, 2 Oct 2019 17:18:39 +0200 [thread overview]
Message-ID: <20191002151841.18476-1-j.neuschaefer@gmx.net> (raw)
This fixes the following Sphinx warning:
Documentation/translations/it_IT/process/maintainer-pgp-guide.rst:458:
WARNING: Unknown target name: "nitrokey pro".
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
---
.../translations/it_IT/process/maintainer-pgp-guide.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/it_IT/process/maintainer-pgp-guide.rst b/Documentation/translations/it_IT/process/maintainer-pgp-guide.rst
index 118fb4153e8f..f3c8e8d377ee 100644
--- a/Documentation/translations/it_IT/process/maintainer-pgp-guide.rst
+++ b/Documentation/translations/it_IT/process/maintainer-pgp-guide.rst
@@ -455,7 +455,7 @@ soluzioni disponibili:
`GnuK`_ della FSIJ. Questo è uno dei pochi dispositivi a supportare le chiavi
ECC ED25519, ma offre meno funzionalità di sicurezza (come la resistenza
alla manomissione o alcuni attacchi ad un canale laterale).
-- `Nitrokey Pro`_: è simile alla Nitrokey Start, ma è più resistente alla
+- `Nitrokey Pro 2`_: è simile alla Nitrokey Start, ma è più resistente alla
manomissione e offre più funzionalità di sicurezza. La Pro 2 supporta la
crittografia ECC (NISTP).
- `Yubikey 5`_: l'hardware e il software sono proprietari, ma è più economica
--
2.20.1
next reply other threads:[~2019-10-02 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 15:18 Jonathan Neuschäfer [this message]
2019-10-03 16:19 ` [PATCH] docs: it_IT: maintainer-pgp-guide: Fix reference to "Nitrokey Pro 2" Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191002151841.18476-1-j.neuschaefer@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=amantegazza@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).