From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: "Adrián Mihálko" <adriankoooo@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Fix Debian install guide on wireguard.com/install
Date: Wed, 15 Nov 2017 12:08:49 +0100 [thread overview]
Message-ID: <20171115110849.GA27782@lud.polynome.dn42> (raw)
In-Reply-To: <CA+Hw3eY4541LNE9TnS5tsU2O+n28BNQ-Spko5dpem8Ej2_ctFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
Hi Daniel, Adrián,
On 31-10-17, Adrián Mihálko wrote:
> There is a missing step in the Debian installation guide, you must import
> GPG keys before you can add the new repo:
Which version of Debian are you using?
The installation instructions on https://www.wireguard.com/install/ are
tested on Jessie and Stretch, anything older (wheezy) will not work
because the kernel is too old.
Jason, can you add a note on the installation page that says "Jessie or
later" somewhere?
Baptiste
> gpg --keyserver pgpkeys.mit.edu --recv-key 8B48AD6246925553
> gpg -a --export 8B48AD6246925553 | sudo apt-key add -
>
> and also the key 7638D0442B90D010
>
> gpg --keyserver pgpkeys.mit.edu --recv-key 7638D0442B90D010
> gpg -a --export 7638D0442B90D010 | sudo apt-key add -
>
> More about PGP and APT:
>
> http://ccm.net/faq/809-debian-apt-get-no-pubkey-gpg-error
>
> Regards,
> Adrian Mihalko
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-15 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 22:18 Adrián Mihálko
2017-10-31 22:20 ` Jason A. Donenfeld
2017-11-10 7:48 ` Daniel Kahn Gillmor
2017-11-15 11:08 ` Baptiste Jonglez [this message]
[not found] ` <9AD312F5-AB70-40F8-BAF9-64200037D125@gmail.com>
2017-11-15 22:00 ` Baptiste Jonglez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171115110849.GA27782@lud.polynome.dn42 \
--to=baptiste@bitsofnetworks.org \
--cc=adriankoooo@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).