Bug 11915 – Community SSU script doesn't work if you are behind a proxy

Bug 11915 - Community SSU script doesn't work if you are behind a proxy


Summary:	Community SSU script doesn't work if you are behind a proxy

Status:	UNCONFIRMED

Product:	Maemo 5 Community SSU
Component:	community-ssu-enabler
Version:	unspecified
Platform:	N900 Maemo

Importance:	Unspecified normal with 1 vote (vote)
Target Milestone:	---
Assigned To:	unassigned
QA Contact:	general

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2011-02-09 14:47 UTC by nicolai
Modified:	2011-02-26 14:54 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description nicolai (reporter) 2011-02-09 14:47:30 UTC

SOFTWARE VERSION: 
20.2010.36-2.003

EXACT STEPS LEADING TO PROBLEM: 
1. follow wiki steps for community ssu testing
2. launch "Community SSU" from progam menu.
(/usr/sbin/install-community-ssu)

EXPECTED OUTCOME: 
apt-get finds the repositorys 

ACTUAL OUTCOME: 
apt-get can not find the repositorys 

REPRODUCIBILITY: 
always

OTHER COMMENTS: 
Ok, this is a common problem of apt-get
in maemo 5. I don't know how to access the
proxy settings from within the script,
but for it works if I start the install-community-ssu
after exporting the proxy settings in the shell:
export https_proxy=https://proxyname:port
export http_proxy=http://proxyname:port

Comment 1 Lucas Maneos 2011-02-26 14:54:52 UTC

(In reply to comment #0)
> I don't know how to access the proxy settings from within the script

Quick, dirty and untested:

proxy_vars=$(gconftool-2 -R /system/http_proxy | sed -e 's/^/proxy_/' -e 's/
//g')
eval $proxy_vars
if [ "x$proxy_use_http_proxy" = "xtrue" ]; then
    export http_proxy=http://${proxy_host}:${proxy_port}
fi

One may also need to check whether /system/proxy/mode is "manual" (not sure if
/system/http_proxy/* are set if its value is "none", and if it's "auto" the
whole thing is a lost cause anyway).

If https_proxy is also needed the keys to check are /system/proxy/secure_host &
/system/proxy/secure_port.