From: Johannes Frandsen <jsf@imento.dk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Gentoo as a production server - insecure?
Date: Mon, 16 Feb 2009 13:48:04 +0100 [thread overview]
Message-ID: <CB457718-33A0-4A93-9961-0ED60D4F8A55@imento.dk> (raw)
In-Reply-To: <200902161326.07025.shrdlu@unlimitedmail.org>
I got in to a discussion about which server to recommend for running
the php5 symfony framework, and I recommended Gentoo as I had been
using it my self for a couple of years and have been very satisfied
with it.
Somebody pointed out that having a productions server with a gcc
installed was a big no no security wise, so I did a bit of goggling on
that topic and found a couple of articles supporting that view.
Maybe I'm just ill informed, but I can't really see the big problem
here. Sure if there is a gcc compiler installed you can recompile
everything to your hearts content, but you still need to get access to
the server first. And if you have server access you can install gcc on
any distribution. Even openbsd (to my knowledge) comes with gcc
bundled and they claim to be the most secure *nix available.
Im using the gentoo hardened profile for my production servers with a
lamp stack and have considered them reasonably secure, but am I wrong
in assuming this?
Joe
next prev parent reply other threads:[~2009-02-16 12:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 12:05 [gentoo-user] Mailing Lists Kaushal Shriyan
2009-02-16 12:26 ` Etaoin Shrdlu
2009-02-16 12:48 ` Johannes Frandsen [this message]
2009-02-16 13:50 ` [gentoo-user] Gentoo as a production server - insecure? Mike Kazantsev
2009-02-16 14:27 ` Mick
2009-02-16 15:51 ` [gentoo-user] " James
2009-02-16 22:36 ` Neil Bothwick
2009-02-20 8:36 ` Mick
2009-02-16 17:33 ` [gentoo-user] " Dirk Heinrichs
2009-02-16 20:15 ` [gentoo-user] " james
2009-02-16 20:27 ` Matt Harrison
2009-02-16 20:33 ` Dirk Heinrichs
2009-02-16 21:35 ` James
2009-02-16 15:11 ` [gentoo-user] Mailing Lists Dan Cowsill
2009-02-16 16:35 ` Hilco Wijbenga
2009-02-17 14:06 ` Dan Cowsill
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=CB457718-33A0-4A93-9961-0ED60D4F8A55@imento.dk \
--to=jsf@imento.dk \
--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