Invalid shell - Revision history

Ninereasons at 16:19, 16 June 2006

2006-06-16T16:19:00Z

Ninereasons: syntax

2006-06-07T21:41:32Z

syntax

Ninereasons: another oops

2006-06-07T20:29:24Z

another oops

Ninereasons: paren

2006-06-07T20:26:32Z

paren

Ninereasons: invalid vs non-standard

2006-06-07T19:43:58Z

invalid vs non-standard

Dave at 07:18, 24 December 2004

2004-12-24T07:18:11Z

Dave at 06:01, 3 October 2004

2004-10-03T06:01:20Z

New page

A shell that won't let you login, either intentionally or not. [[/sbin/nologin]] is one, [[/bin/false]] is another.

[[Category: Shells]]

← Older revision		Revision as of 16:19, 16 June 2006
Line 1:		Line 1:
−	An '''invalid [[shell]]''' is a path in the account database's ''login shell path'' field to a file that does not exist, cannot be executed for login or, if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell. It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port. Oops. What if <code>bash</code> is not located on your boot partition, and <code>/usr/local/bin</code> fails to mount? Oops again.	+	An '''invalid [[shell]]''' is a path in the account database's ''login shell path'' field to a file that does not exist or, cannot be executed for login or, if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell. It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port. Oops. What if <code>bash</code> is not located on your boot partition, and <code>/usr/local/bin</code> fails to mount? Oops again.

	This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' (/[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:		This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' (/[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:

← Older revision		Revision as of 21:41, 7 June 2006
Line 1:		Line 1:
−	An '''invalid [[shell]]''' is a path ~~to a program~~ in the account database's ''login shell path'' field that does not exist, cannot be executed for login, or if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell. It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port. Oops. What if <code>bash</code> is not located on your boot partition, and <code>/usr/local/bin</code> fails to mount? Oops again.	+	An '''invalid [[shell]]''' is a path in the account database's ''login shell path'' field to a file that does not exist, cannot be executed for login or, if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell. It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port. Oops. What if <code>bash</code> is not located on your boot partition, and <code>/usr/local/bin</code> fails to mount? Oops again.

	This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' (/[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:		This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' (/[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:

← Older revision		Revision as of 20:29, 7 June 2006
Line 1:		Line 1:
−	An '''invalid [[shell]]''' is a path to a program in the account database's ''login shell path'' field that does not exist, cannot be executed for login, or if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell. It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port. Oops.	+	An '''invalid [[shell]]''' is a path to a program in the account database's ''login shell path'' field that does not exist, cannot be executed for login, or if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell. It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port. Oops. What if <code>bash</code> is not located on your boot partition, and <code>/usr/local/bin</code> fails to mount? Oops again.

	This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' (/[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:		This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' (/[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:

@@ Line 1: / Line 1: @@
 An '''invalid [[shell]]''' is a path to a program in the account database's ''login shell path'' field that does not exist, cannot be executed for login, or if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell.  It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port.  Oops.
-This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' /[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:
+This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' (/[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:
   %chsh -s /sbin/nologin

← Older revision		Revision as of 19:43, 7 June 2006
Line 1:		Line 1:
−	A shell ~~that won~~'~~t let you~~ login, ~~either intentionally~~ or not. [[ /sbin/nologin]] is ~~one~~, [[ /bin/false]] is another.	+	An '''invalid [[shell]]''' is a path to a program in the account database's ''login shell path'' field that does not exist, cannot be executed for login, or if executed does not provide a shell. [[ /sbin/nologin]] is an invalid shell, and [[ /bin/false]] is another, both of which are program paths that <code>root</code> can use to ''intentionally'' disable shell access for the user to which they are assigned as the login shell. It is a valid reason to be distressed if you somehow manage to ''unintentionally'' assign an invalid shell to <code>root</code>, which can be done as easily as, for example, assigning <code>/usr/local/bin/bash</code> as the root user's login shell, and then deleting that port. Oops.
		+
		+	This isn't quite the same thing as a ''non-standard shell'' - which can include any valid shell, the path of which is not listed in the ''shell database'' /[[etc/shells]]). A non-root user cannot assign itself a shell that does not exist in the shell database; or, the message will return:
		+
		+	%chsh -s /sbin/nologin
		+	chsh: /sbin/nologin: non-standard shell
		+
		+	Obviously, you don't want an invalid shell to be listed in the database of standard shells (<code>/etc/shells</code>).

	[[Category: Shells]]		[[Category: Shells]]

← Older revision		Revision as of 07:18, 24 December 2004
Line 1:		Line 1:
−	A shell that won't let you login, either intentionally or not. [[/sbin/nologin]] is one, [[/bin/false]] is another.	+	A shell that won't let you login, either intentionally or not. [[ /sbin/nologin]] is one, [[ /bin/false]] is another.

	[[Category: Shells]]		[[Category: Shells]]