Re: Security hole in file sharing (bug?)
From: Alun Jones [MSFT] (alunj_at_online.microsoft.com)
Date: 01/28/05
- Next message: Torgeir Bakken \(MVP\): "Re: 16 bit Windows Subsystem Message"
- Previous message: null: "Re: Spyware removal"
- In reply to: Roger Abell: "Re: Security hole in file sharing (bug?)"
- Next in thread: Roger Abell: "Re: Security hole in file sharing (bug?)"
- Reply: Roger Abell: "Re: Security hole in file sharing (bug?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 28 Jan 2005 12:11:47 -0800
I don't think it'll help you in this situation.
The fault lies in the English language, and the similarity between the words
"not" and "now", in their spelling and in their allowed placements.
Consider the two sentences:
I will now insult your parental lineage.
I will not insult your parental lineage.
Either is contextually correct, at least up until a subsequent line, wherein
it'd be clear as to whether I was, or was not, crafting a rude retort.
Clearly the English language needs to be changed. I'll suggest it for a
future service pack.
Alun.
~~~~
-- Software Design Engineer, Internet Information Server (FTP) This posting is provided "AS IS" with no warranties, and confers no rights. "Roger Abell" <mvpNOSpam@asu.edu> wrote in message news:efNFUrDBFHA.1524@TK2MSFTNGP09.phx.gbl... > not > When will someone make a free context sensitive and > aware spell/grammar checker for me !! > > -- > Roger > "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message > news:%23kZVDEDBFHA.2156@TK2MSFTNGP10.phx.gbl... >> Now or not?? -- Steve >> >> "Roger Abell" <mvpNOSpam@asu.edu> wrote in message >> news:uk08Xv$AFHA.608@TK2MSFTNGP15.phx.gbl... >> > What you report is now what I have experienced. >> > How is it that you performed your test? >> > >> > -- >> > Roger Abell >> > Microsoft MVP (Windows Security) >> > MCSE (W2k3,W2k,Nt4) MCDBA >> > "Massimo" <barone@mclink.it> wrote in message >> > news:%23LzUmk%23AFHA.2788@TK2MSFTNGP15.phx.gbl... >> >> I don't know if this has already been reported. >> >> >> >> I have a Windows XP SP2 computer, fully up-to-date with patches, which >> >> connects to the Internet through a dial-up connection. >> >> In the network settings for the dial-up connection, I have disabled >> >> the >> >> "client for Microsoft networks" and "file and print sharing" > components, >> > and >> >> I've also disabled NetBIOS on the TCP/IP settings. With this >> > configuration, >> >> I was quite sure my shares wouldn't have been exposed to Internet >> >> users... >> >> but I found, instead, that they are. Altough disabled, the file >> >> sharing >> >> services are fully accessible, and I was able to connect to them and > also >> >> use them (by supplying my username/password). >> >> >> >> What's happening here? Are not the connection-specific settings valid >> >> anymore? >> >> >> >> This seems to me quite a serious bug! >> >> >> >> Massimo >> >> >> >> P.S. >> >> I know I can activate the built-in firewall, or stop the server > service, >> > or >> >> fully remove the file sharing network component, and so on... but I > want >> > to >> >> know why I'm settings things right and they're behaving wrong! >> >> >> > >> > >> >> > >
- Next message: Torgeir Bakken \(MVP\): "Re: 16 bit Windows Subsystem Message"
- Previous message: null: "Re: Spyware removal"
- In reply to: Roger Abell: "Re: Security hole in file sharing (bug?)"
- Next in thread: Roger Abell: "Re: Security hole in file sharing (bug?)"
- Reply: Roger Abell: "Re: Security hole in file sharing (bug?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|