home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!mips!sdd.hp.com!caen!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!newshost.cs.rose-hulman.edu!news
- From: mgrdla@NeXTwork.Rose-Hulman.Edu (David L. Allabaugh, Jr.)
- Newsgroups: comp.sys.next.misc
- Subject: Re: Preferences - UNIX setup
- Message-ID: <1992Jul28.013310.8328@cs.rose-hulman.edu>
- Date: 28 Jul 92 01:33:10 GMT
- References: <1992Jul27.213926.7386@pencom.com>
- Sender: news@cs.rose-hulman.edu (The News Administrator)
- Organization: Rose-Hulman Institute of Technology
- Lines: 20
- Nntp-Posting-Host: cornflower.nextwork.rose-hulman.edu
-
-
- In article <1992Jul27.213926.7386@pencom.com> alex@laos (Alex D. Nghiem)
- writes:
- > Public Sound Server -- allows/prohibits others from sending sounds over
- the
- > network to your speaker
- > + allows you to create "haunted house effect" (hey, where's the music
- coming
- > from?)
- > - I don't know of any
- Setting yourself to be a Public Sound Server also allows the microphone on
- the machine you are using to be accessed by someone else. This can (yes
- I've seen it done) be used to listen to the environment around a machine
- without the knowlege of the person on that machine. That is a definite
- security risk. Would you want all of what was said in your office to be
- heard by person X on your local network? If not, then don't set yourself
- to be a public sound server.
- Dave Allabaugh
- Asst. Unix Mgr.
- Rose-Hulman Inst. Tech.
-