From: Antonio Quartulli <a@unstable.cc>
To: Matthias Urlichs <matthias@urlichs.de>, wireguard@lists.zx2c4.com
Subject: Re: Cipher the private key in peers wg0.conf ?
Date: Wed, 16 May 2018 22:09:54 +0800 [thread overview]
Message-ID: <11a67eb5-fd12-a86b-5b00-b6d14ddc30a7@unstable.cc> (raw)
In-Reply-To: <6e06ad4b-24f2-4d25-b52c-780f0f341d2e@urlichs.de>
[-- Attachment #1.1: Type: text/plain, Size: 950 bytes --]
Hi,
On 16/05/18 22:06, Matthias Urlichs wrote:
> On 16.05.2018 14:53, reiner otto wrote:
>> Actually, in wg0.conf the private key is defined in clear text. Which allows dump of physical disk to grab it
>> and to fake this client.
> So? If you have physical access to the peer's (unencrypted) disk you can
> do anything. Security is over.
>> Wouldn't it be safer, to cipher the private key somehow ?
> Where would you store the key for that?
>
> If you need that kind of safety, encrypt the whole disk. Securing the
> private key doesn't help if you can simply subvert the binary that
> decrypts it.
I think this can be compared to classic encrypted private keys, where
you need to decrypt them (normally with a passphrase) before they can be
loaded by the SSL library.
Maybe this could just be a feature in the wg tool, which could decrypt
the key before pushing it down to the kernel.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-05-16 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <392763090.3358208.1526475207903.ref@mail.yahoo.com>
2018-05-16 12:53 ` Cipher the private key in peers wg0.conf ? reiner otto
2018-05-16 14:06 ` Matthias Urlichs
2018-05-16 14:09 ` Antonio Quartulli [this message]
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=11a67eb5-fd12-a86b-5b00-b6d14ddc30a7@unstable.cc \
--to=a@unstable.cc \
--cc=matthias@urlichs.de \
--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).