Right – we don’t allow authenticated proxies to be set per-origin because the cleartext proxy authentication details would get stored in /var/pkg, which would be bad.
The best solution at the moment, is to set the $http_proxy environment variable at the time you’re running the command (though that exposes the authentication details to anyone who can run ‘pargs -e’ on the pkg(1) process, but it’s the best we have right now)
Ideally, we’d have a way to securely store the proxy information – we don’t as yet, but it’s something I’d like to add.
timsfoster said:
http://docs.oracle.com/cd/E26502_01/html/E29030/pkglint-1.html#REFMAN1pkglint-1
Craig Burtenshaw said:
Hi Tim,
With the proxy settings, is there a plan to enable authenticated proxies?
That is:
–proxy http://:@:
Currently I get:
pkg.sysrepo: unable to get publisher information: proxy value http://:@: for http://pkg.oracle.com/solaris/release is not supported.
Thank you for any suggestions
Craig.
Craig Burtenshaw said:
Hi Again,
My comments above seemed to have broken.
–proxy http://user:password@proxy:port
gets the error:
pkg.sysrepo: unable to get publisher information: proxy value http://user:password@proxy:port for http://pkg.oracle.solaris/release is not supported.
Thanks again…
Cheers
Craig.
timsfoster said:
Right – we don’t allow authenticated proxies to be set per-origin because the cleartext proxy authentication details would get stored in /var/pkg, which would be bad.
The best solution at the moment, is to set the $http_proxy environment variable at the time you’re running the command (though that exposes the authentication details to anyone who can run ‘pargs -e’ on the pkg(1) process, but it’s the best we have right now)
Ideally, we’d have a way to securely store the proxy information – we don’t as yet, but it’s something I’d like to add.