12-12-2011
Quote:
Originally Posted by
DGPickett
I read that the keys need to be generated with no password, as well, else you get prompted for that (which is more secure than simple password, I guess).
I think the idea for that is keys with passwords can be held by ssh-agent... enter the password once, use the key many times.
10 More Discussions You Might Find Interesting
1. Red Hat
I setup the keys between 2 servers, but my user account has no password specified for it (never set one up on the account for security reasons). When I try to SSH to the server, SSH prompts for a password that doesn't exist (so I can never connect successfully).
Note: 'passwd -d Rynok' removes... (3 Replies)
Discussion started by: Rynok
3 Replies
2. UNIX for Dummies Questions & Answers
I have 3 Solaris 10 UNIX servers, the shadow and passwd file are all identical and are automatically sync every 5 minutes. A majority of the users do not have CLI access but rather use a menu. I currently have menu options that allows them to rlogin to another server and I need to have the... (1 Reply)
Discussion started by: creedonjm
1 Replies
3. Solaris
Hi,
I am using DSEE 6.3 to authenticate and authorize my Solaris 9 and 10 users. Everything works fine except password expiration. I use built-in global password policy for all users. The policy works well. However I could not find the right pam configuration in order to prompt users at ssh... (2 Replies)
Discussion started by: niyazi
2 Replies
4. Programming
Hello forum,
I want to have a function to test for passwordless SSH setup. Pretty simple. However, what I'm finding difficult is to NOT return a password prompt to screen IF it's not in place.
Here's the function:
check_passwordless_ssh_working()
#check passed parameter, assuming it is... (4 Replies)
Discussion started by: doonan_79
4 Replies
5. UNIX for Dummies Questions & Answers
Hi!
Im trying to set access from ServerA(SunOS) to ServerB(Some custom Linux with Keyboard Interactive login) with SSH Keys. As a proof of concept I was able to do it between 2 virtual machines. Now in my real life scenario it isnt working.
I created the keys in ServerA, copied them to... (7 Replies)
Discussion started by: RedSpyder
7 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I'm trying to perform these operations without entering any password, as user "fzd":fzd@machine1> scp /tmp/srcFile1 fzd@machine2:/tmp/$destFile
fzd@machine1> scp fzd@machine2:/tmp/$srcFile /tmp/$destFilebut alsofzd@machine1> scp /tmp/srcFile1 machine2:/tmp/$destFile
fzd@machine1> scp... (6 Replies)
Discussion started by: fzd
6 Replies
7. SuSE
We are having an issue with slow password prompts via SSH login on all of our SLES 11.2 boxes. The output from a ssh -v login attempt shows a delay here:
debug1: SSH2_MSG_SERVICE_ACCEPT receivedThis issue only happens on the first logon of the day; subsequent logons are normal. Adding the client's... (8 Replies)
Discussion started by: j_aix
8 Replies
8. Red Hat
I am not sure what I am missing here. I have the following identical entry in /etc/sudoers on multiple Red Hat 6.4 servers.
icinga ALL=NOPASSWD:/usr/bin/yum --security --exclude\="kernel*" check-update
On one server when I enter the command over SSH as follows it works fine.
ssh -t -q... (1 Reply)
Discussion started by: scotbuff
1 Replies
9. Linux
Recently I have been playing with password ageing and the usage of ssh keys. I have found that if usePAM yes (default) is set in the /etc/ssh/sshd_config file then any password ageing and inactiivity can adversely affect a client with ssh keys.
For example:
Set PASS_MAX_DAYS to 60 in... (5 Replies)
Discussion started by: smurphy_it
5 Replies
10. UNIX for Beginners Questions & Answers
Hi gurus,
I am NOT the SA of the servers so very limited on what I can do. Basically the scenario is like this:
Every 6 months our password expires and we have to reset them to comply to some password rules. Thing is users, me included, tend to have plaintext copy of this difficult to... (2 Replies)
Discussion started by: newbie_01
2 Replies
LEARN ABOUT FREEBSD
ssh-copy-id
SSH-COPY-ID(1) BSD General Commands Manual SSH-COPY-ID(1)
NAME
ssh-copy-id -- copy public keys to a remote host
SYNOPSIS
ssh-copy-id [-lv] [-i keyfile] [-o option] [-p port] [user@]hostname
DESCRIPTION
The ssh-copy-id utility copies public keys to a remote host's ~/.ssh/authorized_keys file (creating the file and directory, if required).
The following options are available:
-i file
Copy the public key contained in file. This option can be specified multiple times and can be combined with the -l option. If a
private key is specified and a public key is found then the public key will be used.
-l Copy the keys currently held by ssh-agent(1). This is the default if the -i option was not specified.
-o ssh-option
Pass this option directly to ssh(1). This option can be specified multiple times.
-p port
Connect to the specified port on the remote host instead of the default.
-v Pass -v to ssh(1).
The remaining arguments are a list of remote hosts to connect to, each one optionally qualified by a user name.
EXIT STATUS
The ssh-copy-id utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
To send a specific key to multiple hosts:
$ ssh-copy-id -i /path/to/keyfile.pub user@host1 user@host2 user@host3
HISTORY
The ssh-copy-id utility was written by Eitan Adler <eadler@FreeBSD.org> as a drop-in replacement for an existing utility included with
OpenSSH.
BSD
February 28, 2014 BSD