Sponsored Content
Full Discussion: Why use strong passwords?
Special Forums Cybersecurity Why use strong passwords? Post 302727019 by jgt on Monday 5th of November 2012 01:46:59 PM
Old 11-05-2012
Even so, you are still left with the problem of determining the seed used on the target system. The same password for the same user on the same system does not produce the same encrypted key each time the password is changed.
 

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Strong quotes and spaces

We ran into a problem because of a shop that uses Windows and UNIX. The file names that Windows uses have spaces in them. When they get moved to the unix system they still have spaces. This produces a problem in our script that moves them again from one unix system to another. I've made up a... (2 Replies)
Discussion started by: jimcampanella
2 Replies

2. UNIX for Advanced & Expert Users

When did UNIX start using encrypted passwords, and not displaying passwords when you type them in?

I've been using various versions of UNIX and Linux since 1993, and I've never run across one that showed your password as you type it in when you log in, or one that stored passwords in plain text rather than encrypted. I'm writing a script for work for a security audit, and two of the... (5 Replies)
Discussion started by: Anne Neville
5 Replies
SGE_PASSWD(1)						   Sun Grid Engine User Commands					     SGE_PASSWD(1)

NAME
sgepasswd - Modify the Sun Grid Engine password file of Sun Grid Engine SYNTAX
sgepasswd [[ -D domain ] -d user ] sgepasswd [ -D domain ] [ user ] DESCRIPTION
sgepasswd modifies the Sun Grid Engine password file sgepasswd(5). This file contains a list of usernames and their windows password in encrypted form. sge_execd(8) and sge_shepherd(8) on hosts running Mi- crosoft Windows as operating systems use this information to start jobs for a certain user. Each user can use the sgepasswd application to add a new entry for the own user account. It is also possible to change the stored password with sgepasswd as far as the user knows the old one. The root user additionally has the permission to change the password entries for other user accounts. Root can also delete existing entries. The sgepasswd binary is only available on non-Windows hosts. OPTIONS
-D domain Per default sgepasswd will add/modify the current Unix username without domain specification. This switch can be used to add a domain specification in front of the current user name. Consult your Microsoft Windows documentation to get more information about domain users. -d user Only root can use this parameter to delete entries from the sgepasswd(5) file. -help Prints a listing of all options. ENVIRONMENTAL VARIABLES
SGE_CERTFILE Specifies the location of public key file. Per default sgepasswd will use the file $SGE_ROOT/$SGE_CELL/com- mon/sgeCA/certs/cert.pem SGE_KEYFILE If set, specifies the location of the private key file. Default is /var/sgeCA/port${SGE_QMASTER_PORT}/${SGE_CELL}/pri- vate/key.pem SGE_RANDFILE If set, specifies the location of the seed used to create encrypted versions of user passwords. Default is /var/sgeCA/port${SGE_QMASTER_PORT}/${SGE_CELL}/private/rand.seed SEE ALSO
sge_intro(1), sgepasswd(5) COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ SGE_PASSWD(1)
All times are GMT -4. The time now is 09:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy