Contextualization of Linux VMs - Revision history

Stoyan: /* Custom Vars */

2017-04-24T13:26:22Z

Custom Vars

← Older revision		Revision as of 13:26, 24 April 2017
Line 49:		Line 49:
	*: sudo -s		*: sudo -s

	* '''CRYPTED_PASSWORD_BASE64''' - Crypted password encoded in base64~~. To be set for the user USERNAME. If not defined it will change root user~~. You can use the following command:		* '''CRYPTED_PASSWORD_BASE64''' - Crypted password encoded in base64. You can use the following command:
	*: openssl passwd -1 \| base64		*: openssl passwd -1 \| base64

Stoyan: /* Custom Vars */

2017-04-24T13:25:23Z

Custom Vars

← Older revision		Revision as of 13:25, 24 April 2017
Line 52:		Line 52:
	*: openssl passwd -1 \| base64		*: openssl passwd -1 \| base64

	* '''~~PASSWORD_BASE64~~''' - ~~Password encoded in base64~~. ~~To be set for~~ the ~~user USERNAME.~~		* '''CRYPTED_PASSWORD''' - Crypted password. This parameter is not recommended, use CRYPTED_PASSWORD_BASE64 instead. You can use the following command:
			*: openssl passwd -1

	* '''~~CRYPTED_PASSWORD~~''' - ~~Crypted~~ password~~. To be set for the user USERNAME~~. This parameter is not recommended, use CRYPTED_PASSWORD_BASE64 instead. ~~You can use the following~~ command:		* '''PASSWORD_BASE64''' - Clear text password encoded in base64. This parameter is not recommended, use CRYPTED_PASSWORD_BASE64 instead. Example command:
	*: ~~openssl passwd -1~~		*: echo "Password" \| base64

	* '''PASSWORD''' - ~~Password~~ to be set for the user USERNAME. This parameter is not recommended, use ~~PASSWORD_BASE64~~ instead.		* '''PASSWORD''' - Clear text password to be set for the user USERNAME. This parameter is not recommended, use CRYPTED_PASSWORD_BASE64 instead.

	The following attributes are automatically filled up configuring the Network section of the template:		The following attributes are automatically filled up configuring the Network section of the template:

Valentina at 13:43, 21 April 2017

2017-04-21T13:43:02Z

← Older revision		Revision as of 13:43, 21 April 2017
Line 78:		Line 78:
	* '''ETHx_DNS''' - DNS for the network		* '''ETHx_DNS''' - DNS for the network

	These last attributes are also automatically filled up adding SSH public keys in the [[Contextualization_of_Linux_VMs#Configuration \| Context Configuration Section]]:		These last attributes are also automatically filled up adding SSH public keys in the [[Contextualization_of_Linux_VMs#Configuration \| Context Configuration Section]] of the template:
	* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.		* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.

	* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY		* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY

Valentina at 13:42, 21 April 2017

2017-04-21T13:42:45Z

← Older revision		Revision as of 13:42, 21 April 2017
Line 78:		Line 78:
	* '''ETHx_DNS''' - DNS for the network		* '''ETHx_DNS''' - DNS for the network

	These last attributes are also automatically filled up adding SSH public keys in the [[Contextualization_of_Linux_VMs#Configuration \| Configuration Section]]:		These last attributes are also automatically filled up adding SSH public keys in the [[Contextualization_of_Linux_VMs#Configuration \| Context Configuration Section]]:
	* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.		* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.

	* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY		* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY

Valentina at 13:42, 21 April 2017

2017-04-21T13:42:04Z

← Older revision		Revision as of 13:42, 21 April 2017
Line 59:		Line 59:
	* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.		* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.

	The following attributes are automatically filled up configuring the Network:		The following attributes are automatically filled up configuring the Network section of the template:
	* '''ETHx_MAC''' - Used to find the correct interface		* '''ETHx_MAC''' - Used to find the correct interface

Valentina at 13:32, 21 April 2017

2017-04-21T13:32:56Z

← Older revision		Revision as of 13:32, 21 April 2017
Line 78:		Line 78:
	* '''ETHx_DNS''' - DNS for the network		* '''ETHx_DNS''' - DNS for the network

	These last attributes are also automatically filled up ~~if you add~~ SSH public keys in the [[Contextualization_of_Linux_VMs#Configuration \| Configuration Section]]:		These last attributes are also automatically filled up adding SSH public keys in the [[Contextualization_of_Linux_VMs#Configuration \| Configuration Section]]:
	* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.		* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.

	* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY		* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY

Valentina at 13:25, 21 April 2017

2017-04-21T13:25:22Z

← Older revision		Revision as of 13:25, 21 April 2017
Line 59:		Line 59:
	* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.		* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.

	The following attributes are automatically filled up configuring the Network ~~and the [[Contextualization_of_Linux_VMs#Configuration \| Context Configuration]] section of the template~~:		The following attributes are automatically filled up configuring the Network:
	* '''ETHx_MAC''' - Used to find the correct interface		* '''ETHx_MAC''' - Used to find the correct interface

Line 78:		Line 78:
	* '''ETHx_DNS''' - DNS for the network		* '''ETHx_DNS''' - DNS for the network

			These last attributes are also automatically filled up if you add SSH public keys in the [[Contextualization_of_Linux_VMs#Configuration \| Configuration Section]]:
	* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.		* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.

	* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY		* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY

Valentina at 13:22, 21 April 2017

2017-04-21T13:22:33Z

← Older revision		Revision as of 13:22, 21 April 2017
Line 59:		Line 59:
	* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.		* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.

	The following attributes are automatically filled up configuring the Network and [[Contextualization_of_Linux_VMs#Configuration \| Context Configuration]] section of the template:		The following attributes are automatically filled up configuring the Network and the [[Contextualization_of_Linux_VMs#Configuration \| Context Configuration]] section of the template:
	* '''ETHx_MAC''' - Used to find the correct interface		* '''ETHx_MAC''' - Used to find the correct interface

Valentina: /* Custom Vars */

2017-04-21T13:17:26Z

Custom Vars

← Older revision		Revision as of 13:17, 21 April 2017
Line 59:		Line 59:
	* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.		* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.

	The following attributes are automatically filled up configuring the ~~network~~ and ~~context~~ section of the template:		The following attributes are automatically filled up configuring the Network and [[Contextualization_of_Linux_VMs#Configuration \| Context Configuration]] section of the template:
	* '''ETHx_MAC''' - Used to find the correct interface		* '''ETHx_MAC''' - Used to find the correct interface

Valentina at 13:15, 21 April 2017

2017-04-21T13:15:33Z

← Older revision		Revision as of 13:15, 21 April 2017
Line 46:		Line 46:
	* '''DNS''' - Specific DNS server for the Virtual Machine		* '''DNS''' - Specific DNS server for the Virtual Machine

			* '''USERNAME''' - User to be created in the guest OS. If any password attribute is defined (see below) it will change this user (defaults to root). '''Please note:''' SSH daemon on the host is configured to deny access to user '''root''' and it does not support password authentication. If you specify '''USERNAME''' such account will be created and any SSH keys you may have configured will be allowed to login as that user. If you use any of the context variables below then password will be set for the user too. If username is not root you will be able to SSH in using SSH key and you will be able to login on the VNC console but you will '''not be able escalate your privileges''' to root. If username is '''root''' or you do not use '''USERNAME''' then you will be able to login on the VNC console but you will not be able to SSH in. '''Contextualization script always creates an user ''cloudUser'' which is allowed to login SSH using the keys you have configured in the template. Also cloudUser is allowed to elevate its privileges via sudo without password. the following command will make you root without password:'''
			*: sudo -s

			* '''CRYPTED_PASSWORD_BASE64''' - Crypted password encoded in base64. To be set for the user USERNAME. If not defined it will change root user. You can use the following command:
			*: openssl passwd -1 \| base64

			* '''PASSWORD_BASE64''' - Password encoded in base64. To be set for the user USERNAME.

			* '''CRYPTED_PASSWORD''' - Crypted password. To be set for the user USERNAME. This parameter is not recommended, use CRYPTED_PASSWORD_BASE64 instead. You can use the following command:
			*: openssl passwd -1

			* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.

			The following attributes are automatically filled up configuring the network and context section of the template:
	* '''ETHx_MAC''' - Used to find the correct interface		* '''ETHx_MAC''' - Used to find the correct interface

Line 63:		Line 77:

	* '''ETHx_DNS''' - DNS for the network		* '''ETHx_DNS''' - DNS for the network

	* '''USERNAME''' - User to be created in the guest OS. If any password attribute is defined (see below) it will change this user (defaults to root). '''Please note:''' SSH daemon on the host is configured to deny access to user '''root''' and it does not support password authentication. If you specify '''USERNAME''' such account will be created and any SSH keys you may have configured will be allowed to login as that user. If you use any of the context variables below then password will be set for the user too. If username is not root you will be able to SSH in using SSH key and you will be able to login on the VNC console but you will '''not be able escalate your privileges''' to root. If username is '''root''' or you do not use '''USERNAME''' then you will be able to login on the VNC console but you will not be able to SSH in. '''Contextualization script always creates an user ''cloudUser'' which is allowed to login SSH using the keys you have configured in the template. Also cloudUser is allowed to elevate its privileges via sudo without password. the following command will make you root without password:'''
	*: sudo -s

	* '''CRYPTED_PASSWORD_BASE64''' - Crypted password encoded in base64. To be set for the user USERNAME. If not defined it will change root user. You can use the following command:
	*: openssl passwd -1 \| base64

	* '''PASSWORD_BASE64''' - Password encoded in base64. To be set for the user USERNAME.

	* '''CRYPTED_PASSWORD''' - Crypted password. To be set for the user USERNAME. This parameter is not recommended, use CRYPTED_PASSWORD_BASE64 instead. You can use the following command:
	*: openssl passwd -1

	* '''PASSWORD''' - Password to be set for the user USERNAME. This parameter is not recommended, use PASSWORD_BASE64 instead.

	* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.		* '''SSH_PUBLIC_KEY''' - Key to be added to USERNAME authorized_keys file or root in case USERNAME is not set.

	* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY		* '''EC2_PUBLIC_KEY''' - Same as SSH_PUBLIC_KEY