06-01-2008
Created the keys in host1, while logged in as root & then copied the public key to host2
From host1, initially did
ssh host2 - which worked fine
now,
ssh user2@host2 - prompts for password
In public key it contains root@host1 - which is fine. Coz, am always logged as root in host1 - so no need to change
Not sure how to proceed :-(
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi there
Probably a really simple question but I am writing an install script and at certain stages of the install (ie creating a table in mysql) the system prompts for you to enter a password, I was wondering, how do I script this input so that the install doesnt keep stopping for manual... (3 Replies)
Discussion started by: hcclnoodles
3 Replies
2. UNIX for Advanced & Expert Users
I would like to log all the commands that are entered on an ssh client. I can do this successfully, however, I dont want to log user logins and passwords. Is there any way to identify passwords and avoid them? For example, I can look for a string 'password:' and ignore everything until a nl/cr. Is... (2 Replies)
Discussion started by: balag
2 Replies
3. UNIX for Dummies Questions & Answers
How can I know users have changed their passwords ? I don't need their password (!) I have to know if they have changed their pass word and when ?
Thank you in advance for any SIMPLE answer. (6 Replies)
Discussion started by: annemar
6 Replies
4. Solaris
Hi Gurus
I have a few Sol 5.9 servers and i have enabled password less authentication between them for my user ID. Often i have found that when my password has expired,the login fails.
Resetting my password reenables the keys.
Do i need to do something to avoid this scenario or is this... (2 Replies)
Discussion started by: Renjesh
2 Replies
5. 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
6. UNIX Desktop Questions & Answers
Hi there,
I'm working with a Linux server and now I can get a daily Logwatch mail ... my question is:since there are too many users with root password (...in my opinion... :mad:) how could I prevent to delete information about "su" log?
Thanks in advance,
GB (3 Replies)
Discussion started by: Giordano Bruno
3 Replies
7. AIX
Hi
I have experienced this for years and just put up with it. However a client of mine now wants to stop this happening to their users. I have scoured the internet but can find no reference to the problem. I tried switching to PAM authentication thinking this might help but it made no... (6 Replies)
Discussion started by: johnf
6 Replies
8. Shell Programming and Scripting
I am writing a BASH script to update a webserver and then restart Apache. It looks basically like this:
#!/bin/bash
rsync /path/on/local/machine/ foo.com:path/on/remote/machine/
ssh foo.com sudo /etc/init.d/apache2 reloadrsync and ssh don't prompt for a password, because I have DSA encryption... (9 Replies)
Discussion started by: fluoborate
9 Replies
9. Shell Programming and Scripting
Hi, I'm writing a script,
in the script I need to use tcpdump to capture some packets
however it needs root priviledge
my computer is configured by school and I have no real root priviledge
so I can't use sudo on my computer,like
Code:
sudo tcpdump ......
I have to use a limited... (1 Reply)
Discussion started by: esolve
1 Replies
10. Red Hat
Hello Experts,
when I am trying to connect my target server through sftp after creating ssh password less setup, it is asking for passowrd to connect.
to setup this I followed below process:
-->generated keys by executing the command "ssh-keygen -t rsa"
-->this created my .ssh directory... (9 Replies)
Discussion started by: Devipriya Ch
9 Replies
LEARN ABOUT CENTOS
passmass
PASSMASS(1) General Commands Manual PASSMASS(1)
NAME
passmass - change password on multiple machines
SYNOPSIS
passmass [ host1 host2 host3 ... ]
INTRODUCTION
Passmass changes a password on multiple machines. If you have accounts on several machines that do not share password databases, Passmass
can help you keep them all in sync. This, in turn, will make it easier to change them more frequently.
When Passmass runs, it asks you for the old and new passwords. (If you are changing root passwords and have equivalencing, the old pass-
word is not used and may be omitted.)
Passmass understands the "usual" conventions. Additional arguments may be used for tuning. They affect all hosts which follow until
another argument overrides it. For example, if you are known as "libes" on host1 and host2, but "don" on host3, you would say:
passmass host1 host2 -user don host3
Arguments are:
-user
User whose password will be changed. By default, the current user is used.
-rlogin
Use rlogin to access host. (default)
-slogin
Use slogin to access host.
-ssh
Use ssh to access host.
-telnet
Use telnet to access host.
-program
Next argument is a program to run to set the password. Default is "passwd". Other common choices are "yppasswd" and "set
passwd" (e.g., VMS hosts). A program name such as "password fred" can be used to create entries for new accounts (when run as
root).
-prompt
Next argument is a prompt suffix pattern. This allows the script to know when the shell is prompting. The default is "# " for
root and "% " for non-root accounts.
-timeout
Next argument is the number of seconds to wait for responses. Default is 30 but some systems can be much slower logging in.
-su
Next argument is 1 or 0. If 1, you are additionally prompted for a root password which is used to su after logging in. root's
password is changed rather than the user's. This is useful for hosts which do not allow root to log in.
HOW TO USE
The best way to run Passmass is to put the command in a one-line shell script or alias. Whenever you get a new account on a new machine,
add the appropriate arguments to the command. Then run it whenever you want to change your passwords on all the hosts.
CAVEATS
Using the same password on multiple hosts carries risks. In particular, if the password can be stolen, then all of your accounts are at
risk. Thus, you should not use Passmass in situations where your password is visible, such as across a network which hackers are known to
eavesdrop.
On the other hand, if you have enough accounts with different passwords, you may end up writing them down somewhere - and that can be a
security problem. Funny story: my college roommate had an 11"x13" piece of paper on which he had listed accounts and passwords all across
the Internet. This was several years worth of careful work and he carried it with him everywhere he went. Well one day, he forgot to
remove it from his jeans, and we found a perfectly blank sheet of paper when we took out the wash the following day!
SEE ALSO
"Exploring Expect: A Tcl-Based Toolkit for Automating Interactive Programs" by Don Libes, O'Reilly and Associates, January 1995.
AUTHOR
Don Libes, National Institute of Standards and Technology
7 October 1993 PASSMASS(1)