Include:Abuild-keygen - Revision history

Prabuanand: moved content from here to Abuild_and_Helpers#Signing_packages_and_indexes so this page can be transcluded wherever needed

2025-03-14T10:06:11Z

moved content from here to Abuild_and_Helpers#Signing_packages_and_indexes so this page can be transcluded wherever needed

← Older revision		Revision as of 10:06, 14 March 2025
Line 1:		Line 1:
	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.		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\|$ 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 {{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 ====~~

	~~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>.~~

	~~Since the public key needs to be unique for each developer, the email address should be used as name for the public key.~~

	~~Create the private key:~~
	~~{{cmd\|openssl genrsa -out ''emailaddress.priv'' 2048}}~~

	~~{{tip\|Append ''-aes256'' if you want it encrypted, but then you'll need to enter the password for every package you sign}}~~

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

Prabuanand: removed extra lines

2025-03-13T17:42:51Z

removed extra lines

← Older revision		Revision as of 17:42, 13 March 2025
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 ====

Prabuanand: reduced redundant space

2025-03-13T17:30:02Z

reduced redundant space

← Older revision		Revision as of 17:30, 13 March 2025
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''}}-->

	-->

Prabuanand: fixed the command updated the help message as per current version

2025-03-13T17:27:26Z

fixed the command updated the help message as per current version

← Older revision		Revision as of 17:27, 13 March 2025
Line 1:		Line 1:
	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.		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\|$ ~~doas~~ abuild-keygen -a -i}}		{{Cmd\|$ 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

	~~'''~~abuild~~-keygen options''~~'		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.

	* '''-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
	<!--		<!--
	==== Creating keys manually ====		==== Creating keys manually ====
Line 25:		Line 28:
	{{cmd\|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}		{{cmd\|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}

	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.
	-->		-->

Prabuanand: commented out obsolete information

2025-02-18T08:37:50Z

commented out obsolete information

← Older revision		Revision as of 08:37, 18 February 2025
Line 1:		Line 1:
	For abuild a public/private rsa key pair is needed. <tt>abuild-keygen</tt> ~~does~~ the ~~generation of those~~ keys ~~for you~~.		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.
			-->
	~~[[Category:Development]]~~
	~~[[Category:Package Manager]]~~

Sertonix: add category package manager

2023-08-25T01:07:15Z

add category package manager

← Older revision		Revision as of 01:07, 25 August 2023
Line 29:		Line 29:

	[[Category:Development]]		[[Category:Development]]
			[[Category:Package Manager]]

EvanCarroll at 05:46, 19 February 2021

2021-02-19T05:46:21Z

← Older revision		Revision as of 05:46, 19 February 2021
Line 26:		Line 26:
	{{cmd\|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}		{{cmd\|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}

	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 ~~{{cmd\|~~abuild}}, 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.

	[[Category:Development]]		[[Category:Development]]

EvanCarroll: added note about the default for private key

2021-02-19T05:45:41Z

added note about the default for private key

← Older revision		Revision as of 05:45, 19 February 2021
Line 26:		Line 26:
	{{cmd\|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}		{{cmd\|openssl rsa -in ''emailaddress.priv'' -pubout -out /etc/apk/keys/''emailaddress''}}

	The public key should be distributed and installed into {{Path\|/etc/apk/keys}} on the alpine box that will install the packages. 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 {{cmd\|abuild}}, 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.

	[[Category:Development]]		[[Category:Development]]

Dubiousjim: Dubiousjim moved page Abuild-keygen to Include:Abuild-keygen

2012-10-29T04:11:30Z

Dubiousjim moved page Abuild-keygen to Include:Abuild-keygen

← Older revision	Revision as of 04:11, 29 October 2012
(No difference)

Dubiousjim: formatting

2012-10-22T12:14:26Z

formatting

← Older revision		Revision as of 12:14, 22 October 2012
Line 12:		Line 12:


	=== 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>.