Javier Marcon <javiermarcon@gmail.com> (2016-07-11): > El 11/07/16 a las 05:32, Philipp Kern escribió: > > There is a key property on the repository preseed where you can > > specify a URL: > > > > d-i apt-setup/local0/key string [...] > > > > You could specify a keyserver there using HTTP, but any HTTP server > > should do. (And HTTPS in testing.) > > > > Kind regards > > Philipp Kern > > > thanks, so it will do the trick setting the line: > > d-i apt-setup/local0/key string keys.gnupg.net E1F958385BFE2B6E > > Or the line shuld be: > > d-i apt-setup/local0/key string --keyserver keys.gnupg.net E1F958385BFE2B6E > > Which format is the correct? The code goes like this: | if [ -n "$key" ]; then | # fetch the key | while :; do | if fetch-url "$key" "$ROOT/tmp/key$i.pub"; then | # add it to the keyring | $chroot $ROOT apt-key add "/tmp/key$i.pub" | rm -f "$ROOT/tmp/key$i.pub" | break | else and fetch-url is morally a wget/curl equivalent within d-i. I'd usually specify something like http://my.own.server/mykey.asc; I'm not sure whether Philipp's reply meant to imply you could feed it an URL to a GPG key to be fetched from a keyserver. Some seem to be accessible over port 80 (probably to bypass limitations of usual corporate proxies and/or firewalls), but that doesn't seem to give users a direct http URL to download a key. KiBi.
Attachment:
signature.asc
Description: Digital signature