Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!ames!pasteur!agate!saturn!ssyx.ucsc.edu!vespa From: vespa@ssyx.ucsc.edu (Adam Alexander Margulies) Newsgroups: comp.sys.mac.hypercard Subject: Hypercard Security Message-ID: <3085@saturn.ucsc.edu> Date: 30 Apr 88 02:34:46 GMT Sender: usenet@saturn.ucsc.edu Reply-To: vespa@ssyx.ucsc.edu (Adam Alexander Margulies) Organization: Universiy of California, Santa Cruz Lines: 41 I hate security, copy protection, and secrecy, but I couldn't help playing with some of hypercard's "security" features. It is difficult to keep someone from going to another stack and typing into the message box "edit script of stack XYZ". I found that on openStack set userlevel to 1 . . . nicely foils that (although I found that almost no "secure" stacks do this. Through this method I have breached many a "secure" stack) Hypercard uses a lot of encryptionn (literally dozens of different compression techniques, this is effective encryption) so people cannot fedit your stack for passwords. To be truly secure you must set the userlevel to 1 on openStack, intercept the message box being opened, and stop blindtyping. Also putting a on idle hide menubar end idle seems to be the best way of avoiding things like PopIt! from giving access to the menubar, and it is easier than intercepting every menu item. Anyone played with hypercard security and/or enjoy breaking other people's security? I said, type it NOW, Adam! || ||Adam Margulies | \ ||_ /| ||ARPA: vespa@ucscb.ucsc.edu | ||\`o_O' ||BITNET: vespa@ucsci.BITNET | || ( ) ||UUCP: ...!ucbvax!ucscc!ssyx!vespa | ----------------------------||--mU-m-||WEIRD:vespa%ssyx.ucsc.edu@RELAY.CS.NET | |DISCLAIMER: ||ATT: (408)429-8868 | | These are NOT my opinions. They are my dog's. |