linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: latten@austin.ibm.com
To: davem@redhat.com, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: IPsecv6 integrity failures not dropped
Date: Fri, 18 Apr 2003 15:17:04 -0500	[thread overview]
Message-ID: <200304182017.h3IKH4ng019821@faith.austin.ibm.com> (raw)

I am running IPSecv6 on 2.5.67 with patch-2.5.67-bk8.

If AH authentication or ESP encryption integrity check for an 
incoming packet fails, result is an ICMPv6 Parameter problem 
of Unknown-Next-Header, instead of just dropping packet. This 
is because xfrm6_rcv() expects an unsigned-8-bit return value 
from the input handler, i.e. ah6_input() or esp6_input(). But handler 
returns a signed int (-EINVAL) that seems to be getting converted into 
a "u8" via 2's complement, because ah6_input() says it is returning
-EINVAL/-22, but xfrm6_rcv() says it got a return value of 234,
which it believes to be valid and passes to ip6_input() who thinks it is 
the next header.  

I modified ah6_input() and esp6_input() to return zero instead of -EINVAL
in the fix below. I tested it and it works.

Please let me know if this is ok. 

Joy
-------------------------------------------------------------------------

--- ah6.c.orig	2003-04-17 16:04:07.000000000 -0500
+++ ah6.c	2003-04-18 14:15:37.000000000 -0500
@@ -212,7 +212,7 @@
 free_out:
 	kfree(tmp_hdr);
 out:
-	return -EINVAL;
+	return 0;
 }
 
 void ah6_err(struct sk_buff *skb, struct inet6_skb_parm *opt, 
--- esp6.c.orig	2003-04-17 17:07:25.000000000 -0500
+++ esp6.c	2003-04-17 17:08:17.000000000 -0500
@@ -346,7 +346,7 @@
 	return ret_nexthdr;
 
 out:
-	return -EINVAL;
+	return 0;
 }
 
 static u32 esp6_get_max_size(struct xfrm_state *x, int mtu)

             reply	other threads:[~2003-04-18 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 20:17 latten [this message]
2003-04-18 21:10 ` IPsecv6 integrity failures not dropped David S. Miller
2003-04-19  2:12   ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-19  2:17     ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-19  2:50 ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-20  3:35   ` David S. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304182017.h3IKH4ng019821@faith.austin.ibm.com \
    --to=latten@austin.ibm.com \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).