Signed-off-by: Jörg Thalheim
---
src/uapi.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/uapi.h b/src/uapi.h
index 6c6971e..69dfee3 100644
--- a/src/uapi.h
+++ b/src/uapi.h
@@ -113,7 +113,7 @@ struct wgpeer {
struct wgdevice {
char interface[IFNAMSIZ]; /* Get */
-
"Jason A. Donenfeld" writes:
> On Fri, Oct 21, 2016 at 5:02 PM, PaX Team wrote:
>> are you sure it was for satisfying PaX only and not a bug itself? :)
>
> Blurg. I was overly hasty. Note to self: do not prepare conf
> presentations and push code at the same time. Indeed this /should/ be
> ~0, w
On 21 Oct 2016 at 17:47, Jason A. Donenfeld wrote:
> On Fri, Oct 21, 2016 at 5:02 PM, PaX Team wrote:
> > are you sure it was for satisfying PaX only and not a bug itself? :)
>
> Blurg. I was overly hasty. Note to self: do not prepare conf
> presentations and push code at the same time. Indeed t
On Fri, Oct 21, 2016 at 5:02 PM, PaX Team wrote:
> are you sure it was for satisfying PaX only and not a bug itself? :)
Blurg. I was overly hasty. Note to self: do not prepare conf
presentations and push code at the same time. Indeed this /should/ be
~0, which means "unset". I can't see any bugs
On 21 Oct 2016 at 11:32, Jason A. Donenfeld wrote:
> On Fri, Oct 21, 2016 at 9:24 AM, PaX Team wrote:
> > in any case, whoever can reproduce this should print out the value of
> > head->mac_header before the increment. my guess based on past experience
> > on similar network problems is that the
