netdev - networking/ip-sysctl.txt: SRR or SSRR

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]

Message-ID: <alpine.DEB.2.20.12.1605081823420.3193@trent.utfs.org>
Date:	Sun, 8 May 2016 18:23:59 -0700 (PDT)
From:	Christian Kujau <lists@...dbynature.de>
To:	netdev@...r.kernel.org
Subject: networking/ip-sysctl.txt: SRR or SSRR

In Documentation/networking/ip-sysctl.txt, the accept_source_route 
parameter is described with:

  Accept packets with SRR option.

I could not find anything describing an "SRR option". The closest thing 
was something called "SSR - Strict Source Route"[0] - is that what is 
meant here? If so, RFC791 then refers to the same as "SSRR", as in "strict 
source and record route". Does the patch below clears that up or did I 
confuse it with something else?

Thanks,
Christian.

Signed-off-by: Christian Kujau <lists@...dbynature.de>

diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index b183e2b..db6b538 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -1057,9 +1057,9 @@ bootp_relay - BOOLEAN
 	Not Implemented Yet.

 accept_source_route - BOOLEAN
-	Accept packets with SRR option.
+	Accept packets with SSRR option (RFC791 3.1).
 	conf/all/accept_source_route must also be set to TRUE to accept packets
-	with SRR option on the interface
+	with SSRR option on the interface
 	default TRUE (router)
 		FALSE (host)

[0] https://www.iana.org/assignments/ip-parameters/ip-parameters.xhtml
-- 
BOFH excuse #224:

Jan  9 16:41:27 huber su: 'su root' succeeded for .... on /dev/pts/1