Sponsored Content
Top Forums UNIX for Advanced & Expert Users When did UNIX start using encrypted passwords, and not displaying passwords when you type them in? Post 302606051 by drl on Friday 9th of March 2012 11:55:17 AM
Old 03-09-2012
Hi.

Note also that the original terminal for UNIX (TM) was in fact a teletype -- a TTY. That, and many hardcopy devices, would always show the text as it was typed in, so the 8 character-space for the password was obscured beforehand with a series of over-strikes, so that it was very difficult to see what had been typed by the human. Still the NSA could ... but that's a different story, eh? Smilie ... cheers, drl
This User Gave Thanks to drl For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

Urgent !!! - Script to Change passwords in unix

I have SunOs 5.8. I need to change password using a unix shell script. I have tried to pipe the passwords to the passwd command but does not work. Pls provide a script to change passwds of a list of users using a shell script. ( I have also tried crypt() but did not work) The flow of the... (2 Replies)
Discussion started by: tofani
2 Replies

2. UNIX for Dummies Questions & Answers

Unix passwords?

The local policy is set in our LAN so that passwords have to be 8 characters and contain a capital letter, a small letter and a special character. Is Unix able to restrict users passwords to certain lengths and characters. (1 Reply)
Discussion started by: wmosley2
1 Replies

3. UNIX for Advanced & Expert Users

About unix passwords.

How the unix is maintaining the password ? How it does the encryption and how the passwords are stored in the system and where it is stored ? How it is better when compared to other OS ? (1 Reply)
Discussion started by: nagalenoj
1 Replies

4. Shell Programming and Scripting

Oracle Passwords in Unix scripts

Hi Most of the shell scripts I am dealing with have to connect to oracle database . The username password is stored in a environment file which sets the variables for username and password . Set user id do not work on AIX so users who will execute these scripts need to have read or execute... (5 Replies)
Discussion started by: clifford
5 Replies

5. Shell Programming and Scripting

Script to Check for Unix/Linux Passwords

We have almost 100+ Unix/Linux servers, on which I have account. Does anybody have a batch script which can do the following : - check if my password is correct - change my password We use SFTP/SSH on Linux. The solution should force reading of password from command line. ( Passwordless... (1 Reply)
Discussion started by: lucknowm
1 Replies

6. Cybersecurity

how to Hide Passwords From UNIX ps Command

Hi, By reporting the process status with ps, any Unix user will see the command line arguments #ps -ef UID PID PPID C STIME TTY TIME CMD lsc 13837 13825 0 May 11 pts/17 0:01 -ksh oracle 4698 6294 0 12:00:40 ? 0:00 sqlplus -s system/manager appluser 4229 4062 0 12:00:03... (2 Replies)
Discussion started by: bhagirathi
2 Replies

7. Shell Programming and Scripting

SSH - Passing Unix login passwords through shell scripts

Hi All , I need to call a script runscript_B.sh on server A, the runscript_B.sh script locating in server B. The runscript_B.sh in calls another script runscript_A on server A itself. it seend, i need to be connect from Server A to Server B using ssh. I have tryed like this in... (3 Replies)
Discussion started by: koti_rama
3 Replies

8. AIX

When did AIX start using /etc/security/passwd instead of /etc/passwd to store encrypted passwords?

Does anyone know when AIX started using /etc/security/passwd instead of /etc/passwd to store encrypted passwords? (1 Reply)
Discussion started by: Anne Neville
1 Replies

9. Shell Programming and Scripting

How to change passwords for User accounts on multiple UNIX/Linux machines remotely?

Hello Experts, Need some direction on creating shell script for following environment: We have about 20 people in the team working as Oracle DBA's (sysdba's and appdba's). Total Servers which is a mix of Unix and Linux are 200. We do not have Root user access on any of the servers and... (3 Replies)
Discussion started by: sha2402
3 Replies
LLOGIN(1)						      General Commands Manual							 LLOGIN(1)

NAME
llogin - Connect to a LAT service SYNOPSIS
llogin [options] service Options: [-dvcpblhQ] [-H node] [-R port] [-n name] [-w password | -W] [-q quit char] DESCRIPTION
llogin connects your terminal to a LAT service via latd, the service name must be known to latd for this to work. OPTIONS
-d Shows learned services. This is the same as latcp -d -l -d -v Verbose form of -d. -v without -d is ignored. -H <node> Remote nodename. If the service is advertised by more than one node and you want to connect to a particular node then use this switch. By default you will be connected to the node with the highest rating. -R <port> Connect to a specific port on (usually) a terminal server. This is the port NAME on the server and not the port number. -c Do not convert typed LF to CR. By default the enter key generates LF and llogin converts it CR as it is the most generically useful translation. This switch will cause the enter key to send LF instead. Occasionally useful for connecting to Unix consoles. -b Convert typed DEL to BS. By default the DEL key (keyboard, top right usually) send DEL (ASCII 0x7f) to the remote system. This switch will cause the DEL key to send BS (ASCII 8) instead. Useful for some Unix systems connected via terminal servers. -l Convert output LF to VT. By default LF output is sent as CRLF which can cause output formatting problems. Changing this to VT should preserve the output formatting on most devices or terminal emulators. -q <char> Change the quit character. By default CTRL-] will quit the terminal session. Entering a character after -q will cause CTRL-<char> to be the quit character for that session. -q0 will disable the quit character. If you use the latter, make sure you are connecting to a service that will disconnect you when you log out or you will have to kill llogin from another session to get out of it! -Q Tells latd that the service you are connecting to is queued service and not a normal login service or port service. Unfortunately latd cannot tell whether a remote service needs to be queued or not so the onus is on the user to specify this switch when connect- ing to a queued service. -n <name> Sets the local connection name. By default this will be your local TTY name. In most cases this simply affects the display of the terminal on the remote end so you shouldn't need to change it. -w <password> Sends the password for the service. Only needed for services that require a password for access. If the password given is "-" then you will be prompted for a password and it will not be echoed. This avoids having passwords visible on the screen. -W Prompts for the service password. This is the same as -w- (see above). -p Tells llogin to connect to the device named instead of a LAT service. This would usually be a /dev/lat pseudo-terminal but could be any other device you like really. This switch does not make the program useful as a terminal program because there is no way to set any serial parameters, nor am I going to add them. This is just a convenient way to use the /dev/lat ports without the overhead of programs such as minicom. -h Displays a brief usage description. This is the same as invoking llogin without any parameters at all. SEE ALSO latcp(8), latd(8) LAT utilities January 3 2002 LLOGIN(1)
All times are GMT -4. The time now is 01:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy