View Single Post
  #23 (permalink)  
Old 03-26-2004, 11:52 PM
David's Avatar
David David is offline
Senior Member
 

Join Date: Apr 2003
Location: Portland, OR
Posts: 5,318
David has left a lasting impression (500)David has left a lasting impression (500)David has left a lasting impression (500)David has left a lasting impression (500)David has left a lasting impression (500)David has left a lasting impression (500)
Send a message via AIM to David
DoS is bad, DOS is good. =)

DoS = Denial of Service attack
DOS = Disk operating system, where very little of the OS is actually loaded into memory.

I remember how my VB teacher was amazed when I made 'Network Client-Server-Client IM system', and how she told me that I wasn't allowed to use it after she graded it because it was a security risk.

I can't see how a Connection on port 4000 over the INTERNAL network could possibly compromise the entire network, I'm not even accessing the WAN.

We don't have access to NT-DOS (WinNT doesn't come with DOS, NT-DOS actually processes everything through Windows NT, unlike the Win9X systems did), but we have RUN, and that's all I need to really do anything. And we have Visual Studio, so I could use FileSystemObject to interact with the local file system. The point is that the network is generally not protected from more advanced users and all they can do is punish anyone that does something 'They don't like'.

Raining on the parade since 2003.

Dave Amenta .com
Reply With Quote