From: Greg KH <gregkh@linuxfoundation.org>
To: John Wayne <matrixman3077@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard backport to 2.6.3x kernels
Date: Wed, 31 Jan 2018 10:03:19 +0100 [thread overview]
Message-ID: <20180131090319.GA7820@kroah.com> (raw)
In-Reply-To: <CACwd1hYUb0aGFOQoDY30a0Gsu2E-OaSHF0319x-kGbTSwov9Hg@mail.gmail.com>
On Wed, Jan 31, 2018 at 10:44:39AM +0200, John Wayne wrote:
> Hi,
>
> I am working on a project that involves some old MIPS and ARM based
> custom boards.
> Current SDKs for these boards are pretty messy and there is no
> documentation about the
> patches that were applied to the 2.6.3x kernels in order make them
> work on these boards.
You can always just diff against the kernel.org release to see that.
> So my question is how painfully will it be to port wireguard to the
> even more ancient 2.6.3x kernels?
You shouldn't be running any device based on those old kernels exposed
to the network as they are probably totally insecure. Instead work on
updating the kernel to something that was at least released in the past
5 years.
Wireguard support is the least of your problems here :)
good luck!
greg k-h
next prev parent reply other threads:[~2018-01-31 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:44 John Wayne
2018-01-31 9:03 ` Greg KH [this message]
2018-01-31 14:23 ` 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=20180131090319.GA7820@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=matrixman3077@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).