From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Hairpin NAT - possible without packet marking?
Date: Tue, 4 Jul 2017 03:07:39 -0400 [thread overview]
Message-ID: <20170704030739.3746d533@playground> (raw)
In-Reply-To: <B3451526-9879-43F6-87BB-291E414AE43B@quintux.com>
On Tue, 04 Jul 2017 07:48:36 +0200
K <netfilter@quintux.com> wrote:
> What do all the locks in the world help when you invite the burglar in for tea? In other words: most IT departments have the incoming traffic pinned down as you described, but a single executable disguised as a clip of a cute kitty, downloaded and executed by any employee is what nowadays forms the real threat.
And that's why I maintain that SSL/TLS is the one of the worst things that could've happened to The Internet: our peripheral firewalls are powerless to prevent malware from traversing conns encrypted with SSL/TLS.
Neal
>
> On July 4, 2017 3:14:59 AM GMT+02:00, Robert White <rwhite@pobox.com> wrote:
> >They had
> >people sharing segments of their hard drives. Pooled servers with just
> >ludicrously broad write policies, printers, store and forward scanners,
> >all the normal stupid things that let business function. And you know,
> >what, its well they should. Security that becomes a denial of service
> >attack on the corporation's innards just encourages misuse.
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-07-04 7:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:55 Full NAT forward and source routing - possible without packet marking? Øyvind Kaurstad
2017-07-01 10:05 ` Pascal Hambourg
2017-07-01 20:26 ` Robert White
2017-07-01 22:17 ` zrm
2017-07-01 23:50 ` Robert White
2017-07-03 18:07 ` Hairpin NAT " zrm
2017-07-04 1:14 ` Robert White
2017-07-04 5:48 ` K
2017-07-04 7:07 ` Neal P. Murphy [this message]
2017-07-04 10:21 ` Robert White
2017-07-04 20:53 ` Pascal Hambourg
2017-07-04 21:20 ` Neal P. Murphy
2017-07-05 5:28 ` Robert White
2017-07-08 19:54 ` zrm
2017-07-08 21:55 ` Robert White
2017-07-02 7:29 ` Full NAT forward and source routing " Pascal Hambourg
2017-07-02 10:33 ` Robert White
2017-07-02 11:19 ` Pascal Hambourg
2017-07-02 15:58 ` Øyvind Kaurstad
2017-07-02 17:10 ` Pascal Hambourg
2017-07-02 23:20 ` Øyvind Kaurstad
2017-07-02 21:10 ` Robert White
2017-07-02 23:09 ` Øyvind Kaurstad
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=20170704030739.3746d533@playground \
--to=neal.p.murphy@alum.wpi.edu \
--cc=netfilter@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.