On Sun, May 14, 2017 at 11:55:52AM +0200, Baptiste Jonglez wrote:
> On Sun, May 14, 2017 at 12:52:11AM +0200, Jason A. Donenfeld wrote:
> > One small and unfortunate thought just occurred to me: the backporting
> > to really old kernels I'm pretty sure is way less efficient than newer
> > kernels
On Tue, Oct 10, 2017 at 01:19:45AM +0200, Jason A. Donenfeld wrote:
> Hey folks,
>
> A few friends asked if I'd do a meticulous read through and
> explanation, in person, of every line of the relatively short
> WireGuard code base. We had done this at some point in 2015, before
> the project was
On Tue, Oct 10, 2017 at 01:19:45AM +0200, Jason A. Donenfeld wrote:
> Hey folks,
>
> A few friends asked if I'd do a meticulous read through and
> explanation, in person, of every line of the relatively short
> WireGuard code base. We had done this at some point in 2015, before
> the project was
On Thu, Nov 16, 2017 at 11:04:49AM +0100, d...@fastmail.fm wrote:
> Hi,
>
> Is there a way to disable ipv6 when using wg-quick?
>
> If I have the following line on my conf file:
>
> Address = xx.xx.x.39/32,::xxx:bb01::327/128
>
> wg-quick will fail with the following error:
>
> ~ 2
On Wed, Nov 15, 2017 at 04:18:54PM +0100, Jason A. Donenfeld wrote:
> Hey folks,
>
> One of the strengths of WireGuard is its visibility. wg(8) is a tiny tool
> that's easy to use, and you can configure and reconfigure everything at
> runtime, examining the current configuration, and doing other
On Mon, Nov 06, 2017 at 09:41:18PM +, Ferris Ellis wrote:
> Hello Wireguard mailing list!
>
> I have been very interested in the WireGuard project for a little while now
> and am in the process of evaluating it. While benchmarks and code reviews
> are useful, they don’t uncover many of the
On Fri, Jun 15, 2018 at 04:27:09PM -0400, Glen Bojsza wrote:
> I am trying to run wireguard server on Bionic ARM processor.
>
> After following the installation instructions and creating my server config
> file I get the following error when I run
>
> root@odroidxu4:~# wg-quick up wg0
>
>
On Wed, Jun 13, 2018 at 03:54:24PM +0100, Paul Hedderly wrote:
> On Wed, 2018-06-13 at 15:52 +0200, Jason A. Donenfeld wrote:
> > Hi Paul,
> >
> > I got an -rt kernel up and running, enabled a bunch of nice debugging
> > options, and found a handful of problems, all of which were fixed by:
> >
On Thu, Jan 18, 2018 at 04:42:10PM +0100, Jason A. Donenfeld wrote:
> Hi folks,
>
> Writing crypto code is hard and sometimes scary. Especially on things
> like elliptic curves and big number arithmetic, subtle but critical
> bugs often sit around undetected for years. For this reason, I've been
On Tue, Jan 30, 2018 at 09:38:59AM -0600, Bruno Wolff III wrote:
> While there were a few other warnings about sibling call from callable
> instruction with modified stack frame, the following looked more significant
> if it isn't a gcc bug.
> CC [M]
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
On Mon, Jul 30, 2018 at 11:34:31AM +0800, Yousong Zhou wrote:
> On Mon, 30 Jul 2018 at 11:29, Jason A. Donenfeld wrote:
> >
> > Update to the latest available centos kernel in the latest available
> > centos release, and then after install WireGuard. If you're facing
> > problems then, email a
On Mon, Jan 22, 2018 at 03:42:25PM +0100, Kevin wrote:
> Hi all,
>
> I've been having trouble building WireGuard on Solus since its December
> snapshots. Earlier snapshots (e.g. November) still build without a
> problem, even on new kernels. Does this have to do with Solus kernel
> builds, or am
On Wed, Apr 17, 2019 at 01:02:36PM +0530, bhashkar prakash Singh wrote:
> Hi,
>
> I want to integrate Wireguard to my confidential project. I see Wireguard
> source code is under GPLv2, if I add any patch to Wiregaurd source code to
> work with my confidentail project, do I need to publish
On Tue, May 14, 2019 at 11:11:52AM +0200, Rene 'Renne' Bartsch, B.Sc.
Informatics wrote:
> Hi,
>
> it seems activities adding Wireguard to the Linux kernel have stopped
> because of lack of audits and cryptographic weakness tests.
That is not why it has stopped.
> I suggest to offer adding
On Sun, Mar 29, 2020 at 08:16:43PM -0600, Jason A. Donenfeld wrote:
> Hi folks,
>
> Earlier this evening, Linus released [1] Linus 5.6, which contains our
> first release of WireGuard. This is quite exciting. It means that
> kernels from here on out will have WireGuard built-in by default. And
>
On Sun, Dec 13, 2020 at 03:58:20PM +0100, Miguel Ojeda wrote:
> > The key here is "if nobody complains". I would argue that it is _your_
> > responsibility to do those builds, and not the reponsibility of others
> > to do it for you.
>
> Testing allmodconfig for a popular architecture, agreed, it
On Tue, Nov 10, 2020 at 01:29:41PM +0100, Jason A. Donenfeld wrote:
> Note that this requires
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=46d6c5ae953cc0be38efd0e469284df7c4328cf8
> And that commit should be backported to every kernel ever, since the
> bug is so
On Thu, Jun 30, 2022 at 09:49:24PM +0200, Jason A. Donenfeld wrote:
> Hi Kalesh,
>
> On Thu, Jun 30, 2022 at 07:12:29PM +, Kalesh Singh wrote:
> > Systems that initiate frequent suspend/resume from userspace
> > can make the kernel aware by enabling PM_USERSPACE_AUTOSLEEP
> > config.
> >
> >
19 matches
Mail list logo
