netdev - [PATCH v3 net-next 0/2] Use correct sk->sk

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-next>] [day] [month] [year] [list]

Date:   Mon,  4 Sep 2017 13:13:59 +0300
From:   Ilya Lesokhin <ilyal@...lanox.com>
To:     netdev@...r.kernel.org, davem@...emloft.net
Cc:     davejwatson@...com, aviadye@...lanox.com,
        Ilya Lesokhin <ilyal@...lanox.com>
Subject: [PATCH v3 net-next 0/2]  Use correct sk->sk_prot for IPV6                

The tls ulp overrides sk->prot with a new tls specific proto structs.            
The tls specific structs were previously based on the ipv4 specific              
tcp_prot sturct.                                                                 
As a result, attaching the tls ulp to an ipv6 tcp socket replaced                
some ipv6 callback with the ipv4 equivalents.                                    
                                                                                 
This patch adds ipv6 tls proto structs and uses them when                        
attached to ipv6 sockets. 

Changed since v2: 
- Dropped patch to fix IPV6_ADDRFORM setsockopt
There was some disagreement about the correct way of fixinig it,
and this series does not depend on it.

Changes since v1:                                                                
- TLS now dependes on IPV6                                                       
This fixes complication issues when TLS is built-in and IPV6 is a module.        
The downside should be small as it is unlikely that there are kernel TLS         
users who can't afford to include IPV6 in thier kernel.                          
- tls_init now checks sk->sk_prot directly                                       
This is somewhat safer then checking indirectly through sk->sk_family       

Ilya Lesokhin (2):
  net: Export tcpv6_prot
  tls: Use correct sk->sk_prot for IPV6

 net/ipv6/tcp_ipv6.c |  1 +
 net/tls/Kconfig     |  1 +
 net/tls/tls_main.c  | 50 ++++++++++++++++++++++++++++++++++++++------------
 3 files changed, 40 insertions(+), 12 deletions(-)

-- 
1.8.3.1