Path: utzoo!attcan!uunet!motcid!king
From: king@cell.mot.COM (Steven King)
Newsgroups: comp.sys.amiga
Subject: Re: WB 1.3.2
Summary: How would public keys solve matters?
Keywords: encrypt workbench release
Message-ID: <188@grape3.UUCP>
Date: 30 Sep 89 22:22:39 GMT
References: <14203@polyslo.CalPoly.EDU> <7825@cbmvax.UUCP> <6068@tekigm2.MEN.TEK.COM> <7850@cbmvax.UUCP> <6097@tekigm2.MEN.TEK.COM> <226@estinc.UUCP> <193@teslab.lab.OZ>
Reply-To: king@grape3.UUCP (Steven King)
Organization: Motorola Inc. - cellular Infrastructure Div., Arlington Heights, IL 60004
Lines: 16

In article <193@teslab.lab.OZ> andrew@teslab.lab.OZ writes:
>Using a public-key encryption system could ensure that any release you
>got was the real thing.  Commodore would encrypt the software using their
>secret key.  If you can decrypt it correctly using their public key then
>you can be certain that it hasn't been tampered with.

I'm not sure I understand the usefulness of this; maybe I just don't know all
the ins and outs of encryption.  Wouldn't it be possible for the industrious
virus-producer to decrypt the software, infect it, and then encrypt it again
in such a way that the public key will still retrieve it?

/-----------------------------------------------------------------------------\
| Never hold down the "k" key.  It tends to put  | Steve King  (312) 991-8056 |
| a lot of "k"s on the screen.                   |   ...uunet!motcid!king     |
|                                                |   ...ddsw1!palnet!stevek   |
\-----------------------------------------------------------------------------/