public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Nicolas Sebrecht <nicolas.s-dev@laposte.net>,
	Nicolas Sebrecht <nsebrecht@piing.fr>
Subject: Re: [gentoo-user] Re: Fwd:How about the gentoo server or cluster in production environment?
Date: Fri, 21 Feb 2014 15:16:54 +0400	[thread overview]
Message-ID: <20140221151654.a7e7fcc99c06062666740892@gmail.com> (raw)
In-Reply-To: <20140220204103.GA3381@vidovic.ultras.lan>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Thu, 20 Feb 2014 21:41:03 +0100 Nicolas Sebrecht wrote:
> On Thu, Feb 20, 2014 at 08:52:07PM +0400, Andrew Savchenko wrote:
> 
> > And this point is one of the highest security benefits in real world:
> > one have non-standard binaries, not available in the wild. Most
> > exploits will fail on such binaries even if vulnerability is still
> > there. 
> 
> While excluding few security issues by compiling less code is possible,
> believing that "non-standard binaries" (in the sense of "compiled for
> with local compilation flags") gives more security is a dangerous dream.

Any decent security setup contains multiple layers of protection.
Use of non-standard binaries, algorithms or implementations is just
one of them and it is the simplest math to prove that security is
_improved_ this way. Nobody says that system became _acceptably_
secure _only_ by using this techniques.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-02-21 11:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5297F0C8.3060403@gmail.com>
2014-02-19 23:40 ` [gentoo-user] Fwd: How about the gentoo server or cluster in production environment? Franklin Wang
2014-02-20  0:14   ` Nilesh Govindrajan
2014-02-20  0:36     ` Franklin Wang
2014-02-20  0:53       ` Facundo Curti
2014-02-20  1:06         ` Nilesh Govindrajan
2014-02-20  1:17         ` Franklin Wang
2014-02-20  9:28         ` thegeezer
2014-02-20 12:04         ` Tanstaafl
2014-02-20 12:24           ` Tanstaafl
2014-02-21  1:03           ` Facundo Curti
2014-02-21  1:39             ` Nilesh Govindrajan
2014-02-21 13:49             ` Tanstaafl
2014-02-27 13:09       ` Nick Cameo
2014-02-27 17:53         ` Facundo Curti
2014-03-21 13:37           ` Tom Wijsman
2014-02-20 10:29     ` [gentoo-user] Re: Fwd:How " Nicolas Sebrecht
2014-02-20 16:52       ` Andrew Savchenko
2014-02-20 20:41         ` Nicolas Sebrecht
2014-02-20 20:59           ` Alan McKinnon
2014-02-21 12:39             ` Andrew Savchenko
2014-02-26 11:44               ` Nicolas Sebrecht
2014-02-21 14:15             ` hasufell
2014-02-22  8:28               ` Alan McKinnon
2014-02-26 15:02                 ` hasufell
2014-02-26 10:55               ` Nicolas Sebrecht
2014-02-26 14:05                 ` Poison BL.
2014-02-26 15:03                 ` hasufell
2014-02-26 15:26                   ` Nicolas Sebrecht
2014-02-27  1:05                     ` hasufell
2014-02-21 11:16           ` Andrew Savchenko [this message]
2014-02-26 10:51             ` Nicolas Sebrecht
2014-02-20 14:35   ` [gentoo-user] Fwd: How " Andrew Savchenko
2014-02-21  7:35     ` Franklin Wang
2014-02-20 18:41   ` Andreas K. Huettel
2014-02-21  7:40     ` Franklin Wang

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=20140221151654.a7e7fcc99c06062666740892@gmail.com \
    --to=bircoph@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=nicolas.s-dev@laposte.net \
    --cc=nsebrecht@piing.fr \
    /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