Include:Abuild-keygen: Difference between revisions
Prabuanand (talk | contribs) m (reduced redundant space) |
Prabuanand (talk | contribs) m (removed extra lines) |
||
| Line 12: | Line 12: | ||
The public key should be distributed and installed into {{Path|/etc/apk/keys}} on the alpine box that will install the packages. The private key, when created by <code>abuild</code>, is installed into {{Path|~/.abuild/abuild.conf}}. This basically means that the main developer's public keys should be in {{Path|/etc/apk/keys}} on all Alpine boxes. | The public key should be distributed and installed into {{Path|/etc/apk/keys}} on the alpine box that will install the packages. The private key, when created by <code>abuild</code>, is installed into {{Path|~/.abuild/abuild.conf}}. This basically means that the main developer's public keys should be in {{Path|/etc/apk/keys}} on all Alpine boxes. | ||
<!--==== Creating keys manually ==== | <!--==== Creating keys manually ==== | ||
Revision as of 17:42, 13 March 2025
For abuild a public/private rsa key pair is needed. The abuild-keygen command from abuild package generates and configures the security keys.
$ abuild-keygen -a -i
Options:
- -a, --append Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i, --install Install public key into /etc/apk/keys using doas/sudo
- -n Non-interactive. Use defaults
- --kernel Generate a key for kernel modules
- -b, --numbits [BITS] The size of the private key to generate in bits.
- -q Quiet mode
- -h Show this help
The public key should be distributed and installed into /etc/apk/keys on the alpine box that will install the packages. The private key, when created by abuild, is installed into ~/.abuild/abuild.conf. This basically means that the main developer's public keys should be in /etc/apk/keys on all Alpine boxes.