Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 02 Aug 2014 18:56:29 -0500
From:      "William A. Mahaffey III" <wam@hiwaay.net>
To:        "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
Subject:   Re: permission problems w/ ordinary user ....
Message-ID:  <53DD7AAD.4000902@hiwaay.net>
In-Reply-To: <20140803014039.75f4b2f9.freebsd@edvax.de>
References:  <53DD742F.3020408@hiwaay.net> <20140803014039.75f4b2f9.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 08/02/14 18:40, Polytropon wrote:
> On Sat, 02 Aug 2014 18:28:47 -0500, William A. Mahaffey III wrote:
>> .... I have been trying to setup the regular user (me, non-root) on my
>> newly minted FreeBSD 9.3 box. I tried su-ing from tooy & ssh-ing in as
>> me from another box, both give weird results, see the following from my
>> syslog:
>>
>> [...]
>> Aug  2 18:23:01 kabini1 sshd[1252]: _secure_path: cannot stat
>> /home/wam/.login_conf: Permission denied
>>
>>
>> also, the home-directory keeps getting the 'x' permission bit set to off
>> by .... something ....
> I think you have described the reason for the problem:
> The x attribute for a directory means "enter and search"
> and should be _set_ for the user. If it's not, the user
> cannot enter his own home directory or access files
> within it. In this case, /home/wam/.login_conf cannot
> be read which seems to be neccessary for the login
> process.
>
> You need to find that "something" that created or altered
> /home/wam with the x attribute off. Login as root and
> correct the setting manually, so you should be able to
> login afterwards.
>
> This is how the resulting "ls -l /home" output it should
> look like for your user:
>
> 	drwx------  [...] wam     wam     [...] wam/
> 	   ^
>
> (This is minimum permissions; drwxrwxr-x or drwxr-x---
> are other common examples.)
>
> How did you introduce the user to the system? Did you
> use "adduser" or "pw add"?

I used useradd as root, & the permissions were set correctly to begin 
with. I suspect that the failed logins are triggering the reset, but w/ 
little proof .... I have reset the perms as root several times during 
this exercise, & they keep getting unset after the login failure ....

-- 

	William A. Mahaffey III

  ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                            -- Gen. George S. Patton Jr.




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?53DD7AAD.4000902>