Bug 858536 - Setting a proxy fails when username contains a backslash
Summary: Setting a proxy fails when username contains a backslash
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 978845 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-19 04:36 UTC by Baurzhan Muftakhidinov
Modified: 2014-07-21 17:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 978845 (view as bug list)
Environment:
Last Closed: 2014-07-21 17:00:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Baurzhan Muftakhidinov 2012-09-19 04:36:09 UTC
Description of problem:

Setting the proxy does not work in Fedora 18 Alpha net installer iso.

Version-Release number of selected component (if applicable):
Fedora 18 Aplha

How reproducible:
Every time

Steps to Reproduce:
1. Start the installation from Fedora 18 Alpha netinstall cd
2. Go to Installation Source, Enter mirror, open Proxy setup, Enable authorization
3. Enter Proxy credentials, close the dialog windows, open it again
4. Username is the password you enterer earlier.
5. If username contains backslash, proxy url gets substituted by a password+ 3128 port.
  
Actual results:
Username is substituted by password you entered earlier.

Expected results:
Username should not be substituted by password.

Additional info:

Its a copy-paste typo, I guess. Check here
http://git.fedorahosted.org/cgit/anaconda.git/tree/pyanaconda/ui/gui/spokes/source.py
Line 67-68.

Also, please check for cases where username contains backslash. The proxy url gets substituted by a password in that case.

Comment 1 Baurzhan Muftakhidinov 2012-09-19 07:32:20 UTC
No, that's not a backslash in username which causes proxy url damaging when one re-opens the settings dialog windows, but '=' sign in password. 
If you have '=' in password, proxy url will be replaced with your password + default 3128 proxy port.

Comment 2 Chris Lumens 2012-09-19 14:40:29 UTC
Fixed the typo, but I'm not seeing any funny behavior with an = in the password.  Perhaps it's also fixed by the typo, but that seems a little bit unlikely.  Please check again when there's an updated image and let me know if you are continuing to see problems.  Thanks.

Comment 3 Baurzhan Muftakhidinov 2012-10-09 07:54:13 UTC
Hello,

I have downloaded the Fedora 18 Beta TC2 image, and there is a following error:

When username contains the backslash "\", the proxy URL I have set earlier is damaged.

Comment 4 Baurzhan Muftakhidinov 2012-10-18 14:06:41 UTC
Ping.

Comment 5 Adam Williamson 2012-11-23 02:19:51 UTC
Can you please check with Beta RC1 and let us know the current status? Sorry for the trouble.

Comment 6 Baurzhan Muftakhidinov 2012-11-23 08:10:31 UTC
Hello,

Yes, the same error happens, I downloaded netinstall x64 image from here
(http://alt.fedoraproject.org/pub/alt/stage/18-Beta-RC1/Fedora/x86_64/iso/Fedora-18-Beta-x86_64-netinst.iso)

Steps to reproduce
1) Boot from netinstall image;
2) Select Installation source;
3) Check "On the network" radio button, select http:// from drop-down menu instead of Closest mirror;
4) Click the "Proxy Setup" button on the right side of input field;
5) Check "Enable HTTP Proxy" and "Use Authentication", enter your proxy hostname and port, enter username with backslash, like mydomain\username and password, click on Add button, window will close;
6) Click the "Proxy Setup" button on the right side of input field;
7) Now we see that proxy string is equal to http://mydomain\username:3128, e.g. it was substituted by username and default port on the end.

Comment 7 Baurzhan Muftakhidinov 2012-12-24 08:20:49 UTC
Ping.

Comment 8 Baurzhan Muftakhidinov 2013-01-04 15:21:08 UTC
I just figured out that my username is like
domain\nusername, i.e. it always contains "\n".

Could it be the issue?

Comment 9 Brian Lane 2013-06-28 00:32:25 UTC
*** Bug 978845 has been marked as a duplicate of this bug. ***

Comment 10 Emanuele Gissi 2013-06-28 07:00:35 UTC
Adding a new case from duplicate bug 978845.
What happens is slightly different.

Description of problem:

Setting the proxy does not work in Fedora 19 RC2 net installer iso.

Version-Release number of selected component (if applicable):
Fedora 19 RC2

How reproducible:
Every time

Steps to Reproduce:
1. Start the installation from Fedora 19 RC2 netinstall cd
2. Go to Installation Source, leave "Closest mirror", open Proxy setup ("http://proxy:3128"), Enable authorization
3. Enter Proxy credentials (username "GE\emanuele.gissi" and password similar to "password30_"), close the dialog windows, open it again
4. Proxy settings get mangled! ("http://GE\emanuele.gissi:3128")
  
Actual results:
Not possible to set correct proxy settings.

Expected results:
It should be possible to enter correct proxy settings.

Thank you!

Comment 11 Emanuele Gissi 2013-06-28 07:03:01 UTC
Please, modify version to 19 RC2. Emanuele

Comment 12 Adam Williamson 2013-06-28 08:11:45 UTC
Emanuele: it's not really terribly important to anaconda development, as it happens (the version field). I wouldn't sweat it. Bumping to Rawhide as there's no point fixing for F18 or F19 any more.

Comment 13 Emanuele Gissi 2013-12-06 07:47:30 UTC
This bug is still present in F20 beta installer.

Steps to Reproduce:
1. Start the installation from Fedora 20 beta netinstall cd
2. Go to Installation Source, leave "Closest mirror", open Proxy setup ("http://proxy:3128"), Enable authorization
3. Enter Proxy credentials (username "GE\emanuele.gissi" and password similar to "password30_"), close the dialog windows, open it again
4. Proxy settings get mangled! ("http://GE\emanuele.gissi:3128")
  
Actual results:
Not possible to set correct proxy settings.

I succesfully installed by using a live image and setting proxy settings there.

Best regards,
Emanuele

Comment 14 Brian Lane 2014-07-21 17:00:27 UTC
This was fixed in rawhide and will be in f21.


Note You need to log in before you can comment on or make changes to this bug.