From 4c3503a739490ddc2f37b5bcef66ecf6d03a11c5 Mon Sep 17 00:00:00 2001 From: marinamoore Date: Fri, 4 Oct 2019 10:58:34 -0400 Subject: [PATCH] changed minilock example to yubikey --- pep-0458.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pep-0458.txt b/pep-0458.txt index a5067b51a52..68e79d6591c 100644 --- a/pep-0458.txt +++ b/pep-0458.txt @@ -932,7 +932,7 @@ in this section: delegate trust of these wheels to an online role. 2. An easy-to-use key management solution is needed for developers. - `miniLock`__ is one likely candidate for management and generation of keys. + `YubiKey`__ is one likely candidate for management and generation of keys. Although developer signatures can remain optional, this approach may be inadequate due to the great number of potentially unsigned dependencies each distribution may have. If any one of these dependencies is unsigned, it @@ -942,7 +942,7 @@ in this section: distributions and manage keys is expected to render key signing an unused feature. - __ https://github.com/kaepora/miniLock + __ https://www.yubico.com/products/yubikey-hardware/ 3. A two-phase approach, where the minimum security model is implemented first followed by the maximum security model, can simplify matters and give PyPI