[pve-devel] [PATCH docs] pveum: u2f: defuse the warning about certificates

[pve-devel] [PATCH docs] pveum: u2f: defuse the warning about certificates

[Dominik Csapak]

since it seems (currently) to work with self-signed certificates as well
tested in chromium/chrome/firefox

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
 pveum.adoc | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/pveum.adoc b/pveum.adoc
index 1f7c69f..602332d 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -328,8 +328,9 @@ field before pressing the 'Apply' button.
 Server side U2F configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To allow users to use 'U2F' authentication, the server needs to have a valid
-domain with a valid https certificate. Initially an 'AppId'
+To allow users to use 'U2F' authentication, it may be necessary to use a valid
+domain with a valid https certificate, otherwise some browsers may print
+a warning or reject U2F usage altogether. Initially an 'AppId'
 footnote:[AppId https://developers.yubico.com/U2F/App_ID.html]
 needs to be configured.
 
-- 
2.20.1

[pve-devel] applied: [PATCH docs] pveum: u2f: defuse the warning about certificates

[Thomas Lamprecht]

On 29.04.21 12:28, Dominik Csapak wrote:
> since it seems (currently) to work with self-signed certificates as well
> tested in chromium/chrome/firefox
> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
>  pveum.adoc | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
>

applied, thanks! PBS may need this too, IIRC the user in the forum used got it
from that docs.