Managing ACF - Revision history

Prabuanand: added installation link

2025-03-10T06:48:57Z

added installation link

← Older revision		Revision as of 06:48, 10 March 2025
Line 1:		Line 1:
	[[ACF]] is a powerful web application for configuring your Alpine Linux device. While all efforts are made to make ACF a secure application, it is, by its very nature, dangerous. The purpose of ACF is to give users the ability to administer the services running on the system. It is up to the system administrator to ensure that users do not receive more priviliges on ACF than they should have. Access control is provided by the following means:		[[ACF]] is a powerful web application for configuring your Alpine Linux device. While all efforts are made to make ACF a secure application, it is, by its very nature, dangerous. The purpose of ACF is to give users the ability to administer the services running on the system. Once [[Alpine_Configuration_Framework_Design#Installation\|ACF is installed]], it is up to the system administrator to ensure that users do not receive more priviliges on ACF than they should have. Access control is provided by the following means:

	*System Configuration		*System Configuration

Prabuanand: fixed headings and removed obsolete information fixed wiki tags

2025-03-10T06:40:13Z

fixed headings and removed obsolete information fixed wiki tags

← Older revision		Revision as of 06:40, 10 March 2025
Line 1:		Line 1:
	~~= Managing Your ACF Installation =~~		[[ACF]] is a powerful web application for configuring your Alpine Linux device. While all efforts are made to make ACF a secure application, it is, by its very nature, dangerous. The purpose of ACF is to give users the ability to administer the services running on the system. It is up to the system administrator to ensure that users do not receive more priviliges on ACF than they should have. Access control is provided by the following means:

	ACF is a powerful web application for configuring your Alpine Linux device. While all efforts are made to make ACF a secure application, it is, by its very nature, dangerous. The purpose of ACF is to give users the ability to administer the services running on the system. It is up to the system administrator to ensure that users do not receive more priviliges on ACF than they should have. Access control is provided by the following means:

	*System Configuration		*System Configuration
Line 22:		Line 20:
	ACF includes user management under the '''System''' \| '''User Management''' menu. Select the '''New User''' button to create a new user. Separate user accounts should be created for each ACF user. Each user account may belong to any number of ACF roles.		ACF includes user management under the '''System''' \| '''User Management''' menu. Select the '''New User''' button to create a new user. Separate user accounts should be created for each ACF user. Each user account may belong to any number of ACF roles.

	In Alpine Linux 1.8, the system includes two default users: ''alpine'' and ''foo''. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In Alpine Linux 1.9 and later, you will be prompted to create an initial user the first time you try to log in. If you install ACF using the ~~'''~~setup-acf~~'''~~ script, you will be prompted for a password, and a ''root'' user will be created.		{{Note\|If you install ACF using the <code>[[Alpine_setup_scripts#setup-acf\|setup-acf]]</code> script, you will be prompted for a password, and a ''root'' user will be created. If you installed ACF before defining the root password, you must execute the command {{Cmd\|# acfpasswd -s root}}}}

	~~{{Warning\|~~If you installed ACF before defining the root password, you must execute ~~'''~~acfpasswd -s root~~'''~~}}

	== Roles Management ==		== Roles Management ==
Line 54:		Line 50:
	These built-in roles can be selected on a controller-by-controller basis (ie. /alpine-baselayout/alpine-baselayout/ADMIN) or globally (ie. ADMIN). The global built-in roles consist of all of the permissions of all of the corresponding controller-by-controller roles (ie. ADMIN contains /x/y/ADMIN for every x and y installed).		These built-in roles can be selected on a controller-by-controller basis (ie. /alpine-baselayout/alpine-baselayout/ADMIN) or globally (ie. ADMIN). The global built-in roles consist of all of the permissions of all of the corresponding controller-by-controller roles (ie. ADMIN contains /x/y/ADMIN for every x and y installed).

	ACF packages may also include built-in roles that define specific usage scenarios for that package. For instance, acf-openssl is a fully functional certificate authority that separates the roles of submitting and approving certificate requests:		ACF packages may also include built-in roles that define specific usage scenarios for that package. For instance, {{pkg\|acf-openssl}} is a fully functional certificate authority that separates the roles of submitting and approving certificate requests:

	{\| width="100%" border="1"		{\| width="100%" border="1"
Line 74:		Line 70:

	== Package-specific Management ==		== Package-specific Management ==
			{{Seealso\|ACF packages}}
			ACF packages may include their own package-specific management. {{pkg\|acf-tinydns}} package manages a tinydns DNS server and includes permissions management on a domain by domain basis. This is available under the '''Networking''' \| '''DNS''' \| '''Permissions''' tab. The tinydns ACF package is designed to keep configuration for each domain in a separate file (see the '''List Domains''' tab). Permissions can then be set as to which domains may be viewed / edited by a specific user or members of a particular role.

	~~ACF packages may include their own package-specific management.~~		== See also ==

	acf-tinydns manages a tinydns DNS server and includes permissions management on a domain by domain basis. This is available under the '''Networking''' \| '''DNS''' \| '''Permissions''' tab. The tinydns ACF package is designed to keep configuration for each domain in a separate file (see the '''List Domains''' tab). Permissions can then be set as to which domains may be viewed / edited by a specific user or members of a particular role.

	~~= More Information =~~		[[Alpine Configuration Framework Design]]
	~~For more information, please see~~ [[Alpine Configuration Framework Design]].

	[[Category:ACF]]		[[Category:ACF]]
	[[Category:Security]]		[[Category:Security]]

Sertonix: replace /etc/init.d with rc-service

2023-11-17T10:11:43Z

replace /etc/init.d with rc-service

← Older revision		Revision as of 10:11, 17 November 2023
Line 16:		Line 16:
	*Limit ACF access to specified IP or MAC addresses		*Limit ACF access to specified IP or MAC addresses

	{{tip\|By default, ACF use '''mini_httpd''' and use port '''443'''. If you would like to change this port you simply have to specify the port in '''/etc/mini_httpd/mini_httpd.conf''' and restart: '''~~/etc/init.d/~~mini_httpd restart'''}}		{{tip\|By default, ACF use '''mini_httpd''' and use port '''443'''. If you would like to change this port you simply have to specify the port in '''/etc/mini_httpd/mini_httpd.conf''' and restart: '''rc-service mini_httpd restart'''}}

	== User Management ==		== User Management ==

Aduty: /* User Management */

2019-05-21T21:19:03Z

User Management

← Older revision		Revision as of 21:19, 21 May 2019
Line 24:		Line 24:
	In Alpine Linux 1.8, the system includes two default users: ''alpine'' and ''foo''. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In Alpine Linux 1.9 and later, you will be prompted to create an initial user the first time you try to log in. If you install ACF using the '''setup-acf''' script, you will be prompted for a password, and a ''root'' user will be created.		In Alpine Linux 1.8, the system includes two default users: ''alpine'' and ''foo''. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In Alpine Linux 1.9 and later, you will be prompted to create an initial user the first time you try to log in. If you install ACF using the '''setup-acf''' script, you will be prompted for a password, and a ''root'' user will be created.

	{{Warning\|If you ~~did install~~ ACF before ~~define~~ the root password, you must execute '''acfpasswd -s root'''}}		{{Warning\|If you installed ACF before defining the root password, you must execute '''acfpasswd -s root'''}}

	== Roles Management ==		== Roles Management ==

Aduty: /* System Configuration */

2019-05-21T21:16:56Z

System Configuration

← Older revision		Revision as of 21:16, 21 May 2019
Line 16:		Line 16:
	*Limit ACF access to specified IP or MAC addresses		*Limit ACF access to specified IP or MAC addresses

	{{tip\|By default, ACF use '''mini_httpd''' and use port '''443'''. If you would like to change this port you simply have to specify the port in '''/etc/mini_httpd/mini_httpd.conf''' ~~than~~ restart '''/etc/init.d/mini_httpd restart'''}}		{{tip\|By default, ACF use '''mini_httpd''' and use port '''443'''. If you would like to change this port you simply have to specify the port in '''/etc/mini_httpd/mini_httpd.conf''' and restart: '''/etc/init.d/mini_httpd restart'''}}

	== User Management ==		== User Management ==

Jodumont: add 2tips about port + password

2018-02-07T10:37:17Z

add 2tips about port + password

← Older revision		Revision as of 10:37, 7 February 2018
Line 15:		Line 15:
	*Do not make ACF available on Internet connections (if possible)		*Do not make ACF available on Internet connections (if possible)
	*Limit ACF access to specified IP or MAC addresses		*Limit ACF access to specified IP or MAC addresses

			{{tip\|By default, ACF use '''mini_httpd''' and use port '''443'''. If you would like to change this port you simply have to specify the port in '''/etc/mini_httpd/mini_httpd.conf''' than restart '''/etc/init.d/mini_httpd restart'''}}

	== User Management ==		== User Management ==
Line 21:		Line 23:

	In Alpine Linux 1.8, the system includes two default users: ''alpine'' and ''foo''. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In Alpine Linux 1.9 and later, you will be prompted to create an initial user the first time you try to log in. If you install ACF using the '''setup-acf''' script, you will be prompted for a password, and a ''root'' user will be created.		In Alpine Linux 1.8, the system includes two default users: ''alpine'' and ''foo''. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In Alpine Linux 1.9 and later, you will be prompted to create an initial user the first time you try to log in. If you install ACF using the '''setup-acf''' script, you will be prompted for a password, and a ''root'' user will be created.

			{{Warning\|If you did install ACF before define the root password, you must execute '''acfpasswd -s root'''}}

	== Roles Management ==		== Roles Management ==

Dubiousjim: add Category:Security

2012-06-01T13:41:38Z

add Category:Security

← Older revision		Revision as of 13:41, 1 June 2012
Line 79:		Line 79:

	[[Category:ACF]]		[[Category:ACF]]
			[[Category:Security]]

Dubiousjim: Category:ACF

2012-03-12T07:22:52Z

Category:ACF

← Older revision		Revision as of 07:22, 12 March 2012
Line 77:		Line 77:
	= More Information =		= More Information =
	For more information, please see [[Alpine Configuration Framework Design]].		For more information, please see [[Alpine Configuration Framework Design]].

			[[Category:ACF]]

Mattx86: Added "More Information" section with a link to "Alpine Configuration Framework Design."

2010-08-14T02:05:06Z

Added "More Information" section with a link to "Alpine Configuration Framework Design."

← Older revision		Revision as of 02:05, 14 August 2010
Line 74:		Line 74:

	acf-tinydns manages a tinydns DNS server and includes permissions management on a domain by domain basis. This is available under the '''Networking''' \| '''DNS''' \| '''Permissions''' tab. The tinydns ACF package is designed to keep configuration for each domain in a separate file (see the '''List Domains''' tab). Permissions can then be set as to which domains may be viewed / edited by a specific user or members of a particular role.		acf-tinydns manages a tinydns DNS server and includes permissions management on a domain by domain basis. This is available under the '''Networking''' \| '''DNS''' \| '''Permissions''' tab. The tinydns ACF package is designed to keep configuration for each domain in a separate file (see the '''List Domains''' tab). Permissions can then be set as to which domains may be viewed / edited by a specific user or members of a particular role.

			= More Information =
			For more information, please see [[Alpine Configuration Framework Design]].

Ttrask: Updated for 1.10 and alpine -> Alpine Linux

2010-06-28T14:48:31Z

Updated for 1.10 and alpine -> Alpine Linux

← Older revision		Revision as of 14:48, 28 June 2010
Line 1:		Line 1:
	= Managing Your ACF Installation =		= Managing Your ACF Installation =

	ACF is a powerful web application for configuring your ~~alpine~~ device. While all efforts are made to make ACF a secure application, it is, by its very nature, dangerous. The purpose of ACF is to give users the ability to administer the services running on the system. It is up to the system administrator to ensure that users do not receive more priviliges on ACF than they should have. Access control is provided by the following means:		ACF is a powerful web application for configuring your Alpine Linux device. While all efforts are made to make ACF a secure application, it is, by its very nature, dangerous. The purpose of ACF is to give users the ability to administer the services running on the system. It is up to the system administrator to ensure that users do not receive more priviliges on ACF than they should have. Access control is provided by the following means:

	*System Configuration		*System Configuration
Line 10:		Line 10:
	== System Configuration ==		== System Configuration ==

	System administrators can do much to limit inappropriate access to ACF by properly managing the firewall and http services on the ~~alpine~~ device. Lock down access to ACF as much as possible. The following steps are highly recommended:		System administrators can do much to limit inappropriate access to ACF by properly managing the firewall and http services on the Alpine Linux device. Lock down access to ACF as much as possible. The following steps are highly recommended:

	*Limit ACF to encrypted (HTTPS) access		*Limit ACF to encrypted (HTTPS) access
Line 20:		Line 20:
	ACF includes user management under the '''System''' \| '''User Management''' menu. Select the '''New User''' button to create a new user. Separate user accounts should be created for each ACF user. Each user account may belong to any number of ACF roles.		ACF includes user management under the '''System''' \| '''User Management''' menu. Select the '''New User''' button to create a new user. Separate user accounts should be created for each ACF user. Each user account may belong to any number of ACF roles.

	In ~~alpine~~ 1.8, the system includes two default users: ''alpine'' and ''foo''. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In ~~alpine~~ 1.9, you will be prompted to create an initial user the first time you try to log in.		In Alpine Linux 1.8, the system includes two default users: ''alpine'' and ''foo''. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In Alpine Linux 1.9 and later, you will be prompted to create an initial user the first time you try to log in. If you install ACF using the '''setup-acf''' script, you will be prompted for a password, and a ''root'' user will be created.

	== Roles Management ==		== Roles Management ==
Line 48:		Line 48:
	\|}		\|}

	ACF packages may also include built-in roles that define specific usage scenarios for that package. For instance, acf-openssl is a fully ~~functionaly~~ certificate authority that separates the roles of ~~submiting~~ and approving certificate requests:		These built-in roles can be selected on a controller-by-controller basis (ie. /alpine-baselayout/alpine-baselayout/ADMIN) or globally (ie. ADMIN). The global built-in roles consist of all of the permissions of all of the corresponding controller-by-controller roles (ie. ADMIN contains /x/y/ADMIN for every x and y installed).

			ACF packages may also include built-in roles that define specific usage scenarios for that package. For instance, acf-openssl is a fully functional certificate authority that separates the roles of submitting and approving certificate requests:

	{\| width="100%" border="1"		{\| width="100%" border="1"