gpg: revocation certificate stored as ’/home/pkgrepo/.gnupg/openpgp-revocs.d/
å
F8FE22F74F1B714E38DA6181B27F74F7B4EF2D0D.rev’
public and secret key created and signed.
gpg: checking the trustdb
gpg: marginals needed: 3
completes needed: 1
trust model: PGP
gpg: depth: 0
valid:
1
signed:
0
trust: 0-, 0q, 0n, 0m, 0f, 1u
pub
rsa2048/B4EF2D0D 2020-06-17 [S]
Key fingerprint = F8FE 22F7 4F1B 714E 38DA
6181 B27F 74F7 B4EF 2D0D
uid
[ultimate] Offensive Security Repository Signing Key
sub
rsa2048/38035F38 2020-06-17 []
Note that when you are prompted for a passphrase, you should enter an empty value (and confirm
that you don’t want to protect your private key) as you want to be able to sign the repository non-
interactively. Note also that
gpg
requires write access to the terminal to be able to securely prompt
for a passphrase: that is why you changed the ownership of the virtual terminal (which is owned
by root since you initially connected as that user) before starting a shell as pkgrepo.
Now you can start setting up the repository. A dedicated directory is necessary for
reprepro
and
inside that directory you have to create a
conf/distributions
file documenting which distribu-
tions are available in the package repository:
pkgrepo@kali:~$ mkdir -p reprepro/conf
pkgrepo@kali:~$ cd reprepro
pkgrepo@kali:~/reprepro$ cat >conf/distributions <