2 Replies Latest reply: Nov 2, 2013 6:45 PM by neoform
neoform Level 1 (0 points)



Something happened yesterday on my terminal. I was using it without issue via remote login (SSH), then an hour later when i logged in it saw this:


Screen Shot 2013-11-02 at 11.44.57 AM.png


I thought it was weird since I wasn't loggin in as root, just my regular user.


I then went over to the computer in question and opened a terminal, and saw this:

Screen Shot 2013-11-02 at 11.28.30 AM.png

It's requiring a password as soon as I open the terminal...


I am using Server.app on the machine, could this be the cause? I've never seen this sort of error before. It seems to think my user account is root?

Mac mini, OS X Mavericks (10.9)
  • MrHoffman Level 6 (14,000 points)

    The usual trigger for these sorts of Terminal.app environment oddities is something weird in the local login scripts.


    See here and here for some related details on login scripts, if you're not familiar with that part of bash.


    Some add-on tools can modify these bash scripts and sometimes without the user realizing it.  (Errors related to PATH are one of the more common symptoms here, but all sorts of weirdness is possible.)


    Usual suggestion is to see if a different login works (different user), and also to rename (mv) the usual login files away from their standard names to disable them, and closing and restarting Terminal.app.


    In general and FWIW, you should not be logging in as root.  At all.  That's something that Apple has been discouraging for a while now.


    Server.app should not be modifying the login scripts.

  • neoform Level 1 (0 points)

    Very unusually, the issue turns out to have been the ~/.ssh/authorized_keys file I created.


    The permissions on the file were 644 and not 600....  somehow that was the cause of the problem. Weird.