HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- passwd bugs with special characters?
Operating System - HP-UX
1833818
Members
2525
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
06-11-2010 11:11 AM
06-11-2010 11:11 AM
Hi everybody,
Has anyone else noticed this bug or feature?
1. login as root.
2. perform passwd user1
3. specify password of "harris#$" for example
4. The user "user1" is not able to login through telnet saying password is not correct.
However, if user2 does a su to user1 and enters this new password, they are able su into user1.
I had no problems doing the above 4 steps with other passwords such as "harris123"
I tried this on PA RISC 11.11 and Itanium 11.23
both had this problem.
Has anyone else noticed this bug or feature?
1. login as root.
2. perform passwd user1
3. specify password of "harris#$" for example
4. The user "user1" is not able to login through telnet saying password is not correct.
However, if user2 does a su to user1 and enters this new password, they are able su into user1.
I had no problems doing the above 4 steps with other passwords such as "harris123"
I tried this on PA RISC 11.11 and Itanium 11.23
both had this problem.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2010 11:15 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2010 11:20 AM
06-11-2010 11:20 AM
Re: passwd bugs with special characters?
Thanks for the quick response Patrick. It looks like we must avoid those characters.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2010 11:24 AM
06-11-2010 11:24 AM
Re: passwd bugs with special characters?
>> However, if user2 does a su to user1 and enters this new password, they are able su into user1.
To explain this a bit more:
When you first login, the defaults for special characters are defined in the TTY driver, specifically, # is the erase character (NOT backspace) and @ is defined as a line cancel. When you login, the (archaic and prehistoric) defaults are overridden by an stty command in /etc/profile and $HOME/.profile. So the special meaning for these characters is changed once you are logged in.
As a general rul]e, special characters are problematic on every system, mostly because there are different rules for different systems. If you stay with alpha-numerics and mixed case, you should be fine all virtually all systems.
Bill Hassell, sysadmin
To explain this a bit more:
When you first login, the defaults for special characters are defined in the TTY driver, specifically, # is the erase character (NOT backspace) and @ is defined as a line cancel. When you login, the (archaic and prehistoric) defaults are overridden by an stty command in /etc/profile and $HOME/.profile. So the special meaning for these characters is changed once you are logged in.
As a general rul]e, special characters are problematic on every system, mostly because there are different rules for different systems. If you stay with alpha-numerics and mixed case, you should be fine all virtually all systems.
Bill Hassell, sysadmin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP