netdev - Re: [PATCH net-2.6.23 take2] UDP: Cleanup UDP encapsulation code

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 for Android: free password hash cracker in your pocket

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

Message-ID: <468D299E.5070902@katalix.com>
Date:	Thu, 05 Jul 2007 18:25:50 +0100
From:	James Chapman <jchapman@...alix.com>
To:	Rémi Denis-Courmont <rdenis@...phalempin.com>
CC:	netdev@...r.kernel.org, remi.denis-courmont@...ia.com
Subject: Re: [PATCH net-2.6.23 take2] UDP: Cleanup UDP encapsulation code

Rémi Denis-Courmont wrote:

> By the way, couldn't encap_type be remove altogether (using two slightly 
> different callbacks for ESP) from udp_sock?

The notion of encap_type is needed for the setsockopt call so it would 
have to stay in the API. If it were removed from udp_sock, getsockopt 
would have to derive the encap_type from encap_rcv funcptr values, which 
would be messy. I think it might complicate the logic in ESP too.

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development

-
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