|
Bugzilla – Full Text Bug Listing |
| Summary: | Proxy Config | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Marc Simpson <m.simpson> |
| Component: | YaST2 | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | openSUSE 10.2 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Proposed patch | ||
|
Description
Marc Simpson
2007-10-26 11:59:20 UTC
Having proxy module accept spaces in username field is trivial (see the patch I'll attach shortly). But I'm unsure if space is a valid character for proxy username. Klaus, can you comment? Created attachment 182186 [details]
Proposed patch
Apply this patch to /usr/share/YaST2/clients/proxy.ycp
I'm not quite sure neither. I'm not aware of any RFC, which defines this. But the allowed characters in the username depends on the underlying authentication scheme. There are several known and supported: LDAP, NCSA, MSNT, PAM, SMB, sasl, ... I don't know, if there exists a scheme, which allows spaces in the username. But if there is one, then it has to be translated to the sequence "%20". Hope this helps. The issue is fixed in yast2-network 2.16.10 (for openSUSE Factory). I'm afraid I cannot do much for openSUSE 10.1 as this does not affect so many users that it'd be worth releasing online update. If you're affected by this bug, simply apply the patch from comment #2 |