public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Harrison <iwasinnamuknow@genestate.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Gentoo as a production server - insecure?
Date: Mon, 16 Feb 2009 20:27:37 +0000	[thread overview]
Message-ID: <4999CC39.1050502@genestate.com> (raw)
In-Reply-To: <loom.20090216T200745-518@post.gmane.org>

james wrote:
> Dirk Heinrichs <dirk.heinrichs <at> online.de> writes:
>
>
>   
>> would you please be so kind and avoid hijacking other threads next time.
>>     
>
> Um, you must not have read the response.
>
> I did specifically address and provide remedy if indeed having gcc
> installed on a machine is a security threat. 
>
> Sure I expounded on the whole concept of security, because one
> of the most important aspect of any or all security is a measure
> of reasonableness and sufficiency. There are many instances, imho,
> that overkill for security is applied and often does not work,
> such as removing gcc from a system. A good hacker (security interloper)
> can patch a system without ever compiling anything on that system....
>
>
> Your opinion that I hijacked a thread is, well, your opinion, at best.
>
>
> Ignore what you do not like, or give a more singularly focused response,
> if you deem that necessary, but avoid pissing into a fan and telling 
> the rest of us how cool and relevant you are.
>
> After all, you did not even respond with any relevance to what the poster
> was look for, did you ? (your just another pompous a.....)....
>
>
> hth,
> James
>
>
>
>
>   
Actually Dirk wasn't talking to you at all, he was talking to the person 
that did indeed hijack the thread (titled "Mailing Lists") by replying 
to it with an unrelated email (titled "Gentoo as a production server - 
insecure?"). This was a valid point, as it was thread hijacking and it 
does make threads very difficult to manage.

It does not however make it so difficult to manage that you cannot see 
Dirk replied to the original hijacking email, and not to you.

Now lets all kiss and make up :)

Matt



  reply	other threads:[~2009-02-16 20:27 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   ` [gentoo-user] Gentoo as a production server - insecure? Johannes Frandsen
2009-02-16 13:50     ` 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 [this message]
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=4999CC39.1050502@genestate.com \
    --to=iwasinnamuknow@genestate.com \
    --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