hi,
may i ask some stupid question. :)
I am using Samba 2.2.8a, how should i do if i don't want upgrade to the
latest version of Samba but use the *.patch file?
And there are so many patch files, should i patch every file to my system?
If the affected release of a patch file is "3.0.x <=3D 3.0.6", dose
it mean this security issue just affect version 3.0.x and my system can ignore
this? From jht at Samba.Org Tue May 24 05:33:07 2005
From: jht at Samba.Org (John H Terpstra)
Date: Tue May 24 05:33:16 2005
Subject: [Samba] how to use the *.patch file
In-Reply-To: <000801c56015$c7dbaed0$0114290a@ares1034>
References: <000801c56015$c7dbaed0$0114290a@ares1034>
Message-ID: <200505232333.07813.jht@Samba.Org>
On Monday 23 May 2005 22:05, =C4=A3=B6h wrote:> hi,
> may i ask some stupid question. :)
You may ask, but you may also receive a not-expected answer.
> I am using Samba 2.2.8a, how should i do if i don't want upgrade to the
> latest version of Samba but use the *.patch file?
Why do you not want to update to Samba-3.0.x? What have we done wrong?
Samba-2.2.x is a dead code tree that is no longer maintained. It has a number=20
of security vulnerabilities, and is not fully compatible with current Windows=20
clients, nor with recent Windows service patches.
The documentation for Samba-3 is extensive, including detailed guides for=20
updating your system. The documentation for Samba-2.2.x consisted of a=20
fraction of what is available now. Lack of documentation is no longer a=20
reasonable objection.
> And there are so many patch files, should i patch every file to my system?
Well, it would help if we knew which patches you are referring to. We do not=20
create patches because we need something to do, rather each has it's
purpose.
> If the affected release of a patch file is "3.0.x <=3D 3.0.6",
dose it mean
> this security issue just affect version 3.0.x and my system can ignore
> this?
Suffice to say that today, 18 months after 3.0.0 came out (and at version=20
3.0.14a) no-one should be running an earlier 2.x version. There are security=20
reasons for this, plus the longer you delay in updating the more work will be=20
involved when you do. We put much effort into helping our users to remain=20
current with Microsoft Windows service patches, and we work with the=20
principal that small-step upgrades are less painful than massively=20
discontinuous update performed after long intervals.
Recently I had to help a Samba site move from 2.0.7 to 3.0.14a in what had=20
become a very challenging update. The update was forced because client=20
workstations suddenly started to drop-off the network. The disruption caused=20
would have been avoided had the site remained current.
No offense means, and I certainly would not want to come across as coercing a=20
change - the decision is yours and yours alone.
=2D John T.
=2D-=20
John H Terpstra
Samba-Team Member
Phone: +1 (650) 580-8668
Author:
The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556
Samba-3 by Example, ISBN: 0131472216
Hardening Linux, ISBN: 0072254971
Other books in production.
