Bug 63137 - up2date code error behind proxy
Summary: up2date code error behind proxy
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
(Show other bugs)
Version: 7.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2002-04-10 15:00 UTC by Need Real Name
Modified: 2015-01-07 23:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-10 19:04:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2002-04-10 15:00:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0; Walt Disney 

Description of problem:
Line 356 of /usr/share/rhn/up2date_client/up2date.py and subsequent 9 lines. It 
is possible to pass through this small routine with ProxyUser not set to any 
value. I find that setting proxyUser = None just prior to this routine allows 
me to continue.

I believe there should be an else clause in the upper section so that if 
cfg.readEntry("enableProxyAuth": is true and if cfg.readEntry("proxyUser") is 
false, it will set proxyUser to None.

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

How reproducible:

Steps to Reproduce:
1. Run up2date behind a proxy
2. The proxy doesn't need a username
3. The proxy doesn't need a password

Actual Results:  I got an error traceback saying that proxyUser was undefined.

Expected Results:  up2date should have installed the requested updates.

Additional info:

I have found this bug and fixed it several times in the past and it remains in 
the current version.

Comment 1 Need Real Name 2002-04-10 15:04:33 UTC
Also, proxyPassword is not defaulted, just like proxyUser.

Comment 2 Adrian Likins 2002-04-10 19:04:21 UTC
hmm, true. EnableProxyAuth shouldnt be enabled if a proxyUser 
and proxyPassword isnt set. I didnt think the config tools
would allow that combination. 

Workaround is to disable enableProxyAuth if your not using it.

I'll add the bits in that section to default proxyUser/proxyPasswd
to None in that case.

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