Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

cpasswd(1) [freebsd man page]

CPASSWD(1)						    BSD General Commands Manual 						CPASSWD(1)

NAME
cpasswd -- scramble passwords for csup authentication SYNOPSIS
cpasswd clientName serverName DESCRIPTION
The cpasswd utility creates scrambled passwords for the CVSup server's authentication database. It is invoked with a client name and a server name. ClientName is the name the client uses to gain access to the server. By convention, e-mail addresses are used for all client names, e.g., 'BillyJoe@FreeBSD.org'. Client names are case-insensitive. ServerName is the name of the CVSup server which the client wishes to access. By convention, it is the canonical fully-qualified domain name of the server, e.g., 'CVSup.FreeBSD.ORG'. This must agree with the server's own idea of its name. The name is case-insensitive. To set up authentication for a given server, one must perform the following steps: 1. Obtain the official serverName from the administrator of the server or from some other source. 2. Choose an appropriate clientName. It should be in the form of a valid e-mail address, to make it easy for the server administrator to contact the user if necessary. 3. Choose an arbitrary secret password. 4. Run cpasswd, and type in the password when prompted for it. The utility will print out a line to send to the server administrator, and instruct you how to modify your $HOME/.csup/auth file. You should use a secure channel to send the line to the server administrator. Since $HOME/.csup/auth contains passwords, you should ensure that it is not readable by anyone except yourself. FILES
$HOME/.csup/auth Authentication password file. SEE ALSO
csup(1), cvsup(1), cvsupd(8). http://www.cvsup.org/ AUTHORS
Petar Zhivkov Petrov <pesho.petrov@gmail.com> is the author of cpasswd, the rewrite of cvpasswd. John Polstra <jdp@polstra.com> is the author of CVSup. LEGALITIES
CVSup is a registered trademark of John D. Polstra. FreeBSD June 27, 2007 FreeBSD

Check Out this Related Man Page

PQRM(1) 							       pqrm								   PQRM(1)

NAME
pqrm - Remove job from NetWare print queue SYNOPSIS
pqrm [ -h ] [ -S server ] [ -U user name ] [ -P password | -n ] [ -C ] queue_name job_ID [ another_job_ID ... ] DESCRIPTION
pqrm remove specified jobs from the NetWare print queue available to you on some server. If you are already connected to some server, this one is used. pqrm looks up the file $HOME/.nwclient to find a file server, a user name and possibly a password. See nwclient(5) for more information. Please note that the access permissions of .nwclient MUST be 600, for security reasons. OPTIONS
queue_name queue_name is used to specify queue. You can not use wildcards in the name. job_ID , another_job_ID job_ID is used to specify which job has to be deleted. -S server server is the name of the server you want to use. -U user name If the user name your NetWare administrator gave to you differs from your unix user-id, you should use -U to tell the server about your NetWare user name. -P password You may want to give the password required by the server on the command line. You should be careful about using passwords in scripts. -n -n should be given to mount shares which do not require a password to log in. If neither -n nor -P are given, pqstat prompts for a password. -C By default, passwords are converted to uppercase before they are sent to the server, because most servers require this. You can turn off this conversion by -C. SEE ALSO
nwclient(5), nprint(1), slist(1), ncpmount(8), ncpumount(8), pqlist(1), pqstat(1) CREDITS
pqrm was written by Petr Vandrovec (vandrove@vc.cvut.cz) pqrm 03/03/1998 PQRM(1)
Man Page

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

VisionFS error

I have a Unix SCO 5.0 connected to the Windows 2000 domain, the administrator was able to access any share folders from the Unix server until I changed the administrator password. When the administrator user tries to connect to the Unix Share a message comes up: Incorrect password or unknown... (0 Replies)
Discussion started by: gonzalez109
0 Replies

2. BSD

portupgrade

Hello this is newly user of FreeBSD and got a problem on portupgrade I just installed release4.6 and then cvsup was ok every ports are renew to up to date. but can't make install even one ports. incomplete process with message below. i want someone advice me what the reason and how to solve... (1 Reply)
Discussion started by: antoniozacca
1 Replies

3. AIX

copy outgoing administrator privilege

Hi, How do I make sure I copied all privileges from previous administrator account? What files/path should I modify to make mine the same. Thanks in advance, Itik (1 Reply)
Discussion started by: itik
1 Replies

4. IP Networking

Slow LAN FTP Transfers with FreeBSD...

Hello, I've got a FreeBSD 6 server running on my network that I used as a file server for my main computer. However I've really become frustrated with the slow up/down speeds I'm getting, about 100KB/s, which is about as bad as if I was using a "real" server. My setup is as follows: ISP |... (4 Replies)
Discussion started by: CyberCat
4 Replies

5. BSD

Updating the FreeBSD ports

When updating the ports, I normally do the following: rm -r /usr/ports csup -L 2 -h cvsup.FreeBSD.org /usr/share/examples/cvsup/ports-supfile This however takes rather long, about 20 mins on stock hardware. Is there a way to exclude certain ports from being updated, such as games and print? (4 Replies)
Discussion started by: figaro
4 Replies

6. BSD

FreeBSD abnormal permission changes in /home

Hi, I have a bit of a headache with a server doing some rather mysterious yet static changes to permissions in /home. The server in question is a FreeBSD server. It's an older beast with quite a few custom tweaks and now I'm stuck with it :-) The problem is that some of the directories in... (2 Replies)
Discussion started by: brightstorm
2 Replies

7. UNIX for Dummies Questions & Answers

FreeBSD vs CentOS as server

(3 Replies)
Discussion started by: jwz104
3 Replies

8. UNIX for Advanced & Expert Users

Writing a REST server to run on FreeBSD -- how to structure for concurrency?

Hi All, I want to write a domain specific REST/HTTP server to run on FreeBSD. I have control over both the server side and the primary client intended to consume the service. My question is: how do you think it should be designed to support multiple connections, given: It will run on a... (6 Replies)
Discussion started by: LittleCookieMon
6 Replies