From: Kevin Chadwick <ma1l1ists@yahoo.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [Bulk] Re: [gentoo-user] How to prevent a dns amplification attack
Date: Sat, 30 Mar 2013 15:11:17 +0000 [thread overview]
Message-ID: <20130330151117.542b249b@kc-sys.chadwicks.me.uk> (raw)
In-Reply-To: <9E829B28-D041-488B-BD22-3E25E6E51A35@smash-net.org>
On Sat, 30 Mar 2013 13:06:16 +0100
Norman Rieß <norman@smash-net.org> wrote:
> As we all know everything works better and cheaper when things are
> privatized
Actually No it's not so simple at all.
You get incompetence in private and public and you may be more likely
to get away with it for longer in a public service than in a market with
competition but there are many examples where things simply get worse.
In the UK, water companies were privatisied and fat cats made lots of
money letting the pipes deteriorate for future generations.
British Telecom, well that's a mixed bag but it is certainly a
tiny shadow of it's original self.
We know ideals and theory hardly ever work but theoretically public
should be much better when well managed.
I wonder if ISPS wouldn't be handling things like TalkTalks
Homesafe in such a stupid manner (across the board is where it is
stupid, even for non users of the service) where they redirect all the
http traffic through an undoubtedly insecure layer 7 handling huawei
device with less commercial pressures or analysing bandwidth at layer
7 when they should be doing so more safely and completely at layers 3
and 4 leading me to believe they are not just thinking about bandwidth
usage. Why does it matter if you download 1000Gb via torrents or http.
ACKs can be managed in any case.
I'm glad open source is beginning to make strides into public services
as it should help put an end to expensive interoperability issues (if
we stay away from non posix things like systemd, though even then
shouldn't be too bad ;-)).
next prev parent reply other threads:[~2013-03-30 15:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 8:51 [gentoo-user] How to prevent a dns amplification attack Norman Rieß
2013-03-28 9:07 ` Adam Carter
2013-03-28 22:16 ` Norman Rieß
2013-03-28 15:12 ` Volker Armin Hemmann
2013-03-28 20:51 ` Kevin Chadwick
2013-03-28 20:57 ` Kevin Chadwick
2013-03-28 21:04 ` Michael Mol
2013-03-28 22:36 ` Kevin Chadwick
2013-03-28 15:38 ` Michael Mol
2013-03-28 16:06 ` Pandu Poluan
2013-03-28 16:10 ` Michael Mol
2013-03-28 18:26 ` Norman Rieß
2013-03-28 19:16 ` Alan McKinnon
2013-03-28 19:38 ` Michael Mol
2013-03-28 20:02 ` Alan McKinnon
2013-03-28 20:53 ` Paul Hartman
2013-03-28 20:59 ` Michael Mol
2013-03-29 0:49 ` Peter Humphrey
2013-03-29 8:53 ` Norman Rieß
2013-03-29 13:27 ` Alan McKinnon
2013-03-29 13:36 ` Michael Mol
2013-03-29 22:34 ` Paul Hartman
2013-03-29 23:01 ` William Kenworthy
2013-03-29 23:09 ` Michael Mol
2013-03-30 4:07 ` Walter Dnes
2013-03-30 12:06 ` Norman Rieß
2013-03-30 14:53 ` Rene Rasmussen
2013-03-30 15:15 ` [Bulk] " Kevin Chadwick
2013-03-30 15:30 ` Tanstaafl
2013-03-30 15:11 ` Kevin Chadwick [this message]
2013-03-30 16:44 ` Norman Rieß
2013-03-30 17:30 ` [gentoo-user] Re: [seriously O/T] " Mick
2013-03-29 13:24 ` [gentoo-user] " Alan McKinnon
2013-03-28 16:53 ` Jarry
2013-03-28 19:40 ` Paul Ezvan
2013-03-31 2:08 ` Paul Hartman
2013-03-31 8:47 ` Jarry
2013-03-31 19:07 ` Norman Rieß
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=20130330151117.542b249b@kc-sys.chadwicks.me.uk \
--to=ma1l1ists@yahoo.co.uk \
--cc=gentoo-user@lists.gentoo.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