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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 23 Jul 2007 00:31:19 +0900 (JST)
From:	Ken-ichirou MATSUZAWA <>
Subject: Re: checksum of lsrr


From: Ken-ichirou MATSUZAWA <>
Subject: checksum of lsrr
Date: Wed, 04 Jul 2007 22:28:24 +0900 (JST)

> if we change destination address, we need recompute not only ip
> checksum but also tcp's, don't we? 

I was ashamed of myself for much confused. My simple story is:

	rt1 ---- rt2 ---- mybox

rt1 is far from rt2 and when I changed bandwith between rt1 and rt2,
I want to confirm if it was changed correctly. A idea occured to me
is using lsrr. Then I tried with nc but it was not worked. To accept
packet from rt2 to mybox which src and dst address are mybox, I

--- net/ipv4/fib_frontend.c.orig	2007-07-23 00:01:17.000000000 +0900
+++ net/ipv4/fib_frontend.c	2007-07-23 00:03:11.000000000 +0900
@@ -206,7 +206,7 @@
 	if (fib_lookup(&fl, &res))
 		goto last_resort;
-	if (res.type != RTN_UNICAST)
+	if (res.type != RTN_UNICAST && likely(res.type != RTN_LOCAL))
 		goto e_inval_res;
 	*spec_dst = FIB_RES_PREFSRC(res);
 	fib_combine_itag(itag, &res);

Would you tell me is this acceptable? I'm afraid of security issue.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists