From 010102c66dc1adc475608aec129d12fbc330ae29 Mon Sep 17 00:00:00 2001 From: Wiktor Kwapisiewicz Date: Mon, 2 Oct 2023 13:05:56 +0200 Subject: [PATCH 1/2] Add explanation on why manual certificate identity retrieval is needed --- changes/1473.doc.rst | 1 + docs/how-to/code-signing/macOS.rst | 4 ++++ docs/how-to/code-signing/windows.rst | 5 +++++ 3 files changed, 10 insertions(+) create mode 100644 changes/1473.doc.rst diff --git a/changes/1473.doc.rst b/changes/1473.doc.rst new file mode 100644 index 000000000..ab9f82a25 --- /dev/null +++ b/changes/1473.doc.rst @@ -0,0 +1 @@ +Add explanation on certificate identity retrieval for macOS and Windows diff --git a/docs/how-to/code-signing/macOS.rst b/docs/how-to/code-signing/macOS.rst index e7c4ad525..101622ce5 100644 --- a/docs/how-to/code-signing/macOS.rst +++ b/docs/how-to/code-signing/macOS.rst @@ -189,3 +189,7 @@ Next steps Now you can use the certificate to sign and notarize your application with the :doc:`briefcase package ` command. + +:doc:`briefcase package ` will ask you +about the code-signing certificate you want to use and it will +give you the command line for unattended installation. diff --git a/docs/how-to/code-signing/windows.rst b/docs/how-to/code-signing/windows.rst index 1240a04a3..b648395c7 100644 --- a/docs/how-to/code-signing/windows.rst +++ b/docs/how-to/code-signing/windows.rst @@ -67,6 +67,11 @@ Refer to your Certificate Authority's documentation for specific instructions. Certificate's SHA-1 Thumbprint ------------------------------ +Unfortunately, on Windows, :doc:`briefcase package +` cannot retrieve the code-signing +certificate's identity automatically so you will need to get it +manually. + The certificates installed on the machine are available in the Certificate Manager. Search for "User Certificates" in the Start Menu to access certificates for ``Current User`` or search for "Computer Certificates" for certificates for From bf58708dca316a0837a95b4a43fc3732e8f0ecd8 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Mon, 9 Oct 2023 20:45:59 +0200 Subject: [PATCH 2/2] Minor phrasing edits. --- changes/1473.doc.rst | 2 +- docs/how-to/code-signing/macOS.rst | 7 ++++--- docs/how-to/code-signing/windows.rst | 7 +++---- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/changes/1473.doc.rst b/changes/1473.doc.rst index ab9f82a25..b13a11ebb 100644 --- a/changes/1473.doc.rst +++ b/changes/1473.doc.rst @@ -1 +1 @@ -Add explanation on certificate identity retrieval for macOS and Windows +Documentation on the process of retrieving certificate identities on macOS and Windows was improved. diff --git a/docs/how-to/code-signing/macOS.rst b/docs/how-to/code-signing/macOS.rst index 101622ce5..fd9fb8226 100644 --- a/docs/how-to/code-signing/macOS.rst +++ b/docs/how-to/code-signing/macOS.rst @@ -190,6 +190,7 @@ Next steps Now you can use the certificate to sign and notarize your application with the :doc:`briefcase package ` command. -:doc:`briefcase package ` will ask you -about the code-signing certificate you want to use and it will -give you the command line for unattended installation. +When you invoke :doc:`briefcase package `, you will be +prompted to select the code signing certificate you want to use from the certificates +that are installed. Once you select a certificate, Briefcase will output the command +line invocation to select that certificate for unattended installation. diff --git a/docs/how-to/code-signing/windows.rst b/docs/how-to/code-signing/windows.rst index b648395c7..8377dc889 100644 --- a/docs/how-to/code-signing/windows.rst +++ b/docs/how-to/code-signing/windows.rst @@ -67,10 +67,9 @@ Refer to your Certificate Authority's documentation for specific instructions. Certificate's SHA-1 Thumbprint ------------------------------ -Unfortunately, on Windows, :doc:`briefcase package -` cannot retrieve the code-signing -certificate's identity automatically so you will need to get it -manually. +On Windows, :doc:`briefcase package ` cannot retrieve the +list of installed code signing certificates automatically. You need to retrieve the +identity manually, and provide the certificates identity as a command line argument. The certificates installed on the machine are available in the Certificate Manager. Search for "User Certificates" in the Start Menu to access certificates