From: Robert Love <rml@tech9.net>
To: elenstev@mesatop.com, esr@thyrsus.com
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: [PATCH] Configure.help: Bad URL for CONFIG_SYN_COOKIES
Date: 18 Aug 2001 02:50:05 -0400 [thread overview]
Message-ID: <998117417.2184.44.camel@phantasy> (raw)
The provided URL for more information re SYN Cookies is bad. I
originally posted a patch to fix this in the 2.4-pre series but it was
not merged. I am reposting because I was in need of the URL and again
got stuck on the stale URL in Configure.help.
This is against Configure.help 2.41, as in 2.4.8-ac7.
--- linux/Documentation/Configure.help~ Sat Aug 18 02:32:33 2001
+++ linux/Documentation/Configure.help Sat Aug 18 02:35:32 2001
@@ -2655,8 +2655,7 @@
continue to connect, even when your machine is under attack. There
is no need for the legitimate users to change their TCP/IP software;
SYN cookies work transparently to them. For technical information
- about SYN cookies, check out
- <ftp://koobera.math.uic.edu/syncookies.html>.
+ about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
If you are SYN flooded, the source address reported by the kernel is
likely to have been forged by the attacker; it is only reported as
@@ -2675,7 +2674,7 @@
at boot time after the /proc file system has been mounted.
- If unsure, say Y.
+ If unsure, say N.
HCI EMU (virtual device) driver
CONFIG_BLUEZ_HCIEMU
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next reply other threads:[~2001-08-18 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 6:50 Robert Love [this message]
2001-08-18 7:47 ` [PATCH] Configure.help: Bad URL for CONFIG_SYN_COOKIES Eric S. Raymond
2001-08-18 17:49 ` [PATCH] let Net Devices feed Entropy, updated (2/2) Robert Love
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=998117417.2184.44.camel@phantasy \
--to=rml@tech9.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=elenstev@mesatop.com \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.