From: Jonny Kent <jonnykent@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Security updates
Date: Thu, 21 Jan 2010 22:36:19 -0800 [thread overview]
Message-ID: <72bf0ae51001212236l22c59bacx66b9f903bbdcec7e@mail.gmail.com> (raw)
In-Reply-To: <5D030B24B210824291B610C6C08E8F58E146581797@BOW-EVS-V01.uoc.local>
[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]
As well as all the good suggestions others have made, consider using a cron
job to run a glsa check daily after updating portage.
# glsa-check -t all
That will email you indications of security issues specifically affecting
your systems as configured.
On Thu, Jan 21, 2010 at 4:19 AM, Machell, Jonathan <
Jonathan.Machell@cumbria.ac.uk> wrote:
> Hello there,
>
> We're currently trialling Gentoo to possibly host some of our web-servers.
> I've used Gentoo for over eight years so I'm leading these trials.
>
> I've subscribed to this mailing list but also gentoo-server and
> gentoo-security. I'm trying to keep up to speed with all the latest security
> news affecting Gentoo, GNU/Linux, Apache and MySQL. Should subscription to
> these mailing lists be sufficient for this or is there any other place where
> I should be looking to keep on top of security issues? I'm aware that this
> and the other two mailing lists are low traffic but I haven't heard a peep
> since subscribing on Tuesday. Is that normal? I was hoping to go through the
> archives of previous messages at some point. Are these kept somewhere?
>
> Many thanks,
>
> Jonathan Machell
> University of Cumbria is a Company Limited by Guarantee, Registered in
> England & Wales No. 06033238. Registered Office: University of Cumbria,
> Fusehill Street, Carlisle, CA1 2HH. Telephone 01228 616234.
>
> Confidentiality: This email and its attachments are intended for the above
> named only and may be confidential. If they have come to you in error you
> must take no action based on them, nor must you copy or show them to anyone;
> please reply to this email and highlight the error.
>
> Security Warning: Please note that this email has been created in the
> knowledge that Internet email is not a 100% secure communications medium. We
> advise that you understand and observe this lack of security when emailing
> us.
>
> Viruses: Although we have taken steps to ensure that this email and
> attachments are free from any virus, we advise that in keeping with good
> computing practice the recipient should ensure they are actually virus free.
>
[-- Attachment #2: Type: text/html, Size: 2454 bytes --]
next prev parent reply other threads:[~2010-01-22 6:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 12:19 [gentoo-hardened] Security updates Machell, Jonathan
2010-01-21 14:05 ` klondike
2010-01-21 14:06 ` Kerin Millar
2010-01-21 14:12 ` Claes Gyllenswärd
2010-01-21 14:20 ` Andri Möll
2010-01-21 15:36 ` RB
2010-01-21 15:47 ` Machell, Jonathan
2010-01-22 6:36 ` Jonny Kent [this message]
2010-01-22 17:29 ` Michael Orlitzky
-- strict thread matches above, loose matches on Subject: below --
2007-02-10 16:02 [gentoo-hardened] security updates Nagy Gabor Peter
2007-02-10 16:43 ` Tom Hendrikx
2007-02-10 17:02 ` John Schember
2007-02-10 18:21 ` Jean-Pierre Schwickerath
2007-02-11 2:17 ` Andrew Ross
2007-02-11 12:38 ` Kevin F. Quinn
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=72bf0ae51001212236l22c59bacx66b9f903bbdcec7e@mail.gmail.com \
--to=jonnykent@gmail.com \
--cc=gentoo-hardened@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