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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Thu, 7 Aug 2014 12:48:14 +0400
From:	Aleksey Midenkov <>
Subject: TCP ISN from userlevel

Expansion of Linux Kernel API for getting from userlevel TCP ISN by
socket descriptor. Would such improvement deserve merge? The use case
is to differ hosts behind NAT. The general plan of changes:

1. copy ISN into the tcp_sock structure when the TCP session is created;
2. add ioctl for getting ISN;
2.  copy that value into the tcp_info structure returned by getsockopt().

I see that 'snt_isn' and 'rcv_isn' are stored in 'tcp_request_sock'.
Is 'tcp_request_sock' have the lifetime of 'tcp_sock'? I.e. can it be
always accessed via 'fastopen_rsk'?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists