Closed RafaelLinux closed 1 month ago
Could you send me the output of:
env|grep -i proxy
Please make sure to redact your password if needed.
Proxy variables seems assigned at console level:
no_proxy=0.0.0.0/0,work.oursite.com
gopher_proxy=
ftp_proxy=
https_proxy=http://10.162.0.1:128
socks_proxy=
NO_PROXY=0.0.0.0/0,work.oursite.com
http_proxy=http://10.162.0.1:128
SOCKS_PROXY=
Take into account that proxy credentials are not in environment variables and can't be added in the way "user:pwd@10.162.0.1:128" cause is not a standard for this variables and will be ignored.
hm - all sources that I could find indicate usage of this syntax:
export https_proxy="https://USER:PASSWORD@PROXY_SERVER:PORT"
e.g. https://www.shellhacks.com/linux-proxy-server-settings-set-proxy-command-line/
Also the python-requests library that opi is using will work with that syntax: https://docs.python-requests.org/en/latest/user/advanced/#proxies
The yast proxy module seems to essentially do what is described in this support document: https://www.suse.com/support/kb/doc/?id=000017441
It will only store the proxy credentials in /root/.curlrc
:
# Changed by YaST2 module proxy 19.09.2024
--proxy-user "testuser:testpass"
--noproxy "localhost,127.0.0.1"
I would expect that only libcurl based tools will parse that file.
But then, I should try with the "export ...
." and launch opi
?
Yes. That should work according to the python-requests documentation.
To make it persistent I guess you would need to put it into your bashrc, .profile or /etc/environment
(no export in that file!)
Yes, this is indeed how it works. Personally I don't like to have the username/password clear, but I guess there is a problem between openSUSE and the applications that want to use the credentials it stores for the proxy. It should be somewhat transparent, as it is when using “zypper” or other commands that require Internet access.
Thanks
I close the request
To access the Internet, my computer requires access to an HTTP proxy with user authentication. The native openSUSE applications use it without problems, using for this purpose the username and passwords previously stored by me with the “Yast proxy” tool. I don't need to type user and password authentication, because I take them from my configuration.
However, opi seems to ignore the proxy configuration and starts showing authentication errors when I try to install applications with it.
This is partial ouput (from beginning) launching opi:
Output from commands: