[20312] in bugtraq
Re: Samba 2.0.8 security fix
daemon@ATHENA.MIT.EDU (Boyce, Nick)
Thu Apr 19 13:37:03 2001
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <C1B2296C5D3ED11182DB00805F9A097E015065D8@GBHBM001>
Date: Wed, 18 Apr 2001 18:09:16 +0100
Reply-To: "Boyce, Nick" <nick.boyce@EDS.COM>
From: "Boyce, Nick" <nick.boyce@EDS.COM>
To: BUGTRAQ@SECURITYFOCUS.COM
Can Tridge or anyone else confirm whether or not this bug was present in
Samba versions earlier than 2.0.7 ?
Along with 2.0.7, we still run 2.0.5a, which is the latest "security fix"
version available as a binary for some of our Unixen, and we have an
exceptionally old-fashioned Un*x still running 1.9.17p4.
I know I should probably just give up on precompiled binaries, and compile
from source on all our boxen.
(I'm making the same enquiry in respect of Samba-for-VMS on the relevant
users' mailing list.)
Thanks,
Nick Boyce
EDS Healthcare, Bristol, UK
-----Original Message-----
From: tridge@SAMBA.ORG [mailto:tridge@SAMBA.ORG]
Sent: 18 April 2001 01:07
To: BUGTRAQ@SECURITYFOCUS.COM
Subject: Samba 2.0.8 security fix
I've just released Samba 2.0.8. This release fixes a significant
security vulnerability that allows local users to corrupt local
devices (such as raw disks).
[snip]
