And they checked - the XP guys messed up bigtime, and the NT QFE team is
looking into getting the fix out....



Larry Osterman 



-----Original Message-----
From: Larry Osterman 
Sent: Tuesday, September 03, 2002 9:32 AM
To: Larry Osterman; Wolfgang Spraul; [EMAIL PROTECTED]
Subject: RE: file not deleted on Win32


Ok, apparently the SSL fix is in NT4 SP7 (the tech reviewer apparently
missed that when he reviewed it :)), I don't know what the deal is with
ME/98, apparently nobody ever reported that it was a problem on those
platforms to Microsoft :)


And if the bug really is in XP (I do trust you Mark, it's just that the
QFE guys don't know you from adam), then there was a monumentous mess-up
on the part of the guy who was fixing the bug, since all the QFE fixes
are supposed to be rolled up into the final release.  I'll ask the NT
dev who owns schannel.


 


Larry Osterman 



-----Original Message-----
From: Larry Osterman 
Sent: Tuesday, September 03, 2002 9:09 AM
To: Wolfgang Spraul; [EMAIL PROTECTED]
Subject: RE: file not deleted on Win32


I wish I understood what caused bugs to make the QFE list for various
products...

I do know that the bar for taking fixes is an order of magnitude higher
for NT4/ME/98 than it is for XP and W2K, since there isn't any active
development being done on them.  In this case, I'm sure that it's
because the Exchange server got burned by the problem (based on the
comments in the KB article).  Interestingly enough, the fix is NOT
limited to schannel.dll, there are a boatload of other changes
associated with the fix, go figure.

I've asked the author of the KB article what the deal is with the other
platforms that have this bug.




Larry Osterman 



-----Original Message-----
From: Wolfgang Spraul [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, September 03, 2002 6:01 AM
To: Larry Osterman; [EMAIL PROTECTED]
Subject: Re: file not deleted on Win32


Larry -

> Is there a reason you can't switch to W2K?

In this case, I had to fix the schannel.dll bug q300562 on a production
nt4 
machine, and the best option I found was to switch to openssl. After the
problem was understood, the fix was done and in use after a few 
hours. Contacting MS support would have probably cost me considerably
more 
time and money. My job was to fix the bug, not to sell a server upgrade
to 
the user.

Again, since these updates exist anyway, please note my lobbying for
making 
them available upfront, for download from the web 24/7.

Thanks for listening,
Wolfgang Spraul

Reply via email to