this is still not working quite fully for add-apt-repository on a new
clean install of 18.04.1.
it may be working for http only, but for https you still need to
manually provide the https_proxy env var.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
{juliank, magnetik},
I checked add-apt-repository operation about a week ago while testing
some (unrelated) automation changes on bionic with proxy environment
variables and it was fine.
apt-key should not be used at all due to its deprecated functionality.
For your reference:
The manpage for
The fix is to put .asc or .gpg files in trusted.gpg.d and not use apt-
key.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761
Title:
apt-key and add-apt-repository don't honor
The variables are usually http_proxy and https_proxy, not uppercase
versions. That said, gpg does not seem to honor either. It does,
however, honor an option --keyserver-options http-proxy=, although it is
deprecated.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Sorry to ping everyone here, but I'm facing the same on bionic while it
was okay in xenial.
The env variables HTTP_PROXY and HTTPS_PROXY are correctly exported, but
it seems that bionic do not use them anymore.
What are the hints for possible fix? I see that the two affected
packages are INVALID
apt-key adv is as the name says an advanced feature for direct access to
gpg. Hence support for proxies lies with gpg. The adv command is
deprecated, as is apt-key in general.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
Added apt based on #15.
dpkg -S `which apt-key`
apt: /usr/bin/apt-key
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761
The difference for Xenial / Bionic
In Xenial apt-key spawns a process named gpg that honors the env. for
http_proxy.
In Bionic the command “apt-key” spawns a process “dirmngr –daemon –homedir
/tmp/apt-key-gpghome.[RANDOM STRING]” which do not honor the env. for
http_proxy / https_proxy.
It also seems that when running apt-key, dirmngr starts with --daemon
and --homedir /tmp/apt-key-gpghome.[RANDOM STRING]. This results that
the dirmngr.conf in ~/.gnupg is also not honored.
We also tried having the configuration-file in /etc/dirmngr/dirmngr.conf
which is also not honored.
We are
I double-checked add-apt-repository and apt-key behavior on bionic (the
same doesn't work on xenial as the fix was landed for bionic only).
add-apt-proxy:
➜ ~ sudo strace -f -e connect bash -c 'HTTP_PROXY=http://192.168.1.1:3128
HTTPS_PROXY=http://192.168.1.1:3128 add-apt-repository
I double-checked add-apt-repository and apt-key behavior on bionic (the
same doesn't work on xenial as the fix was landed for bionic only).
add-apt-proxy:
➜ ~ sudo strace -f -e connect bash -c 'HTTP_PROXY=http://192.168.1.1:3128
HTTPS_PROXY=http://192.168.1.1:3128 add-apt-repository
@miskokot
Probably best to open this up in a new bug report if you think there is
an error. However, I can at least confirm that having http_proxy and
https_proxy set does yield connections to my proxy with apt-add-
repository
root@bionic:~# http_proxy=http://10.5.0.5:8000
I am not sure this was fixed, or maybe I just hardly misunderstand that.
Under current Bionic (software-properties-common 0.96.24.32.3) I still
can't retrieve keys via env-var defined `http_proxy`.
# echo $http_proxy
http://1.2.3.4:3128
# echo $https_proxy
http://1.2.3.4:3128
# apt-key adv
This bug was fixed in the package software-properties - 0.96.24.25
---
software-properties (0.96.24.25) bionic; urgency=medium
* ppa.py:
- rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
& python's built in urllib.
- thus, add-apt-key for PPAs
** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761
Title:
apt-key and add-apt-repository don't honor Acquire::http::Proxy
Bill, just for some more information.
Also note "This options is deprecated".
The correct way to do it now is to configure dirmngr.conf (which is
backgrounded when you invoke gpg).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Muelli,
using use --keyserver-options http-proxy=$http_proxy is nice idea. But I
still has the issue.
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Regarding the gpg proxy setting, I found this document
https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration-
Options.html
http-proxy=value
This options is deprecated. Set the proxy to use for HTTP and HKP keyservers.
This overrides any proxy defined in dirmngr.conf.
Will take a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761
This is a very annoying bug that hits me very often. It's also the
source of yet another place to configure the proxy server.
My usual work around is trying to patch all executions of apt-key and
friends to use --keyserver-options http-proxy=$http_proxy.
It might be possible to patch
(cloud images, apt, keyserver, utilities like add-apt-repository)
Looking at your other bug, ntp should be covered too - and anything else
relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I understand why you expected apt-key and add-apt-repository to use the
proxy you defined with Acquire::http::proxy in /etc/apt. But I'm not
sure this is the only interpretation.
I expect Acquire::http::proxy to
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761
Title:
apt-key and add-apt-repository don't honor Acquire::http::Proxy
To manage notifications about this bug
See also: https://bugs.launchpad.net/maas/+bug/1257082
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761
Title:
apt-key and add-apt-repository don't honor Acquire::http::Proxy
To manage
24 matches
Mail list logo
