Include:Abuild-keygen: Difference between revisions
(add category package manager) |
Prabuanand (talk | contribs) (commented out obsolete information) |
||
| Line 1: | Line 1: | ||
For abuild a public/private rsa key pair is needed. < | For abuild a public/private rsa key pair is needed. The <code>abuild-keygen</code> command from {{pkg|abuild}} package generates and configures the security keys. | ||
{{Cmd|abuild-keygen -a -i}} | {{Cmd|$ doas abuild-keygen -a -i}} | ||
'''abuild-keygen options''' | '''abuild-keygen options''' | ||
| Line 10: | Line 10: | ||
* '''-n''' Non-interactive. Use defaults | * '''-n''' Non-interactive. Use defaults | ||
* '''-q''' Quiet mode | * '''-q''' Quiet mode | ||
<!-- | |||
==== Creating keys manually ==== | ==== Creating keys manually ==== | ||
| Line 27: | Line 26: | ||
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/$something.rsa}}. 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/$something.rsa}}. This basically means that the main developer's public keys should be in {{Path|/etc/apk/keys}} on all Alpine boxes. | ||
--> | |||
Revision as of 08:37, 18 February 2025
For abuild a public/private rsa key pair is needed. The abuild-keygen command from abuild package generates and configures the security keys.
$ doas abuild-keygen -a -i
abuild-keygen options
- -a Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i Install public key into /etc/apk/keys using sudo
- -h Show this help
- -n Non-interactive. Use defaults
- -q Quiet mode