32
7
Is there a way to bypass or prevent the execution of ~/.profile
when logging into a remote Linux server using either ssh or putty?
32
7
Is there a way to bypass or prevent the execution of ~/.profile
when logging into a remote Linux server using either ssh or putty?
31
For bash:
$ ssh hostname "bash --noprofile"
6You'll also need the -t
option, I think. – user1686 – 2009-09-29T13:22:17.997
2ssh -t hostname "bash --noprofile" .If -t wasn't there I was getting the error "standard in must be a tty". – nitins – 2013-06-25T12:01:42.740
14
If you are looking to disable all login scripts, you can use the --noprofile
flag to disable /etc/profile
, ~/.profile
, etc. and --norc
to disable ~/.bashrc
like so:
$ ssh 127.0.0.1 "bash --noprofile --norc"
Keep in mind you can also launch an alternative shell if one is available. I've had to use this after messing up in chsh
:
$ ssh 127.0.0.1 sh
This will most likely drop you to a blank shell (no prompt) so give it an ls
to make sure it is working.
4
If your target machine is in a bash shell:
user@host:/$ ssh hostname "bash --noprofile"
Alternatively, if there's another profile you wish to use
user@host:/$ ssh hostname "bash --noprofile; source ~/.other_profile"
1
Also, try using a FTP program like WinSCP to delete the mistaken login file. This will discard it, but at least you should be able to login to the default shell
or perhaps just rename it. – jezmck – 2013-05-15T14:32:24.003
1
As others have mentioned, running bash with the --noprofile
flag when you initiate the connection will work, although if you're using a different shell this may or may not be an option.
One alternative would be to have the profile script detect an SSH connection itself and behave accordingly. Since SSH connections will normally set a number of environment variables, this can easily be checked. Adding something like the following lines to the start of your profile should suffice:
if [ "$SSH_CONNECTION" != "" ]; then
echo Logging in with ssh
return
else
echo Logging in with something that is not ssh
fi
# rest of your profile goes here
The return
will skip the rest of the script if the $SSH_CONNECTION
environment variable is set, which would normally be created whenever an SSH connection is initiated. Otherwise the profile will be run like normal.
Note that this will only skip the affected profile script. All other profile scripts (e.g.: /etc/profile
) would still be processed unless you modify them similarly.
Why would you want to do this? Why not just edit the values in the file? (It's your profile, after all.) – Telemachus – 2009-09-28T19:52:02.607
7This is usefull for instance if someone screwed up the .profile file and you don't have direct access to the system :) – monkey_p – 2009-09-28T20:14:10.127
That's exactly the situation I found myself in monkey_p – Andrew Hampton – 2009-09-29T18:57:45.840