linux-kernel - Re: Feedback on TCP: Make TCP_RTO

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <485618F1.8020801@davidnewall.com>
Date:	Mon, 16 Jun 2008 17:10:33 +0930
From:	David Newall <davidn@...idnewall.com>
To:	Chris Fowler <cfowler@...postsentinel.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-net@...r.kernel.org
Subject: Re: Feedback on TCP: Make TCP_RTO_MAX a variable

Chris Fowler wrote:
> My only question would be that if you did not have this feature how
> would you have solved your problem?


I have no idea.  An option would be to use private managed links, but
that would cost about 100 times as much, and I would not be able to
administer the machines via the internet.

With programs that scan and probe the internet, widely available for
every script-kiddies entertainment, I believe this is, as I said, a
standard characteristic of the internet, and I must live with it.  Had
this been an actual DOS attack on my client, rather than the normal,
random attention from said script-kiddies, reducing TCP_RTO_MAX would
not have helped.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/