11-05-2019
Bash reads different initialization files depending on whether it is interactive and whether it is a login shell. When you log in by hand and type pgp you will be in an interactive login shell. When you provide commands on the ssh command line you are switching to a non-interactive shell. The PATH to pgp is probably set up in one of the initialization files that is only read by interactive shells. The simplest fix would be to specify the full path to pgp. Alternatively try sourcing the files that bash loads automatically when started interactively.
10 More Discussions You Might Find Interesting
1. AIX
hello
I want to connect from server1 to server2 (Aix 5.3) with ssh, without password prompt.
So i define a ssh-key
On server1:
ssh-keygen -b 1024 -f identity -P '' -t dsa
scp identity.pub toto@server2:/tmp/identity-.pub
On server 2:
cat identity-.pub >> .ssh/authorized_keys
chmod 400... (2 Replies)
Discussion started by: pascalbout
2 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I have got a Solaris machine and I have several user account setup up with the .ssh and authorized_keys file in their home directories.
I have check all the permission and ownership and they are all indentical and belongs to the user ID and group respectively. However one of the... (3 Replies)
Discussion started by: stancwong
3 Replies
3. Cybersecurity
Hi,
When logging in using SSH access (to a remotely
hosted account), I received a prompt to accept
a server's key fingerprint. Wrote that string
of code down for comparision.
Already emailed my host for their listing of the
string of code for the server's key fingerprint
(for comparison,... (1 Reply)
Discussion started by: Texan
1 Replies
4. UNIX for Advanced & Expert Users
When should one have to generate a public key on a Server when the public key is already created and used by other clients?
Thanks,
Rahul. (6 Replies)
Discussion started by: rahulrathod
6 Replies
5. UNIX for Advanced & Expert Users
Hi all,
I have a sshkey which I use to connect from my unix box to a linux box without any issue......
however I downloaded this same key to my laptop and tried to connect to the same linux box but it failed.....
As my laptop is running MS Vista I guessing I going have to convert it ...... (1 Reply)
Discussion started by: Zak
1 Replies
6. Cybersecurity
Hello here is what I've seen
inside some public pgp keys.
gAIAAAAAAAkBAAAAAAoAAAAFAAoArwFI/gkAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA... (1 Reply)
Discussion started by: morten44
1 Replies
7. Shell Programming and Scripting
Hi,
I want to use ssh to add a register key on remote ssh server. Since there are space characters in my register key string, it always failed. If there is no space characters in the string, it worked fine. The following is what I have tried. It seems that "ssh" command doesn't care about double... (9 Replies)
Discussion started by: leaftree
9 Replies
8. Solaris
Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks.
... (1 Reply)
Discussion started by: aixlover
1 Replies
9. UNIX for Dummies Questions & Answers
Hello,
i was talking to an expert in my work and i requested him to import my ssh public-key in the ~/.ssh/authorized_keys on a remote host.
but he told me that he only import OS groupkey(not OS user key). so he asked me to give him the output of (id -a)
user1@hostname$ id -a... (3 Replies)
Discussion started by: amr.emam
3 Replies
10. AIX
Hello
I have AIX server as a source server and destination is Linux server. I have configured the ssh key as below....
generated rsa key on aix with userA and copied the public key to
on linux server in userB/.ssh/authorized_keys
but when i try ssh userB@linux server its again asks me for... (4 Replies)
Discussion started by: powerAIX
4 Replies
LEARN ABOUT XFREE86
git-shell
GIT-SHELL(1) Git Manual GIT-SHELL(1)
NAME
git-shell - Restricted login shell for Git-only SSH access
SYNOPSIS
chsh -s $(command -v git-shell) <user>
git clone <user>@localhost:/path/to/repo.git
ssh <user>@localhost
DESCRIPTION
This is a login shell for SSH accounts to provide restricted Git access. It permits execution only of server-side Git commands implementing
the pull/push functionality, plus custom commands present in a subdirectory named git-shell-commands in the user's home directory.
COMMANDS
git shell accepts the following commands after the -c option:
git receive-pack <argument>, git upload-pack <argument>, git upload-archive <argument>
Call the corresponding server-side command to support the client's git push, git fetch, or git archive --remote request.
cvs server
Imitate a CVS server. See git-cvsserver(1).
If a ~/git-shell-commands directory is present, git shell will also handle other, custom commands by running "git-shell-commands/<command>
<arguments>" from the user's home directory.
INTERACTIVE USE
By default, the commands above can be executed only with the -c option; the shell is not interactive.
If a ~/git-shell-commands directory is present, git shell can also be run interactively (with no arguments). If a help command is present
in the git-shell-commands directory, it is run to provide the user with an overview of allowed actions. Then a "git> " prompt is presented
at which one can enter any of the commands from the git-shell-commands directory, or exit to close the connection.
Generally this mode is used as an administrative interface to allow users to list repositories they have access to, create, delete, or
rename repositories, or change repository descriptions and permissions.
If a no-interactive-login command exists, then it is run and the interactive shell is aborted.
EXAMPLE
To disable interactive logins, displaying a greeting instead:
$ chsh -s /usr/bin/git-shell
$ mkdir $HOME/git-shell-commands
$ cat >$HOME/git-shell-commands/no-interactive-login <<EOF
#!/bin/sh
printf '%s
' "Hi $USER! You've successfully authenticated, but I do not"
printf '%s
' "provide interactive shell access."
exit 128
EOF
$ chmod +x $HOME/git-shell-commands/no-interactive-login
To enable git-cvsserver access (which should generally have the no-interactive-login example above as a prerequisite, as creating the
git-shell-commands directory allows interactive logins):
$ cat >$HOME/git-shell-commands/cvs <<EOF
if ! test $# = 1 && test "$1" = "server"
then
echo >&2 "git-cvsserver only handles "server""
exit 1
fi
exec git cvsserver server
EOF
$ chmod +x $HOME/git-shell-commands/cvs
SEE ALSO
ssh(1), git-daemon(1), contrib/git-shell-commands/README
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-SHELL(1)