1995-10-04 - Re: Serious Windows TCP/IP Security Hole

Header Data

From: Rich Graves <llurch@Networking.Stanford.EDU>
To: “Henry Sanders (Exchange)” <henrysa@microsoft.com>
Message Hash: edf6492820654759f35da6d7c48e1e3f978d9d947887be22d77f5de564370cb4
Message ID: <Pine.ULT.3.91.951004165333.19409K-100000@Networking.Stanford.EDU>
Reply To: <c=US%a=_%p=Microsoft%l=BENJI951004101104NS00DC0D@CHOPPER>
UTC Datetime: 1995-10-04 23:57:57 UTC
Raw Date: Wed, 4 Oct 1995 16:57:57 -0700 (PDT)

Raw message

From: Rich Graves <llurch@Networking.Stanford.EDU>
Date: Wed, 4 Oct 1995 16:57:57 -0700 (PDT)
To: "Henry Sanders (Exchange)" <henrysa@microsoft.com>
Subject: Re: Serious Windows TCP/IP Security Hole
In-Reply-To: <c=US%a=_%p=Microsoft%l=BENJI951004101104NS00DC0D@CHOPPER>
Message-ID: <Pine.ULT.3.91.951004165333.19409K-100000@Networking.Stanford.EDU>
MIME-Version: 1.0
Content-Type: text/plain


I'm forwarding you a couple messages. I haven't run SAMBA myself, but 
people who have have been able to read files on my machine that aren't 
supposed to be shared.

-rich

On Wed, 4 Oct 1995, Henry Sanders (Exchange) wrote:

> Hi, I've jumped in late on this thread. What is the bug referred to in the note below? I might be able to give you current status on it.
> 
> Thanks,
> Henry Sanders
> henrysa@microsoft.com
> 
> >In article <44amc4$ft6@nntp.Stanford.EDU>, llurch@networking.stanford.edu
> says...
> >>
> >>FYI for those of you still running WFW. Could anybody confirm or deny
> >>that Microsoft has patched this hole in the shipping version of 95?
> >>As with most such serious "oopsies," Microsoft has not made any
> >>information on this issue available in their Knowledge Base.
> >
> >Nope, it is still there.
> 
> Can you demonstrate that this is true? I'll give you an account on my box.
> I've received several notes and flames that the problem either never
> existed (which I know is untrue) or was fixed at a specified (often
> specified different) patch level.
> 
> I should really try this myself, but I don't have time, and the only UNIX
> box I can really mess with is my Linux box, which is also my Win95 box.
> 

-rich






Thread