On 16. September 2003 at 17:17, Vincent Danen wrote:

> Typically, when I update openssh, I've tested it for a few days on my
> own machine first.
> 
> 8.2 came with 3.1p1; 3.6.1p2 was provided for updates today
> 9.0 came with 3.4p1; 3.6.1p2 was likewise provided today

a-ha, you'r tested today's update for older version of mdk few days
before with latest patch and it don't break anything and it work
perfectly. you and qa team can say that this was carefully tested, yes??

i have another example about latest kernel updates which contain
freeswan 2.0 and there is no freeswan user space package update for
these versions which makes ipsec implementation unusable..

> What makes you think that 9.1 will have 3.6.1p2 for the next 2 years?
> I don't think you bothered to look at how the updates work; please
> don't make blanket statements like this when they are so obviously
> incorrect.

ok, please tell me where is information how _exactly_ updates work?
maybe i search anyhow, but i can't find any information about this on
"Security updates" link at mandralinux site, wiki site and i make some
google search without success.

i only think, that backporting is more usefull than "it can compiles,
starting without errors -> good candidate for updates" policy.

let's look how openssh problem was fixed in redhat:
for example rh 7.3 openssh package changelog:

* St sep 17 2003 Nalin Dahyabhai <[EMAIL PROTECTED]> 3.1p1-9
- apply patch to store the correct buffer size in allocated buffers
  (CAN-2003-0693)

check version number; there is strictly backported all patches into too
old version of openssh but he has confidence that this updated package
can't break anything.
and this is reason why redhat tell how long want support older
distribution, imho. if mandrake follow this, why don't follow update
policy too?

only thing what i want discuss is:
during cooker freeze can't be updated newer version in this special
situation, but for older releases it is ok? why don't only backported
patch into older releases?

> And, BTW, support is 18mos, not 2 years.

hm, what about this:
http://www.mandrakesecure.net/en/productlifetime.php

"Finally, specialized "server" products, will have a full life updates
support of no less than 24 months."

i understand this that maximum support life is 24 months, and this is
2 years.. it doesn't matter that download edition/desktop applications
is supported for shorter period.

p.s.: i respect your authority about updates, but i think that this
process isn't fully clear long time ago and there is some things which
can be improved and give exactness in this process.
p.s.2.: i promise, that my worst english ever can't lead to
misunderstanding my things in this email.

-- 
member of Advanced InternetWorks group  -> http://www.ainetworks.sk
professional home page                  -> http://tibor.pittich.sk
personal home page                      -> http://c0re.phuture.sk

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to