Migrating to ssh key authentication; implications of adding sbin's to users $PATH
Posted
by
ancillary
on Server Fault
See other posts from Server Fault
or by ancillary
Published on 2012-03-22T17:03:01Z
Indexed on
2012/03/22
17:32 UTC
Read the original article
Hit count: 213
I'm in the process of migrating to key's for authentication on my CentOS boxes. I have it all set up and working, but was a bit taken aback when I noticed service
(and other things) didn't work the way I was accustomed to. Even after su
'ing to root, still had to call the full path for it to work (which I assume to be expected/normal behavior).
I also assume this is because there are different $PATH
's for root (what I was using and am used to) and the newly created, key-using user. Specifically, I noticed the sbin
's of the world missing from the user path.
If I were to add those paths (/sbin/
,/usr/sbin/
,/usr/local/sbin
) to a profile.d
.sh
script for this new key-loving user, would:
- I be opening up the system in ways I shouldn't be?
- I be doing something I needn't do save for reasons of laziness?
- I create other potential problems?
Thanks.
© Server Fault or respective owner