03-22-2005
Never use .netrc files! Major risk, as you end up with unencrypted passwords stored in all users' home directories.
But regarding your question, the .netrc file should be in the directory that is the home directory for the user as specified in the /etc/passwd file (or returned by calls such as getpwent). The /home/<userid> directory is not necessarily <userid>'s home directory.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi, id like to ask a question about .netrc. Id like to have 2 entries for a particular machine, but with different ftp userid's ie
machine 172.19.8.26 login dcm password dcm
macdef job1
bin
hash
bye
machine 172.19.8.26 login ppp password ppp
macdef job2
bin
hash
bye
this code DOES... (8 Replies)
Discussion started by: hcclnoodles
8 Replies
2. UNIX for Dummies Questions & Answers
hello,
I am trying to write an automated script to transfer multiple files to another solaris 5.8 box. I am using the #! /bin/bash prompt and I am having trouble finding/creating the .netrc login file. I googled and the only info I got was that I should create/find it in my home directory. I went... (2 Replies)
Discussion started by: grandtheftander
2 Replies
3. UNIX for Dummies Questions & Answers
I had configured the .netrc file for automatic login to ftp
however i am not clear how to give the port no after the "machine" token:
as in, when i give
machine xyz.com 2121
login <usid>
password <pass>
i am getting the error Unknown .netrc keyword 2121 while giving the command ftp xyz.com... (1 Reply)
Discussion started by: jithinravi
1 Replies
4. UNIX for Advanced & Expert Users
Hi friends,
Can we use the file .netrc for automating ftp from a perl script ?
and if so then how do i go about it ?
can i have a sample script for this ?
thanks in advance
Veera (6 Replies)
Discussion started by: sveera
6 Replies
5. AIX
Hello all,
I am using a .netrc to automatically access an ftp host. Here is the line I use...
machine 412.blank.com login nw\mylogin password *******
when I use this command...
ftp 412.blank.com
I get...
Connected to 412.blank.com.
220 server_7 FTP server (EMC-SNAS: 5.5.25.2)... (4 Replies)
Discussion started by: magikalpnoi
4 Replies
6. UNIX for Dummies Questions & Answers
Hi this is about using .netrc with multiple macro definitions for a single target server. I have seen this done successfully before, but am having trouble getting it working here.
my .netrc file is like the following:
machine server1
login userid1
password userpwd1
macdef... (1 Reply)
Discussion started by: PSDba
1 Replies
7. Shell Programming and Scripting
So...
I'm trying to script and FTP Backup of some files from openVMS Alpha machine to a Unixware 7 machine.
I decided to use .netrc to do all the FTP actions however when I send the
nmap command. It pretty much gets ignored while even other things such "ascii", "case" etc.. get respected... (0 Replies)
Discussion started by: thesubmitter
0 Replies
8. Red Hat
What is the proper format for configuring the netrc file for linux. On Solaris it was:
Machine <machinename> login Domain\\login password passwordname (1 Reply)
Discussion started by: soupbone38
1 Replies
9. IP Networking
I have 2 different id's for an ftp destination. Each id handles files differently on the destinations end. Is it possible to have one destination machine and assign an alias name for each id. The .netrc file doesn't allow this. (2 Replies)
Discussion started by: wangotango
2 Replies
10. Shell Programming and Scripting
Am trying a shell script for ftp process on Solaris
I am trying to mget files to
Destination server: myserverxxx1
folder : /backup/dumps/SERVER-1backup/afterbatch
From
Source server: SERVER-1
folder : /dumps/daily/backupafterbatch/Thu21Oct_04:22:37
depending on the date the... (1 Reply)
Discussion started by: sunnyboy
1 Replies
LEARN ABOUT DEBIAN
qmail-pw2u
qmail-pw2u(8) System Manager's Manual qmail-pw2u(8)
NAME
qmail-pw2u - build address assignments from a passwd file
SYNOPSIS
qmail-pw2u [ -/ohHuUC ] [ -cchar ]
DESCRIPTION
qmail-pw2u reads a V7-format passwd file from standard input and prints a qmail-users-format assignment file.
A V7-format passwd file is a series of lines. Each line has the format
user:password:uid:gid:gecos:home:shell
where user is an account name, uid and gid are the user id and group id of that account, and home is the account's home directory. pass-
word, gecos, and shell are ignored by qmail-pw2u.
If you put the output of qmail-pw2u into /var/lib/qmail/users/assign, and then run qmail-newu, qmail-lspawn will obey the assignments
printed by qmail-pw2u. WARNING: After changing any users, uids, gids, or home directories in your passwd file, you must run qmail-pw2u and
qmail-newu again if you want qmail-lspawn to see the changes.
RULES
By default, qmail-pw2u follows the same rules as qmail-getpw. It skips user if (1) uid is zero, (2) home does not exist, (3) user does not
own home, or (4) user contains uppercase letters. It then gives each remaining user control over the basic user address and all addresses
of the form user-anything. A catch-all user, alias, controls all other addresses.
You may change these rules by setting up files in /var/lib/qmail/users:
include
Allowed users, one per line. If include exists, and user is not listed in include, user is ignored.
exclude
Ignored users, one per line. If exclude exists, and user is listed in exclude, user is ignored.
mailnames
Replacement names for users. Each line has the form
user:mailname1:mailname2:...
The addresses mailname1 and mailname1-ext and mailname2 and so on will be delivered to user.
WARNING: The addresses user and user-ext will not be delivered to user unless user is listed as one of the mailnames.
A line in mailnames is silently ignored if the user does not exist.
subusers
Extra addresses. Each line has the form
sub:user:pre:
sub will be handled by home/.qmail-pre, where home is user's home directory; sub-ext will be handled by home/.qmail-pre-ext.
append Extra assignments, printed at the end of qmail-pw2u's output.
OPTIONS
-o (Default.) Skip user if home does not exist (or is not visible to qmail-pw2u). Skip user if home is not owned by user.
-h Stop if home does not exist. This is appropriate if every user is supposed to have a home directory. Skip user if home is not
owned by user.
-H Do not check the existence or ownership of home.
-U (Default.) Skip user if there are any uppercase letters in user.
-u Allow uppercase letters in user.
-cchar Use char as the user-extension delimiter in place of -.
-C Disable the user-extension mechanism.
-/ Use home/.qmail-/... instead of home/.qmail-...
SEE ALSO
qmail-users(5), qmail-lspawn(8), qmail-newu(8), qmail-getpw(8)
qmail-pw2u(8)