From abe@fettig.net Tue Dec 02 19:06:10 2003
Return-Path: <abe@fettig.net>
Delivered-To: mailman-sharedsolotech@lists.tummy.com
Received: (qmail 1593 invoked by uid 0); 2 Dec 2003 19:06:09 -0000
Received: from vm.shared.tummy.com (HELO fettig.net) (198.49.126.123)
  by dev.tummy.com with RC4-SHA encrypted SMTP; 2 Dec 2003 19:06:09 -0000
Received: from localhost.localdomain
	([127.0.0.1] helo=fettig.net ident=abe)
	by fettig.net with esmtp (Exim 4.24)
	id 1ARFqF-0004RQ-0Q
	for sharedsolotech@lists.tummy.com; Tue, 02 Dec 2003 12:05:47 -0700
Message-ID: <3FCCE45A.9050002@fettig.net>
Date: Tue, 02 Dec 2003 14:13:30 -0500
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6b) Gecko/20031110 Thunderbird/0.4a
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sharedsolotech@lists.tummy.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SA-Exim-Mail-From: abe@fettig.net
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Mailman-Approved-At: Wed, 03 Dec 2003 09:38:47 -0700
From: sharedsolotech@lists.tummy.com
Subject: [Sharedsolotech] Kernel Updates
X-BeenThere: sharedsolotech@lists.tummy.com
X-Mailman-Version: 2.1
Precedence: list
Reply-To: sharedsolotech@lists.tummy.com
List-Id: Technical announcements for tummy.com shared virtuals.
 <sharedsolotech.lists.tummy.com>
List-Unsubscribe: <http://lists.tummy.com/mailman/listinfo/sharedsolotech>,
	<mailto:sharedsolotech-request@lists.tummy.com?subject=unsubscribe>
List-Archive: <http://lists.tummy.com/pipermail/sharedsolotech>
List-Post: <mailto:sharedsolotech@lists.tummy.com>
List-Help: <mailto:sharedsolotech-request@lists.tummy.com?subject=help>
List-Subscribe: <http://lists.tummy.com/mailman/listinfo/sharedsolotech>,
	<mailto:sharedsolotech-request@lists.tummy.com?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2003 19:06:10 -0000

Hi Folks,

It seems that the recent security breaches of the Debian servers were 
made possible by a flaw in the Linux kernel itself.  I'd like to make 
sure my host has an updated kernel, with the security hole fixed.  But 
I'm not quite sure how kernel upgrades work in the tummy virtual server 
environment.  Is it safe for me to go ahead and install an updated 
kernel in my virtual machine, or is that something tummy would have to do?

Thanks,
Abe
From ken.weinert@ihs.com Wed Dec 03 16:55:58 2003
Return-Path: <ken.weinert@ihs.com>
Delivered-To: mailman-sharedsolotech@lists.tummy.com
Received: (qmail 4147 invoked by uid 0); 3 Dec 2003 16:55:58 -0000
Received: from mail1.ihs.com (170.207.70.222)
  by dev.tummy.com with SMTP; 3 Dec 2003 16:55:58 -0000
Received: from adamselene.ihs.com (mail@adamselene.ihs.com [170.207.189.17])
	by mail1.ihs.com (8.12.10/8.12.10) with ESMTP id hB3GsWDV004320
	for <sharedsolotech@lists.tummy.com>;
	Wed, 3 Dec 2003 09:54:32 -0700 (MST)
Received: from wein4257 by adamselene.ihs.com with local (Exim 3.36 #1
	(Debian))	id 1ARaGN-0004oT-00
	for <sharedsolotech@lists.tummy.com>; Wed, 03 Dec 2003 09:54:07 -0700
Date: Wed, 3 Dec 2003 09:54:07 -0700
To: sharedsolotech@lists.tummy.com
Subject: Re: [Sharedsolotech] Kernel Updates
Message-ID: <20031203165407.GB31879@quarter-flash.com>
References: <3FCCE45A.9050002@fettig.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="XF85m9dhOBO43t/C"
Content-Disposition: inline
In-Reply-To: <3FCCE45A.9050002@fettig.net>
X-Operating-System: Linux adamselene.ihs.com 2.4.19
User-Agent: Mutt/1.5.4i
X-IHS-MailScanner: Found to be clean
X-IHS-MailScanner-SpamCheck: 
X-Mailman-Approved-At: Wed, 03 Dec 2003 10:18:12 -0700
From: sharedsolotech@lists.tummy.com
X-BeenThere: sharedsolotech@lists.tummy.com
X-Mailman-Version: 2.1
Precedence: list
Reply-To: sharedsolotech@lists.tummy.com
List-Id: Technical announcements for tummy.com shared virtuals.
 <sharedsolotech.lists.tummy.com>
List-Unsubscribe: <http://lists.tummy.com/mailman/listinfo/sharedsolotech>,
	<mailto:sharedsolotech-request@lists.tummy.com?subject=unsubscribe>
List-Archive: <http://lists.tummy.com/pipermail/sharedsolotech>
List-Post: <mailto:sharedsolotech@lists.tummy.com>
List-Help: <mailto:sharedsolotech-request@lists.tummy.com?subject=help>
List-Subscribe: <http://lists.tummy.com/mailman/listinfo/sharedsolotech>,
	<mailto:sharedsolotech-request@lists.tummy.com?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2003 16:55:58 -0000


--XF85m9dhOBO43t/C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 02, 2003 at 02:13:30PM -0500, sharedsolotech@lists.tummy.com wr=
ote:
> Hi Folks,
>=20
> It seems that the recent security breaches of the Debian servers were=20
> made possible by a flaw in the Linux kernel itself.  I'd like to make=20
> sure my host has an updated kernel, with the security hole fixed.  But=20
> I'm not quite sure how kernel upgrades work in the tummy virtual server=
=20
> environment.  Is it safe for me to go ahead and install an updated=20
> kernel in my virtual machine, or is that something tummy would have to do?


Tummy did it last night.

IIRC it was about 10 or 10:30 when Sean rebooted the entire bunch
of them.

--=20
   .--.     Ken Weinert   Ken.Weinert@ihs.com=20
  |o_o |
  ||_/ |    303-858-6956 (V) 303-705-4258 (F)=20
 //   \ \
(|     | )  GnuPG: 9274F1CE  GnuPG available at http://www.gnupg.org/
/'\_   _/`\=20
\___)=3D(___/ 1D87 3720 BB77 4489 A928  79D6 F8EC DD76 9274 F1CE
Budget: A method for going broke methodically.


--XF85m9dhOBO43t/C
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/zhUv+OzddpJ08c4RAsloAJ9L1ipWVvEFfRPGdK49X0tvkbjGqwCfcXAe
eJJT0fD93Y32ntDf6mM9J1M=
=1Z1+
-----END PGP SIGNATURE-----

--XF85m9dhOBO43t/C--
From jafo@tummy.com Tue Dec 09 17:48:49 2003
Return-Path: <jafo@tummy.com>
Delivered-To: mailman-sharedsolotech@lists.tummy.com
Received: (qmail 5151 invoked by uid 0); 9 Dec 2003 17:48:49 -0000
Received: from newsecure.tummy.com (HELO tummy.com) (198.49.126.8)
  by dev.tummy.com with DES-CBC3-SHA encrypted SMTP; 9 Dec 2003 17:48:48 -0000
Received: (qmail 16326 invoked by uid 10); 9 Dec 2003 17:48:48 -0000
Received: (qmail 13433 invoked by uid 500); 9 Dec 2003 17:48:42 -0000
Date: Tue, 9 Dec 2003 10:48:42 -0700
To: sharedsolotech@lists.tummy.com
Message-ID: <20031209174842.GZ10866@tummy.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Mailman-Approved-At: Tue, 09 Dec 2003 11:08:39 -0700
From: sharedsolotech@lists.tummy.com
Subject: [Sharedsolotech] Snapshots temporarily unavailable.
X-BeenThere: sharedsolotech@lists.tummy.com
X-Mailman-Version: 2.1
Precedence: list
Reply-To: sharedsolotech@lists.tummy.com
List-Id: Technical announcements for tummy.com shared virtuals.
 <sharedsolotech.lists.tummy.com>
List-Unsubscribe: <http://lists.tummy.com/mailman/listinfo/sharedsolotech>,
	<mailto:sharedsolotech-request@lists.tummy.com?subject=unsubscribe>
List-Archive: <http://lists.tummy.com/pipermail/sharedsolotech>
List-Post: <mailto:sharedsolotech@lists.tummy.com>
List-Help: <mailto:sharedsolotech-request@lists.tummy.com?subject=help>
List-Subscribe: <http://lists.tummy.com/mailman/listinfo/sharedsolotech>,
	<mailto:sharedsolotech-request@lists.tummy.com?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2003 17:48:50 -0000

A problem has been identified with the snapshot mechanism on the virtual
servers.  This option in the management control panel has been disabled
until I can track down the source of the problem and take corrective
measures.  I expect to have this completed within the next day or two.

This will not impact the normal running of the virtual machines.

If you have any questions or concerns, let me know.  I should have this
corrected within the next day or two.

Thanks,
Sean
-- 
 Why would I want to be a Doctor, when I could be a MASTER?
Sean Reifschneider, Member of Technical Staff <jafo@tummy.com>
tummy.com, ltd. - Linux Consulting since 1995.  Qmail, Python, SysAdmin
      Back off man. I'm a scientist.   http://HackingSociety.org/
