netdev - Re: [PATCH V3 net-next] LISP: Locator/Identifier Separation Protocol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+mtBx9_BXJqEdh-5xKZhhNMgtHXtqaKDm5VGvEjUk+ubb1=fQ@mail.gmail.com>
Date:	Thu, 19 Jun 2014 10:29:20 -0700
From:	Tom Herbert <therbert@...gle.com>
To:	Christopher White <chris@...icalelegance.com>
Cc:	Linux Netdev List <netdev@...r.kernel.org>,
	"Vina Ermagan (vermagan)" <vermagan@...co.com>,
	"Lorand Jakab -X (lojakab - M SQUARED CONSULTING INC. at Cisco)" 
	<lojakab@...co.com>
Subject: Re: [PATCH V3 net-next] LISP: Locator/Identifier Separation Protocol

>> I was actually thinking this function could be even more general. The
>> L2TP_ENCAPTYPE_UDP case in l2tp_tunnel_sock_create looks like
>> something we might be able to abstract out into a separate function--
>> it would include IPv6 support and the possibility of binding to other
>> than INADDR_ANY and connected sockets. l2tp_tunnel_cfg could be the
>> basis of udp_port_cfg which contains addresses, ports, and sockopts
>> like sk_no_check_tx…
>>
>
> So I’m happy to do this, but I would like to do it in a separate submission.
> For one thing, I am not super familiar with that code and I’m a bit nervous
> about making substantive changes, thus it may take me some time.
> As it is orthogonal to the LISP submission, would it be possible to do this
> separately and have LISP move forward?
>
Okay, I'll post an implementation of the general function once
net-next opens up.

> Thanks!
> -Chris
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html