Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752056AbbKIRXx (ORCPT ); Mon, 9 Nov 2015 12:23:53 -0500 Received: from tschil.ethgen.ch ([5.9.7.51]:57312 "EHLO tschil.ethgen.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751892AbbKIRXw (ORCPT ); Mon, 9 Nov 2015 12:23:52 -0500 Date: Mon, 9 Nov 2015 18:23:43 +0100 From: Klaus Ethgen To: Austin S Hemmelgarn Cc: "Serge E. Hallyn" , "Theodore Ts'o" , Andy Lutomirski , Linus Torvalds , Richard Weinberger , LKML , Christoph Lameter , Andy Lutomirski , Serge Hallyn , Kees Cook , Andrew Morton Subject: Re: [KERNEL] Re: Kernel 4.3 breaks security in systems using capabilities Message-ID: <20151109172340.GF3714@ikki.ethgen.ch> Mail-Followup-To: Austin S Hemmelgarn , "Serge E. Hallyn" , Theodore Ts'o , Andy Lutomirski , Linus Torvalds , Richard Weinberger , LKML , Christoph Lameter , Andy Lutomirski , Serge Hallyn , Kees Cook , Andrew Morton References: <20151105173438.GA3378@mail.hallyn.com> <20151105174823.GD9307@ikki.ethgen.ch> <20151105220843.GA6027@mail.hallyn.com> <20151106135835.GB11901@ikki.ethgen.ch> <20151106155303.GB6160@thunk.org> <20151106175619.GA19491@ikki.ethgen.ch> <20151106181820.GB16749@mail.hallyn.com> <20151107110246.GA7230@ikki.ethgen.ch> <5640C999.5050807@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; x-action=pgp-signed In-Reply-To: <5640C999.5050807@gmail.com> OpenPGP: id=79D0B06F4E20AF1C; url=http://www.ethgen.ch/~klaus/79D0B06F4E20AF1C.txt; preference=signencrypt User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4082 Lines: 92 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am Mo den 9. Nov 2015 um 17:28 schrieb Austin S Hemmelgarn: > >Having some scripts in the process is definitively a nightmare to > >control. That should be prevented wherever possible. And usually it is > >as the scripts might be used for computing some values that are used > >later in privileged stuff. > It's still unavoidable in a number of cases. It's easy to re-write scripts > to fit any local configuration. It's not anywhere near as easy to re-write > a compiled program to account for any local configuration. I would not only say that it is avoidable, it is the worst that can happen. Usually a shell is calling a binary to do the real work. So it should even never ever needed to have some raised privileges for the shell. > >Good example are all that userspace python tools that throw all that > >stack traces around the users ears (I don't know if that saying exists > >in English...) instead of giving proper error messages. > This is debatable. While the app should be giving a user friendly error > message, getting a stack-trace and the exception name (and the exceptions > are usually sanely named) is still far better than just getting something > like 'Segmentation Fault', or just returning the error in the return code. > There is no added security from not providing the stack-trace because there > is no data leaked by it (it contains no information about the contents of > variables, and function names and included libraries can easily be seen by > just looking at the python program itself). My pointing to that python problem is not about security then about how lazy some developer are. And lazyness and security is nothing that can go together. > >By the way, guys, can we start to _not_ add every one in this discussion > >to the Cc? Currently I get every mail twice. One from the list and one > >from Cc. I still leave all Ccs intact with this mail but I would prefer > >to just reply to the list. If anybody is not reading the list and would > >like to get the mail, please insist. > If you're getting duplicates with the same Message-ID header, then your > mail-server is (arguably) broken. I do not know any mailserver that cares about message-ids. Even more, which one is the original one if they differ in body? (as they do for example in this list.) It it even more broken as some (surely broken) MUAs reuse message ids. > It should be delivering exactly one copy of a message with a given > Message-ID: header (this is really a de-facto standard, I wouldn't say so. > GMail, Yahoo, and most other mail-providers do this, as does > Exchange. I would say, they are broken as they suppress users data. > Postfix does not, but it's pretty easy to work around with some > filtering and procmail). Well, pestfix dos it right here. A MTA has to transport the mails and never ever suppress some. But lets keep that stuff offlist, it is OT. I will go ahead with group reply. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQGcBAEBCgAGBQJWQNaJAAoJEKZ8CrGAGfasC9UL/3ipt684NO2m5P6YLjrLGqPY 9TnEJz4ks0uKJsOPMXX7v54eUG6Jv0o1uj28aI/pcFxszBRALLpar2TAuAz6dWID 0hhB2kt/3TaEV00aOP5fzl/BzjwozxYiavYri10B4xqbLOtJEpKgCWNhLpMdEqGO ksgSx/Qqo+lB49uTjueC63Z3dU4T1CL6+iUbPx6MeLURGI1rYn4yye6n33AlceEL /y5jEfscxl9htAtC6O9DJHGp6EgN1Yc7rXdSIYVNqXt3GKTAnfmeVlnt8EO+kOmg zA2fzIXMvt2ZIOWF6TCCSE9tghuFY6S2gnVpmwR0m02JqD+vTarlbzldeDbsI+bg avcEAdmGBfMf1WibAHAazt/GUVMKaMw5rPhj7nXrv5rx+x6NvjNoY1aBb8yEbGjR nvNOcHp6tbMJuBHBWBwtcV1HJafvNm8GzhAVYwQf0efJY4x46E2xDfgaS4hgXvEN yhtGkX5OEVaEvixB2Lkt37UUF8Ix3kqMweW7+sp5vw== =nlsD -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/