[comp.sys.mac] Disklock

boris@ulysses.homer.nj.att.com (Boris Altman) (09/05/89)

I just got the DiskLock from 5-th generation system.
For those of you who are considering this program
here are a couple of things that are not obvious
from any literature:
1. The disk locking program does not work with any removable media,
including SyQuest drives (MassMicro, Microtech and others who pachage
this 45meg drive). When you try to install it on one of those the
program comes back and says, "take the cartridge out and lock it in
your draw". Very funny. In order to find it out
you have to look in the user manual (i.e. open the package).
However, you can still lock folders on those drives.
The tech support said that there is no technical problem
in locking removables, but the philosophy is to lock
only drives that cannot be secured in any other way.
I guess you can say you can lock your office door and
then you do not need any locking program at all.

2. If you shut mac down in some way other than normal SHUTDOWN,
your disks will not be locked.

3. Locking folders means encrypting and takes time proportional
to the amount of files/data in the folder. I should have
guessed this one.

I do not have anything against this product, but because of the above
items it makes it useless for our purposes.
5-th generation offered to take the program back for full refund.

			Boris Altman
			boris@ulysses.att.com

svc@well.UUCP (Leonard Rosenthol) (09/07/89)

In article <12133@ulysses.homer.nj.att.com> boris@ulysses.homer.nj.att.com (Boris Altman) writes:
>I just got the DiskLock from 5-th generation system.
>For those of you who are considering this program
>here are a couple of things that are not obvious
>from any literature:
>1. The disk locking program does not work with any removable media,
>including SyQuest drives (MassMicro, Microtech and others who pachage
>this 45meg drive). 
>
	I have not tried this recently but during the beta testing of this
product, discussions with the author led me to believe that this was indeed
possible (I think we even did it once, as a test).  If the release version does
indeed put up the alert you imply, then something changed... Personally, if 
they have taken out this ability I would also be disappointed as locking 
syquest cartridges is very useful!

>2. If you shut mac down in some way other than normal SHUTDOWN,
>your disks will not be locked.
>
	I am curious as to how else you would shutDown your Macintosh? Even
the use of most of the ShutDown FKEY's and HC XCMD's will cause the disk to
lock - so how are you shutting down that does not lock it??
	Also keep in mind that there are two other ways to lock the disk - one
is to reboot with the option key held down, the other is to use the DiskLock
DA to lock it at any time you please (this is combined with a nice screensaver)
giving you a nice combination for when you walk away from your Mac for a while.

>3. Locking folders means encrypting and takes time proportional
>to the amount of files/data in the folder. I should have
>guessed this one.
>
	This is true - HOWEVER, unlocking takes practially NO TIME AT ALL!
If you consider that you only lock a folder once, but unlock frequently, I can
live with this one-time slowness....
-- 
+--------------------------------------------------+
Leonard Rosenthol        |  GEnie : MACgician
Lazerware, inc.          |  MacNet: MACgician
UUCP: svc@well.UUCP      |  ALink : D0025

d88-jwa@nada.kth.se (Jon W{tte) (09/08/89)

In article <13506@well.UUCP> svc@well.UUCP (Leonard Rosenthol) writes:
>In article <12133@ulysses.homer.nj.att.com> boris@ulysses.homer.nj.att.com (Boris Altman) writes:
>>2. If you shut mac down in some way other than normal SHUTDOWN,
>>your disks will not be locked.

>	I am curious as to how else you would shutDown your Macintosh? Even
>the use of most of the ShutDown FKEY's and HC XCMD's will cause the disk to
>lock - so how are you shutting down that does not lock it??

Ever heard of SYSTEM CRASHES ? If you develop software, and want your source
code to be safe from prying eyes (well, I don't, I give my code away, but I
know people who do...) you damned well shut your macintosh down (although
not intentionally) without locking the disk ! I have crashes thet MacsBug
can't handle by the score every week !

So, APPLE, why don't you run along and give us protected memory ? Huh ?
(Hmm. I could write an INIT that patched the trap and OS dispatchers,
and run all my Apps in protected mode. Hummm. GM: I smell a Quest ! :-)

Happy Hacking

h+
-- 
Moooo.

svc@well.UUCP (Leonard Rosenthol) (09/08/89)

In article <1573@draken.nada.kth.se> d88-jwa@nada.kth.se (Jon W{tte) writes:
>In article <13506@well.UUCP> svc@well.UUCP (Leonard Rosenthol) writes:
>>In article <12133@ulysses.homer.nj.att.com> boris@ulysses.homer.nj.att.com (Boris Altman) writes:
>>>2. If you shut mac down in some way other than normal SHUTDOWN,
>>>your disks will not be locked.
>
>>	I am curious as to how else you would shutDown your Macintosh? Even
>>the use of most of the ShutDown FKEY's and HC XCMD's will cause the disk to
>>lock - so how are you shutting down that does not lock it??
>
>Ever heard of SYSTEM CRASHES ? If you develop software, and want your source
>code to be safe from prying eyes (well, I don't, I give my code away, but I
>know people who do...) you damned well shut your macintosh down (although
>not intentionally) without locking the disk ! I have crashes thet MacsBug
>can't handle by the score every week !
>
	Sure I've heard of system crashes - though I try to write software
that doesn't do that too frequently!  But when it happens, my Mac REBOOTS! I
don't know about you (I am sure very few people do, or want to) but I don't
shut down (turn off) my Mac after a system crash and I would not want a 
protection product asking me my password EVERY time I rebooted/restarted.

	You also missed the second part of my message which explained that 
you can also force the Mac into a protected mode by using the included DA so
that AT ANY TIME you can protect the Mac from prying eyes.

>So, APPLE, why don't you run along and give us protected memory ? Huh ?
>(Hmm. I could write an INIT that patched the trap and OS dispatchers,
>and run all my Apps in protected mode. Hummm. GM: I smell a Quest ! :-)
>
	Why don't you find another forum for your protected memory flambe. You
and I both know that Apple is not giving it to us in System 7 and that they are
working on it for future OS's (when is the future, I don't know either??) so
flaming about it is not doing us or Apple any service...Give it a rest!!!


+--------------------------------------------------+
Leonard Rosenthol        |  GEnie : MACgician
Lazerware, inc.          |  MacNet: MACgician
UUCP: svc@well.UUCP      |  ALink : D0025
-- 
+--------------------------------------------------+
Leonard Rosenthol        |  GEnie : MACgician
Lazerware, inc.          |  MacNet: MACgician
UUCP: svc@well.UUCP      |  ALink : D0025

d88-jwa@nada.kth.se (Jon W{tte) (09/09/89)

In article <13517@well.UUCP> svc@well.UUCP (Leonard Rosenthol) writes:

>	Sure I've heard of system crashes - though I try to write software
>that doesn't do that too frequently!  But when it happens, my Mac REBOOTS! I
>don't know about you (I am sure very few people do, or want to) but I don't

Of course, my crashes may be spectacular. They wreck havoc in my System
Resource Fork, making the Mac unable to boot from that disk. But then It's
REAl safe :-) (Unless someone comes along with a system disk...)

I also write:
>>So, APPLE, why don't you run along and give us protected memory ? Huh ?

>Why don't you find another forum for your protected memory flambe. You

Because I want it, and I want it NOW ! Apple has all the source for the
system, so they're in a far better position than I am to write that piece
of software. And I'm gonna make REALLY sure that this is gonna be their
prime goal for system 7.0.1 ! ,-)

See, my .sig comes only once. And it's short:
-- 
Moooo.

afoster@ogccse.ogc.edu (Allan Foster) (09/11/89)

In article <1581@draken.nada.kth.se> h+@nada.kth.se (Jon W{tte) writes:
>In article <13517@well.UUCP> svc@well.UUCP (Leonard Rosenthol) writes:
>
>>	Sure I've heard of system crashes - though I try to write software
>>that doesn't do that too frequently!  But when it happens, my Mac REBOOTS! I
>>don't know about you (I am sure very few people do, or want to) but I don't
>
>Of course, my crashes may be spectacular. They wreck havoc in my System
>Resource Fork, making the Mac unable to boot from that disk. But then It's
>REAl safe :-) (Unless someone comes along with a system disk...)
>
>I also write:
>>>So, APPLE, why don't you run along and give us protected memory ? Huh ?
>
>>Why don't you find another forum for your protected memory flambe. You
>
>Because I want it, and I want it NOW ! Apple has all the source for the
>system, so they're in a far better position than I am to write that piece
>of software. And I'm gonna make REALLY sure that this is gonna be their
>prime goal for system 7.0.1 ! ,-)

Really?  I am not sure that I would like protected memory in 7.0.1 since that
means to be effective all my current software will break.  Not only the stuff
that I have written but most of the stuff I have purchased as well.

To have a memory protection system that is worth its salt, you would have to
protect the system heap.  Since most glue for current dev systems write
directly into the system heap.

Protected memory is something that Apple has Stated publicly that they are 
working on.  I would rather they spent the time on it aqnd did it RIGHT not
as a KLUDGE that does not do what is needed!

Waiting for properly implemented protected memory!~

Allan Foster
afoster@cse.ogc.edu



-- 
Allan Foster      UUCP  : tektronix!ogcvax!afoster
UseNet: afoster@cse.ogc.edu      GEnie  : A.FOSTER
AppleLink : D1663                  MacNet : FOSTER