- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: login() password problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2004 11:07 AM
05-24-2004 11:07 AM
So, I turned off Kerberos authentication and created a user in /etc/passwd (via sam) and changed the users password to contain an @ symbol. I still couldn't login until I changed the users password and removed the at symbol. su works just find with the at symbol in the password.
Does anyone know of a patch for login, or am I just stuck telling users they can't use the @ symbol in their passwords. Usually only the geeks do anyway.
Thanks
>/dev/null
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2004 12:14 PM
05-24-2004 12:14 PM
Re: login() password problems
Since supposedly you are using Kerobos, the rules that SHOULD apply are those rules, which I don't know.
Fast practical solution is the one you proposed. Tell the users no funy characters. We don't need no stinking special characters anyway. Right? Forgive my humor.
The only thing I don't like is this may be the symptom of other problems. I'd see if that Kerobos implementation is working properly.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2004 05:29 PM
05-24-2004 05:29 PM
Re: login() password problems
Example
Let's assume your username is "typesbad" and password is "fatfingr"
Login: typesbad
Password: fatfib@fatding@fatfingr (although hidden let's assume this is what you typed)
this combination will log you in.
If you did not have the misfortune of vorking with Virtual Vault which locks you real good after 3 hard tries, you can not imagine what a god sent character is that @ sign. It may be something related to the login process and can be changed but even if this is the case I do not know how.
Hope this helps clear why.
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2004 05:39 PM
05-24-2004 05:39 PM
Re: login() password problems
Try escaping the '@' with a '\' this should work. You could also set the erase to someother character in your .profile, that way you can still use '@' in your password, without the need for it to be escaped with '\'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2004 05:10 AM
05-25-2004 05:10 AM
Re: login() password problems
# stty -a < /dev/ttyconf
Try this and see if "kill" is assigned to @ symbol.
If yes then change this to something else
# stty kill ^X < /dev/ttyconf > /dev/ttyconf.
Try now. Alternative way is to include a backslash before the @ symbol to "escape" the special character
If the user password is user@123 then enter the password as user\@123.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2004 06:09 AM
05-25-2004 06:09 AM
Re: login() password problems
I would rather suggest not to use @ sign because it has some other purpose to serve.
In case you write a wrong user name or password by mistake and instead for waiting for the another login prompt you can correct you mistakes by typing @ and then writing the loginname or password again.
for e.g. i am logging as root and typed t twice in end still i am able to correct my self using @ sign and then by typing root correctly i still can proceed with login. @ will nullify the previous characters.
login:roott@root
password:
#
Other workaorund is already suggested that is by using Escape character.
Hope this helps.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2004 06:16 AM
05-25-2004 06:16 AM
Re: login() password problems
Also of note is that you can't use a # sign in your password either.
Thanks again.
>/dev/null
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2004 07:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2004 07:41 AM
05-25-2004 07:41 AM
Re: login() password problems
man stty gave me more enlightenment regarding this. I will probably change it then! THANKS!
# stty -a < /dev/ttyconf
min = 4; time = 0;
intr = DEL; quit = ^\; erase = #; kill = @
eof = ^D; eol = ^@; eol2
stop = ^S; start = ^Q; susp
werase
>/dev/null
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2004 08:27 AM
05-25-2004 08:27 AM
Re: login() password problems
- Tell users that they are authenticating across many different platforms and each one has it's own rules about passwords, filenames, directory names, etc. As a result, they must choose from the lowest common denominator for password rules. One system may accept # and @ but another may not. Or one system likes spaces and punctuation but another does not. One system can handle \{}[]*#? in filenames but another either cannot handle them or must escape them. Since this is so easy to rememeber, just summarize all the rules for all the systems and the users will be happy.
- Or tell the users to use alphanumerics only.
- For HP-UX, you can enable # and @ (using ttyconf) characters but users will probably get confused when they try to copy a file with # in it.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2004 01:50 PM
05-25-2004 01:50 PM
Re: login() password problems
The correct syntax was:
stty erase ^H < /dev/ttyconf
stty intr ^C < /dev/ttyconf
Perfect! Now I can use both @ and # in passwords. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2004 10:53 AM
06-01-2004 10:53 AM
Re: login() password problems
that users should NOT include in passwords:
# because it means kill
@ because it means interupt
& because it means erase line
\ because it means "escape"
Any others?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2004 02:14 PM
06-01-2004 02:14 PM
Re: login() password problems
The termio list is lengthy but the most common are # (erase previous character) and @ (cancel current line). & is not defined as anything special and does not erase the line. \ is not special either. It means escape the next character but only to a shell (unless ICANON was set with /dev/ttyconf). Remember that login has nothing to do with a shell prompt. login and password occur completely outside the environment setup in a shell...or more accurately, the shell sets up it's own environment after login with /etc/profile where stty is used to change the driver defaults.
As mentioned, the special device file /dev/ttyconf was created to allow changing the driver defaults before login. As to which characters to avoid, you have to decide whether to reassign the defaults. If so, then # and @ are fine to use...unless of course you are using passwords across many different operating systems. You must check with each one as to reserved characters.
Once logged on, special characters are now defined by the shell and may be different for different shells and of course, the user may change these in a local .profile or simply use the stty command. Again, all the shell features occur long after login/password have been handled.
Bill Hassell, sysadmin