ADODB.Stream

[Richard K Bethell]

Hi,

We have an application, written in ASP, that uses the ADODB.Stream to be
able to open files and write byte arrays to the Response object. If one of
our administrators patches the web servers this application runs on in
Windows Update, I'm screwed, right? You've essentially just disabled this
COM object, for not only its evil purposes, but its useful ones?

Richard

 

[Tom Kaminski [MVP]]

Hi,

We have an application, written in ASP, that uses the ADODB.Stream to be
able to open files and write byte arrays to the Response object. If one of
our administrators patches the web servers this application runs on in
Windows Update, I'm screwed, right? You've essentially just disabled this
COM object, for not only its evil purposes, but its useful ones?

AFAIK, the update will just affect the Stream object in Internet Explorer.
http://support.microsoft.com/default.aspx?scid=kb;en-us;870669

--
Tom Kaminski IIS MVP
http://www.microsoft.com/windowsserver2003/community/centers/iis/
http://mvp.support.microsoft.com/
http://www.iisfaq.com/
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS
http://www.tryiis.com

 

[Myron Johnson]

AFAIK, the update will just affect the Stream object in Internet Explorer.
http://support.microsoft.com/default.aspx?scid=kb;en-us;870669

We are using an .ASP page and ADODB.Stream on an Windows Server 2003
IIS 6.0 web server to stream files to clients. I was afraid we were
going to have to abandon this approach, but it appears to work just
fine after MS's ADODB.Stream-killing security patch. Apparently, as
stated by Tom Kaminski, if the ADODB.Stream is running on a SERVER, it
is still created and works fine. Clients can still download and save
our streaming files, even after the patch and even after setting
"High" browser security (except they have to allow file downloads, of
course).