On Wed, 17 Sep 2003, Shaun Oliver wrote:
*SNIP*
Not being a debian user I can't answer your other questions, other than
to say that I'm not a fan of automatic updates.
*SNIP*
who the hell gave you the impression that debian did automatic updates?
sorry bud but you have to still type apt-get
at the risk of being helpful, John Clarke delivered up the following on Thu, Sep 18,
2003 at 09:42:21AM +1000,
Next time, I suggest you read the thread you're responding to before
making a fool of yourself in public.
*SNIP*
oohh, I really hit a nerve here didn't I?
oh well,
so you decided to
On Thu, Sep 18, 2003 at 10:09:03PM +1000, Shaun Oliver wrote:
oohh, I really hit a nerve here didn't I?
Apologies to the list. This is a response to a private email and
Shaun should have kept it private.
Cheers,
John
--
whois [EMAIL PROTECTED]
GPG key id: 0xD59C360F
*SNIP*
Not being a debian user I can't answer your other questions, other than
to say that I'm not a fan of automatic updates.
*SNIP*
who the hell gave you the impression that debian did automatic updates?
sorry bud but you have to still type apt-get update and apt-get upgrade
to do an update of
This one time, at band camp, Shaun Oliver wrote:
who the hell gave you the impression that debian did automatic updates?
sorry bud but you have to still type apt-get update and apt-get upgrade
to do an update of any debian packages.
How odd. Did you read the beginning of this thread?
--
[EMAIL
FYI:
-- Forwarded Message --
Subject: CERT Advisory CA-2003-24 Buffer Management Vulnerability in OpenSSH
Date: Tue, 16 Sep 2003 17:44:19 -0400
From: CERT Advisory [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
CERT Advisory CA-2003-24 Buffer
On Wed, 17 Sep 2003, Declan Ingram wrote:
CERT Advisory CA-2003-24 Buffer Management Vulnerability in OpenSSH
Original release date: September 16, 2003
Last revised: --
Source: CERT/CC
A complete revision history can be found at the end of this file.
Systems Affected
On Wed, 17 Sep 2003, David wrote:
2: how do I figure out the version number of ssh there doesn't seem to
be a -v option of anything equally sensible :(
Telnet to the ssh port just like everyone else out there will be doing.
Andrew
--
No added Sugar. Not tested on animals. May contain
On Wed, Sep 17, 2003 at 02:30:02PM +1000, David wrote:
2: how do I figure out the version number of ssh there doesn't seem to
be a -v option of anything equally sensible :(
There is:
[EMAIL PROTECTED] ~]$ ssh -V
OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
Not being a
On Wed, Sep 17, 2003 at 02:30:02PM +1000, David wrote:
1: what is the thinking about running apt-get update, upgrade as a cron in
order to make sure that I don't miss any security updates?
just make sure your sources.list only has security lines.
main lines are ok as well on stable as
10 matches
Mail list logo