Adding users - Revision history

FabienM: /* Prevent login */

2013-10-11T07:48:35Z

Prevent login

← Older revision		Revision as of 09:48, 11 October 2013
Line 70:		Line 70:
	exit 0		exit 0
	</pre>		</pre>

			== Links ==

			* [[How to set the default root password]]

JulienB: /* Make the change effective for all your future rootfs build */

2012-08-16T09:24:05Z

Make the change effective for all your future rootfs build

← Older revision		Revision as of 11:24, 16 August 2012
Line 49:		Line 49:
	$ mkdir -p buildroot/target/device/armadeus/rootfs/target_skeleton/home/guest		$ mkdir -p buildroot/target/device/armadeus/rootfs/target_skeleton/home/guest
	</pre>		</pre>
	* Now each time you will build your rootfs you will have the new user account active		* Now each time you will build your rootfs '''from scratch''', you will have the new user account active.
			* If your rootfs was already built, you will also have to temporary copy the files in ''buildroot/output/target/''.
			* In recent armadeus versions (5.0 for example), you can also modify ''buildroot/target/device/armadeus/rootfs/post-build.sh'' to do all these operations automatically.

	==Already created users==		==Already created users==

JulienB: /* Make the change effective for all your future rootfs build */

2009-11-25T15:12:25Z

Make the change effective for all your future rootfs build

← Older revision		Revision as of 17:12, 25 November 2009
Line 50:		Line 50:
	</pre>		</pre>
	* Now each time you will build your rootfs you will have the new user account active		* Now each time you will build your rootfs you will have the new user account active

			==Already created users==
			* by default Buildroot sets up some common users. To see them:
			<pre class="apf">
			# cat /etc/passwd
			</pre>

			==Prevent login==
			* When you create a user, he's by default allowed to login to your system and so allowed to use telnet and/or ssh. If you don't want some users to login (ex: users used by daemons), you can do the following:
			** when creating an account use ''adduser guest -s /sbin/nologin''
			** if user was already created, then edit ''/etc/passwd'' and replace ''/bin/sh'' with ''/sbin/nologin'' at the end of the user entries
			** create ''/sbin/nologin'', put it the following content and don't forget to give it executables rights :
			<pre class="apf">
			#!/bin/sh

			echo "User $USER is not allowed to login"
			exit 0
			</pre>

JulienB: /* Create user account */

2009-11-25T14:45:26Z

Create user account

← Older revision		Revision as of 16:45, 25 November 2009
Line 4:		Line 4:

	==Create user account==		==Create user account==
	* ~~Use~~ the ''adduser'' command (here the new user is named ''guest''):		* As root, use the ''adduser'' command (here the new user is named ''guest''):
	<pre class="apf">		<pre class="apf">
	# adduser guest		# adduser guest

JulienB: /* Make the change effective for all your future rootfs build */

2009-10-01T16:01:51Z

Make the change effective for all your future rootfs build

← Older revision		Revision as of 18:01, 1 October 2009
Line 40:		Line 40:
	* Copy the transfered files (assuming your [[Communicate#TFTP_server\|TFTP]] points to ''/tftpboot/'') to your Buildroot's rootfs skeleton:		* Copy the transfered files (assuming your [[Communicate#TFTP_server\|TFTP]] points to ''/tftpboot/'') to your Buildroot's rootfs skeleton:
	<pre class="host">		<pre class="host">
	$ ~~source armadeus_env.sh~~		$ sudo chown $USER:$USER /tftpboot/shadow
			$ sudo chown $USER:$USER /tftpboot/passwd
	$ cp /tftpboot/passwd buildroot/target/device/armadeus/rootfs/target_skeleton/etc/		$ cp /tftpboot/passwd buildroot/target/device/armadeus/rootfs/target_skeleton/etc/
	$ cp /tftpboot/shadow buildroot/target/device/armadeus/rootfs/target_skeleton/etc/		$ cp /tftpboot/shadow buildroot/target/device/armadeus/rootfs/target_skeleton/etc/

JulienB: /* Make the change effective for all your future rootfs build */

2009-10-01T15:40:50Z

Make the change effective for all your future rootfs build

← Older revision		Revision as of 17:40, 1 October 2009
Line 33:		Line 33:

	==Make the change effective for all your future rootfs build==		==Make the change effective for all your future rootfs build==
	* Transfer ''/etc/passwd'' and ''/etc/shadow'' ~~for~~ your APF to your PC (here 192.168.0.2):		* Transfer ''/etc/passwd'' and ''/etc/shadow'' from your APF to your PC (here 192.168.0.2):
	<pre class="apf">		<pre class="apf">
	# tftp -p -l /etc/passwd 192.168.0.2		# tftp -p -l /etc/passwd -r passwd 192.168.0.2
	# tftp -p -l /etc/shadow 192.168.0.2		# tftp -p -l /etc/shadow -r shadow 192.168.0.2
	</pre>		</pre>
	* Copy the transfered files (assuming your [[Communicate#TFTP_server\|TFTP]] points to ''/tftpboot/'') to your Buildroot's rootfs skeleton:		* Copy the transfered files (assuming your [[Communicate#TFTP_server\|TFTP]] points to ''/tftpboot/'') to your Buildroot's rootfs skeleton:

JulienB: /* Changing password */

2009-10-01T15:37:25Z

Changing password

← Older revision		Revision as of 17:37, 1 October 2009
Line 20:		Line 20:
	Old password:		Old password:
	New password:		New password:
			Retype password:
			Password for guest changed by guest
	</pre>		</pre>
	* If logged as ''root'' you can change all other users password with:		* If logged as ''root'' you can change all other users password with:

JulienB: /* Make the change effective for all your future rootfs build */

2009-10-01T15:35:18Z

Make the change effective for all your future rootfs build

← Older revision		Revision as of 17:35, 1 October 2009
Line 41:		Line 41:
	$ cp /tftpboot/passwd buildroot/target/device/armadeus/rootfs/target_skeleton/etc/		$ cp /tftpboot/passwd buildroot/target/device/armadeus/rootfs/target_skeleton/etc/
	$ cp /tftpboot/shadow buildroot/target/device/armadeus/rootfs/target_skeleton/etc/		$ cp /tftpboot/shadow buildroot/target/device/armadeus/rootfs/target_skeleton/etc/
			</pre>
			* Create user's HOME directory (here ''/home/guest''):
			<pre class="host">
			$ mkdir -p buildroot/target/device/armadeus/rootfs/target_skeleton/home/guest
	</pre>		</pre>
	* Now each time you will build your rootfs you will have the new user account active		* Now each time you will build your rootfs you will have the new user account active

JulienB: /* Create user account */

2009-10-01T15:32:39Z

Create user account

@@ Line 7: / Line 7: @@
 <pre class="apf">
   # adduser guest
   Changing password for guest
   New password:

JulienB: creation

2009-10-01T14:25:58Z

creation

New page

It's not always a good idea to run all its embedded applications as ''root'' user or it may be mandatory to allow other users than ''root'' to remotly connect to an embedded system.

This page will explain you how to add new users on your board.

==Create user account==
* Use the ''adduser'' command (here the new user is named ''guest''):
<pre class="apf">
# adduser guest
Changing password for guest
New password:
Retype password:
Password for guest changed by root
</pre>

==Make the change effective for all your future rootfs build==
* Transfer ''/etc/passwd'' and ''/etc/shadow'' for your APF to your PC (here 192.168.0.2):
<pre class="apf">
# tftp -p -l /etc/passwd 192.168.0.2
# tftp -p -l /etc/shadow 192.168.0.2
</pre>
* Copy the transfered files (assuming your [[Communicate#TFTP_server|TFTP]] points to ''/tftpboot/'') to your Buildroot's rootfs skeleton:
<pre class="host">
$ source armadeus_env.sh
$ cp /tftpboot/passwd buildroot/target/device/armadeus/rootfs/target_skeleton/etc/
$ cp /tftpboot/shadow buildroot/target/device/armadeus/rootfs/target_skeleton/etc/
</pre>
* Now each time you will build your rootfs you will have the new user account active