11-03-2016
Why such limitations?
The idea of using secure shell suite is mosltly that: after having a secured ( crypted) connection, using keys so there is no more need of entering passwords...
The only other alternative is using a file in home directory but that would be seen by your admins as a security breach... ( my opinion is more temperate...)
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I like to copy a file from one server server1 from path path1 to another server server2 to path path2.
User logging in both the servers are same say user1
I tried to use ssh to generate public/private key pairs and then copy without prompting for password.
These are the steps i followed
... (5 Replies)
Discussion started by: jwala
5 Replies
2. UNIX for Advanced & Expert Users
Hi,
when I use scp test.jsp user@remote:/tmp/
I'm prompted user@remote's password:
How can I avoid it ?
Thank you. (8 Replies)
Discussion started by: big123456
8 Replies
3. Shell Programming and Scripting
hi
I tried reading some of the threads w.r.t scp/sftp file to another server in the same network without asking for password while copying files.....but couldnot succeed.
i have generated the public key for the system using "ssh-keygen -t " and kept it in the
.ssh/authorized_keys file.
... (8 Replies)
Discussion started by: aemunathan
8 Replies
4. UNIX for Dummies Questions & Answers
Hi guys,
I wasn't sure which thread to include this one in (unix or shell scripting) but chose here based on search results. I need to automate a process which requires the need to transfer a file from a machine running on NT to the database server on UNIX. I've found this and a number of other... (7 Replies)
Discussion started by: Dird
7 Replies
5. Red Hat
Hi,
I want to use sftp/scp without password.How can I do that ??
I plan to use script with scp/sftp and execute by cronjob ,any sample or example?? How can I test the scp/sftp working or not in the same user account , in the same red linux server?? any suggestion ??? (5 Replies)
Discussion started by: chuikingman
5 Replies
6. Shell Programming and Scripting
Hi Everyone,
I'm trying to run scp as a one-line command, as of right now, it prompts me for the user's password to the remote machine. Does anyone know if there is an option to pass the password parameter into the scp command on the same line so it doesn't prompt me? Thanks! (1 Reply)
Discussion started by: twhitmarsh
1 Replies
7. UNIX for Advanced & Expert Users
I am trying to copy a file from remote machine using scp. I followed the steps to configure public/private key usage. But still prompting for password when I do ssh.
I did the following steps to configure scp without asking password
Step 1 : local host > ssh-keygen -t rsa and when prompted... (9 Replies)
Discussion started by: satish@123
9 Replies
8. Linux
Dear all,
I have two servers A and B. I want to do scp with out password between these two servers.
I created ssh-keygen and copied the id-rsa.pub file to each of them in authorized_keys.
But I could login only from B to A with out password. From A to B it is asking for a password.
... (5 Replies)
Discussion started by: jegaraman
5 Replies
9. Shell Programming and Scripting
Hi,
I was provided with sftp servername, user and password and the requirement is to connect to sftp server using credentials provided and drop the file.
Manually i am able to connect with commands like
sftp user@servername
and after clicking enter, i was asked for a password and entering... (4 Replies)
Discussion started by: forums123456
4 Replies
10. Shell Programming and Scripting
Hello Folks,
I have two linux server accounts server1 and server2
From the terminal if I say this command,
scp /source/folder/from/server1/unix.txt user@server2.com:/destination/folder/
Then it prompts for the password
user@server2.com's password:
I enter my password and then it... (1 Reply)
Discussion started by: jacobs.smith
1 Replies
LEARN ABOUT REDHAT
passwd
PASSWD(5) File formats PASSWD(5)
NAME
passwd - password file
DESCRIPTION
Passwd is a text file, that contains a list of the system's accounts, giving for each account some useful information like user ID, group
ID, home directory, shell, etc. Often, it also contains the encrypted passwords for each account. It should have general read permission
(many utilities, like ls(1) use it to map user IDs to user names), but write access only for the superuser.
In the good old days there was no great problem with this general read permission. Everybody could read the encrypted passwords, but the
hardware was too slow to crack a well-chosen password, and moreover, the basic assumption used to be that of a friendly user-community.
These days many people run some version of the shadow password suite, where /etc/passwd has *'s instead of encrypted passwords, and the
encrypted passwords are in /etc/shadow which is readable by the superuser only.
Regardless of whether shadow passwords are used, many sysadmins use a star in the encrypted password field to make sure that this user can
not authenticate him- or herself using a password. (But see the Notes below.)
If you create a new login, first put a star in the password field, then use passwd(1) to set it.
There is one entry per line, and each line has the format:
account:password:UID:GID:GECOS:directory:shell
The field descriptions are:
account the name of the user on the system. It should not contain capital letters.
password the encrypted user password or a star.
UID the numerical user ID.
GID the numerical primary group ID for this user.
GECOS This field is optional and only used for informational purposes. Usually, it contains the full user name. GECOS means
General Electric Comprehensive Operating System, which has been renamed to GCOS when GE's large systems division was sold
to Honeywell. Dennis Ritchie has reported: "Sometimes we sent printer output or batch jobs to the GCOS machine. The gcos
field in the password file was a place to stash the information for the $IDENTcard. Not elegant."
directory the user's $HOME directory.
shell the program to run at login (if empty, use /bin/sh). If set to a non-existing executable, the user will be unable to
login through login(1).
NOTE
If you want to create user groups, their GIDs must be equal and there must be an entry in /etc/group, or no group will exist.
If the encrypted password is set to a star, the user will be unable to login using login(1), but may still login using rlogin(1), run
existing processes and initiate new ones through rsh(1), cron(1), at(1), or mail filters, etc. Trying to lock an account by simply chang-
ing the shell field yields the same result and additionally allows the use of su(1).
FILES
/etc/passwd
SEE ALSO
passwd(1), login(1), su(1), group(5), shadow(5)
1998-01-05 PASSWD(5)