[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Announcing Bellcore's Trusted Software Integrity (Betsi) System

To: [email protected]
Subject: Re: Announcing Bellcore's Trusted Software Integrity (Betsi) System
From: "L. Todd Masco" <[email protected]>
Date: Mon, 29 Aug 1994 18:12:41 -0400
Cc: [email protected]
In-Reply-To: <Chameleon.4.01.1.940829165513.merriman@anybody.metronet.com.metronet.com>
References: <Chameleon.4.01.1.940829165513.merriman@anybody.metronet.com.metronet.com>
Sender: [email protected]

[email protected] writes:
 > Or to warn potential virus "authors" that *their* anonymity is no longer 
 > assured - not a bad thing. Not enough to justify the rest of it, IMHO, but 
 > certainly not Evil Incarnate (not to be flinging misinterpretations or 
 > aspersions :-)

Certainly not enough to justify the rest: Can you name one example of an
 author of a package including some virus?  Not someone putting one
 post-production (individual signing will prevent that), but the original
 author?

It's a straw man.
--
L. Todd Masco  | "Which part of 'shall not be infringed' didn't
[email protected]  |   you understand?"

Follow-Ups:
- Re: Announcing Bellcore's Trusted Software Integrity (Betsi) System
  - From: Jim Gillogly <[email protected]>
- Re: Announcing Bellcore's Trusted Software Integrity (Betsi) System
  - From: Brad Huntting <[email protected]>

References:
- Re: Announcing Bellcore's Trusted Software Integrity (Betsi) System
  - From: [email protected]

Prev by Date: Re: Statistics on remail message sizes
Next by Date: e$: e-cash underwriting
Prev by thread: Re: Announcing Bellcore's Trusted Software Integrity (Betsi) System
Next by thread: Re: Announcing Bellcore's Trusted Software Integrity (Betsi) System
Index(es):
- Date
- Thread