Bug 77999
Summary: | When a password with the # sign is used it does not recognise it. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | P H <paddy667> |
Component: | samba | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED UPSTREAM | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | abartlet |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-05-23 18:18:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
P H
2002-11-17 03:56:48 UTC
might be due to URL encoding - I'll have a look at it Actually, this is sounding like a generic 'code page' issue. Should we convert passwords between code pages prior to checking them - which is fine for SWAT, but only in 3.0. However, things like FTP are a bit different. (and not relevent here). Andrew Bartlett I've commited a change to Samba HEAD that should convert your username/password into our 'unix' charset. I have no idea if it would actually help, as it depends very much on what charset the password was hashed in, but it seems a better idea than just assuming it doesn't matter. |