Skip to content

Fix signing instructions #458

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
attah wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix signing instructions #458

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions Develop/Apps/Packaging/Signing_Packages/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ The tool will ask all the necessary information. When unsure, select the default
If your gpg key is protected with a passphrase, you need to provide it to the sfdk tool via passphrase file. This is just a text file containing the passphrase. The permissions of the file should be 600, so that it’s not readable by anyone else. In the example below, we use a file called `passphrase.txt`, located in user's home directory. You can use a file/path of your own choosing instead.

```
$ echo “This is my passphrase” > $HOME/passphrase.txt
$ echo "This is my passphrase" > $HOME/passphrase.txt
$ chmod 0600 $HOME/passphrase.txt
```

Expand All @@ -33,8 +33,8 @@ $ chmod 0600 $HOME/passphrase.txt
The `sfdk` tool supports signing packages as part of the build process. First we need to configure the tool to use our key and passphrase file:

```
$ sfdk config package.signing.user=”Full Name” # replace Full Name with the name given when creating the signing key
$ sfdk config package.signing-passphrase-file=$HOME/passphrase.txt
$ sfdk config --global --push package.signing.user "Full Name" # replace Full Name with the name given when creating the signing key
$ sfdk config --global --push package.signing-passphrase-file $HOME/passphrase.txt
```
Then we can build the package with the `--sign` parameter:
```
Expand All @@ -60,7 +60,7 @@ RPMS/mypackage-0-1.noarch.rpm: digests signatures OK
However, you will likely get `digests SIGNATURES NOT OK` when you first try it. This is because the key used for signing is not known to `rpm`. You must import the key to the rpm keyring first:

```
$ gpg --output keyfile.gpg --armor --export “Full Name”
$ gpg --output keyfile.gpg --armor --export "Full Name"

$ rpm --import keyfile.gpg
```