07-22-2010
When we run ssh -v it looks like it gets a connection then when it goes into autentication mode it asks for public key and the authentication method disables and goes through keyboard-interactive authentication mode then onto password authentication mode where it finally asks for a password to connect. I don't understand why the public key authentication mode is not working. We recently made some updates to the server. I believe the problem lies on the remote server as the home server can connect to other servers with no problem. What are some files I could check to see if they may have gotten corrupted or lost?
10 More Discussions You Might Find Interesting
1. Cybersecurity
Eh... yeah. What the title says. :D (1 Reply)
Discussion started by: PSC
1 Replies
2. AIX
Guy's
I have AIX 6.1 SSH in it is not working but is up and Active .....
server1/etc>lssrc -s sshd
Subsystem Group PID Status
sshd ssh 450686 active
from my PC can I login by SSH but SSH from Server1 to Server2 is not accepting it's giving me this message
server1/etc>ssh sever2... (4 Replies)
Discussion started by: ITHelper
4 Replies
3. 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
4. Solaris
Hi, This is a strange issue: We have an sftp server. Users can ssh to it from internal LAN without any issue, but they can not ssh to it externally via firewall. Here is what I got:
OS is Solaris 9. No hosts.allow and hosts.deny files.
Please help. Thank you in advance! (7 Replies)
Discussion started by: aixlover
7 Replies
5. UNIX for Dummies Questions & Answers
I'm trying to setup a link between my home pc (work-machine) and a server at work (tar-machine) that is behind a gateway (hop-machine) and not directly accessible.
my actions:
work-machine$ ssh -L 1234:tar-machine:22 hop-machine
work-machine$ ssh -p 1234 user@127.0.0.1
- shh access on... (1 Reply)
Discussion started by: Vathau
1 Replies
6. Red Hat
Hi,
I have a server running RHEL 6.0.
While logging in through root ,I can login.But if I try to login through "integ" user,I am unable to login.
/var/log/secure messages:::
May 20 15:25:23 punsyncserv su: pam_unix(su-l:session): session opened for user integ by root(uid=0)
May 20 15:29:44... (4 Replies)
Discussion started by: nowornever
4 Replies
7. Shell Programming and Scripting
I am trying to connect to Windows server via Linux server through a script and run two commands " cd and ls " But its giving me error saying " could not start the program" followed by the command name i specify e g : "cd"
i am trying in this manner "
ssh username@servername "cd... (5 Replies)
Discussion started by: sunil seelam
5 Replies
8. UNIX for Dummies Questions & Answers
Hello,
I tried ssh in debug mode and below is the debug snippet.ssh to a host is not working from any of the hosts
No credentials cache found
debug1: Miscellaneous failure
No credentials cache found
debug1: Next authentication method: publickey
debug1: Offering RSA public key:... (7 Replies)
Discussion started by: Vishal_dba
7 Replies
9. Shell Programming and Scripting
Team,
Presently I have 5 ip address kept in ip_abc1 file, for each of the ip address listed, i need to login on each ipaddress
one at a time and login as below for that specific ip address
ssh -p 8101 karaf@<ip.address_for the specific ip address as logged in>
password
features:list... (4 Replies)
Discussion started by: whizkidash
4 Replies
10. AIX
Hi
I'd like to ssh from an AIX OS server ( v5.3) to a Fabric OS server ( v6.1.2 ) without password.
I tried using dsa or rsa keys but it didn't work, the aix server still asked for the password.
Somebody help, please :(:(:( (8 Replies)
Discussion started by: bobochacha29
8 Replies
AUTH(8) System Manager's Manual AUTH(8)
NAME
changeuser, wrkey, convkeys, printnetkey, status, auth.srv, guard.srv - maintain authentication databases
SYNOPSIS
auth/changeuser [-np] user
auth/wrkey
auth/convkeys [-p] keyfile
auth/printnetkey user
auth/status user
auth/auth.srv
auth/guard.srv
DESCRIPTION
These administrative commands run only on the authentication server. Changeuser manipulates an authentication database file system served
by keyfs(4) and used by file servers. There are two authentication databases, one holding information about Plan 9 accounts and one hold-
ing SecureNet keys. A user need not be installed in both databases but must be installed in the Plan 9 database to connect to a Plan 9
service.
Changeuser installs or changes user in an authentication database. It does not install a user on a Plan 9 file server; see fs(8) for that.
Option -p installs user in the Plan 9 database. Changeuser asks twice for a password for the new user. If the responses do not match or
the password is too easy to guess the user is not installed.
Option -n installs user in the SecureNet database and prints out a key for the SecureNet box. The key is chosen by changeuser.
If neither option -p or option -n is given, changeuser installs the user in the Plan 9 database.
Changeuser prompts for biographical information such as email address, user name, sponsor and department number and appends it to the file
/adm/netkeys.who or /adm/keys.who.
Wrkey prompts for a machine key, host owner, and host domain and stores them in local non-volatile RAM.
Convkeys re-encrypts the key file keyfile. Re-encryption is performed in place. Without the -p option convkeys uses the key stored in
/dev/keys to decrypt the file, and encrypts it using the new key. By default, convkeys prompts twice for the new password. The -p forces
convkeys to also prompt for the old password. The format of keyfile is described in keyfs(4).
Printnetkey displays the network key as it should be entered into the hand-held Securenet box.
Status is a shell script that prints out everything known about a user and the user's key status.
Auth.srv is the program, run only on the authentication server, that handles ticket requests on IL port 566. It is started by an incoming
call to the server requesting a conversation ticket; its standard input and output are the network connection. Auth.srv executes the
authentication server's end of the appropriate protocol as described in auth(6).
Guard.srv is similar. It is called whenever a foreign (e.g. Unix) system wants to do a SecureNet challenge/response authentication.
FILES
/adm/keys.who
List of users in the Plan 9 database.
/adm/netkeys.who
List of users in the SecureNet database.
SOURCE
/sys/src/cmd/auth
SEE ALSO
keyfs(4), securenet(8)
AUTH(8)