Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christian Hesse <list@eworm.de>
Cc: Christian Hesse <mail@eworm.de>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH v2 1/1] add dkms configuration file dkms.conf
Date: Sat, 3 Dec 2016 23:21:51 +0100	[thread overview]
Message-ID: <CAHmME9pAz1e2keE0vH-cWORP7pRmhfoivFt0_=_4xEH9xUjLDA@mail.gmail.com> (raw)
In-Reply-To: <20161203124233.27891-1-list@eworm.de>

I like the general idea here of including dkim in WireGuard now, since
basically all distros use it and ship the exact same logic. By putting
it in WireGuard itself, I can provide maintenance over the
interworkings, which will be helpful for downstream.

Another thing I can do is handle the installation myself. `make dkim`
will then copy all the paths and create the dkim.conf file, etc. First
question: is there a standard destination path to which files should
be copied. Second question: what environment variable name do you
think would be appropriate for representing the destination address
(override)?

  reply	other threads:[~2016-12-03 22:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03 12:30 [PATCH " Christian Hesse
2016-12-03 12:42 ` [PATCH v2 " Christian Hesse
2016-12-03 22:21   ` Jason A. Donenfeld [this message]
2016-12-06  9:35     ` Christian Hesse
2016-12-06 18:14       ` Jason A. Donenfeld
2016-12-06 18:57         ` Jason A. Donenfeld
2016-12-06 20:15         ` Christian Hesse
2016-12-06 21:31           ` Jason A. Donenfeld

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='CAHmME9pAz1e2keE0vH-cWORP7pRmhfoivFt0_=_4xEH9xUjLDA@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=list@eworm.de \
    --cc=mail@eworm.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).