[14769] in bugtraq

home help back first fref pref prev next nref lref last post

Re: Windows NT/95/98/Possible Others Denial of Service Attack.

daemon@ATHENA.MIT.EDU (Jeff Dafoe)
Wed May 3 18:01:55 2000

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id:  <NDBBIOPEKLHMHCDKLPLPOEMNCMAA.jeffd@evcom.net>
Date:         Tue, 2 May 2000 17:04:16 -0400
Reply-To: Jeff Dafoe <jeffd@EVCOM.NET>
From: Jeff Dafoe <jeffd@EVCOM.NET>
X-To:         Daniel Docekal <ddoc@MIA.CZ>, BUGTRAQ@SECURITYFOCUS.COM
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  <080D5336D882D211B56B0060080F2CD6623F35@beta.mia.cz>

> It is WELL known that Access may NOT be used for production WWW servers as
> it is not thread safe and cause various problems, including crashes of
> services. Especially when under heavy load or running for long period of
> time.

	The majority of the symptoms that were originally described (the effects of
failing to close an ODBC connection) are also reproduceable when using a SQL
server data source.  Perhaps under Access the results are more catastrophic,
which would be inline with the symptoms that the poster decribed which were
more severe than what I have encountered.  I do know that failure to close
an ODBC connection in ASP, regardless of the underlying database system,
will eventually cause any ASP code utilizing that connection to fail.


Jeff

home help back first fref pref prev next nref lref last post