Include:Abuild-keygen: Difference between revisions

From Alpine Linux
(fixed the command updated the help message as per current version)
m (reduced redundant space)
Line 13: Line 13:
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 ====


In older versions of Alpine, we had to manually create keys for signing packages and indexes. This explains how. Nowadays you can just use <code>abuild-keygen</code>.
In older versions of Alpine, we had to manually create keys for signing packages and indexes. This explains how. Nowadays you can just use <code>abuild-keygen</code>.
Line 26: Line 25:


Create the public key:
Create the public key:
{{cmd|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}
{{cmd|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}-->
 
-->

Revision as of 17:30, 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.