From: "David S. Miller" <davem@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: nakam@linux-ipv6.org, netdev@oss.sgi.com,
usagi-core@linux-ipv6.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH][IPSEC] IPsec policy can be matched by ICMP type and code
Date: Wed, 11 Aug 2004 13:30:43 -0700 [thread overview]
Message-ID: <20040811133043.455c81fa.davem@redhat.com> (raw)
In-Reply-To: <OF94FC19D3.2EA706DF-ON88256EED.006875F7-88256EED.006980E7@us.ibm.com>
On Wed, 11 Aug 2004 13:14:19 -0600
David Stevens <dlstevens@us.ibm.com> wrote:
> raw sockets predate VJ contributions by many years and are
> typically used by protocols not in the kernel. The original "ping"
> used raw sockets, as well as routing protocols like BGP and RIP
> which are directly encapsulated in IP, without a separate transport
> protocol. The original traceroute I believe used UDP and just set
> the TTL-- I don't believe it used raw sockets at all. Don't know what
> the current versions do; haven't looked in a while.
"ping" does not use the hdrinclude feature.
> And IPv6 does support raw sockets; it just doesn't let you
> generate bad checksums and some header fields, I expect
> to make it harder to write attack software.
So like I said, raw without the hdrinclude feature.
next prev parent reply other threads:[~2004-08-11 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 8:54 [PATCH][IPSEC] IPsec policy can be matched by ICMP type and code Masahide Nakamura
2004-08-09 9:03 ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-10 0:07 ` David S. Miller
2004-08-10 1:32 ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-11 6:01 ` David S. Miller
2004-08-11 19:14 ` David Stevens
2004-08-11 20:30 ` David S. Miller [this message]
2004-08-18 14:09 ` [PATCH] XFRM: ICMP{,v6} type/code support (Take 2) (was Re: [PATCH][IPSEC] IPsec policy can be matched by ICMP type and code) YOSHIFUJI Hideaki / 吉藤英明
2004-08-18 22:24 ` 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=20040811133043.455c81fa.davem@redhat.com \
--to=davem@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=nakam@linux-ipv6.org \
--cc=netdev@oss.sgi.com \
--cc=usagi-core@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.org \
/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).