Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!ogicse!milton!absinthe From: absinthe@milton.u.washington.edu (Daniel 'B' Faken) Newsgroups: comp.sys.next Subject: Re: Security Hole? Message-ID: <12634@milton.u.washington.edu> Date: 9 Dec 90 09:05:49 GMT References: <49464@cornell.UUCP> <10548@uhccux.uhcc.Hawaii.Edu> <12600@milton.u.washington.edu> Organization: University of Washington, Seattle Lines: 26 In article <12600@milton.u.washington.edu> wiml@milton.u.washington.edu (William Lewis) writes: > > Indeed. I just played with a 68040 slab (monochrome, alas) demo unit this >afternoon and Pref now has a switch for "Public Sound Port" or some such. >By default, disabled. > Of course, nothing prevents you from doing exactly this on an *old* >1.0 machine, which is a cause of endless *ahem* merriment around here... >fortunately, people rarely leave microphones lying around plugged into >their NeXTs. =8) > As I remember, the reply to the thread last summer was that the new 'Sound Boxes' (that include outputs for speakers, etc.) have a PHYSICAL switch to turn off the microphone.... I suppose you could write something to acquire the microphone input's port and feed them messages like "We've been waiting for you, " :) [including file: /altdimension7/'heaven'/God/Christian/.signature...] ----------------------------------------------------------------------------- Faithfully and unerringly saving our civilization from certain demise.. absinthe@milton.u.washington.edu | "Don't get Odd, get Even" ------------------------------------------------------------------------------ The opinions (and/or facts) expressed herein may represent most of the student body and administratium here at the UW. But then again, they may not.