1997-10-23 - Re: Singaporean control freaks & CMR

Header Data

From: Anonymous <anon@anon.efga.org>
To: cypherpunks@cyberpass.net
Message Hash: 0043580f6dd2e17e2c8f89ae6d38c39321d15ea9d952a91b94ed6b8fa04e3e31
Message ID: <cb7aef8839502ded654b6de27813cb63@anon.efga.org>
Reply To: N/A
UTC Datetime: 1997-10-23 17:49:49 UTC
Raw Date: Fri, 24 Oct 1997 01:49:49 +0800

Raw message

From: Anonymous <anon@anon.efga.org>
Date: Fri, 24 Oct 1997 01:49:49 +0800
To: cypherpunks@cyberpass.net
Subject: Re: Singaporean control freaks & CMR
Message-ID: <cb7aef8839502ded654b6de27813cb63@anon.efga.org>
MIME-Version: 1.0
Content-Type: text/plain



Adam Back writes:
> The problem is that pgp5.x is both an email encryption system and a
> file encryption system.  So PGP Inc argue that they need the recovery
> features for files.  Well OK, but for emails in transit?

Define "in transit".  Specifically, when exactly does email stop being
"in transit".  When it is received on a mail server?  Transfered to the
destination computer?  Displayed to the user?  Saved in an archive?

How long might a piece of email spend "in transit"?  Compare and contrast
with the amount of time a piece of data from an encrypted phone call
spends in transit.  Or an SSL protected HTTPS web transaction.

Do you understand the difference between transit times of a fraction
of a second and of days or weeks?  Does this suggest any differences in
the need for recovery of encrypted data "in transit"?

Not all communications are alike.  The longer data spends "in transit"
the more need there is for recovery features.






Thread