netdev - Re: [PATCH] net: reflect the fwmark for replies with no socket

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: <20140317.145522.584337331452843243.davem@davemloft.net>
Date:	Mon, 17 Mar 2014 14:55:22 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	lorenzo@...gle.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] net: reflect the fwmark for replies with no socket

From: Lorenzo Colitti <lorenzo@...gle.com>
Date: Mon, 17 Mar 2014 14:24:57 +0900

> In general, that's true. Still - currently the mark on these packets
> is 0, period, and the administrator can't do anything about that at
> all. The idea was that some control is better than zero control, and
> since these packets are always in reply to other packets, then marking
> responses based on the packets that provoked them made sense, since
> the input marking can be as flexible as the administrator desires.

I do not agree with this assesment at all, a default of 0 is better
than an potentially undesirable default.

The incoming fwmark is controlled by external entities, and most people
are usually unhappy with external entities having influence upon their
machine's behavior.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html