1995-12-19 - Securing the end-points

Header Data

From: GLEN_MCBRIDE@BayNetworks.com (Glen McBride)
To: cypherpunks@toad.com
Message Hash: 7f2523243eb229eab49eeaf25c5b94000038fada93fddf25e25be4e383314dee
Message ID: <608235518.31497752@BayNetworks.com>
Reply To: N/A
UTC Datetime: 1995-12-19 00:45:26 UTC
Raw Date: Tue, 19 Dec 1995 08:45:26 +0800

Raw message

From: GLEN_MCBRIDE@BayNetworks.com (Glen McBride)
Date: Tue, 19 Dec 1995 08:45:26 +0800
To: cypherpunks@toad.com
Subject: Securing the end-points
Message-ID: <608235518.31497752@BayNetworks.com>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

Greetings!
I was wondering if in addition to all the work and discussion regarding
crypto which generally centres around the transmission path information takes
traveling from end-point to end-point, there is any work being done to secure
the end-points themselves (I.e. files on your PC etc.)

In my view the end-points present the most vulnerability in the overall
message path from person to person. It is at these points that the
message/information exists as cleartext even if for a short period of time.
While of course it is possible to PGP encode your files is this a practical
way to go about securing your system? I am aware or RSA secure but is that
all there is out there?

Thanks in advance

Glen McBride
Bay Networks ASIA-PAC customer service 
Australia

Views are my own and do not represent those of my employer

===== CURRENT PGP KEY FOLLOWS =====
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2

mQERAzDFDk4AAAEIAJvkPKWMS8TR5eNNQZw5FjUg8roSe/wFdw3d8vCEfb2lX3G+
qBAQKuTSUAhO8marZvNWF9VPuyqkOGEOrwzdont8jSHAdF9dguh1sP56eGXzyn8n
mDN1Fw8vQiNrttvCEYUjvLEML8tFlLc7QlQRkAMEGrkH29D4ck3wOkJLEaSZrTcO
RIZAzOBVVvrJORVKsREnGG4IrItJCiREw7Gp/LXIHMSEBCdu2+uaNc9nHQxKcYZc
yx9UiiZ0XP6TzzUtkD00ZDtO8OdZCAhXdj0zbCUKVrzuY37EgnFVFQ7SlZZAQn/U
Jx26k0eZvZhXjhSVd3QyElbJYNFVLrdyU+h+Gt0AIwQAAAABtCpHbGVuIE1jQnJp
ZGU8R0xFTl9NQ0JSSURFQGJheW5ldHdvcmtzLmNvbT4=
=N/lg
- -----END PGP PUBLIC KEY BLOCK-----


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQEVAwUBMNS1vy63clPofhrdAQHn1wgAjHV2vKXIEY4qZ/Rm2rq4hnJsUJDt+zd5
BbYo/BZBruwX+gqylYlbOemkPvZ7ktAMdu9jUFfaJQ7Cb3jT4kgfp2dqqle6yaq1
0nxU9m7BMiVnSqevtK5Fy+thR/yVZWdHi1LFMy48yp8FCaqvMkEruscOsG0ydUNM
lyf3OCNGdN7LQcxQkRE9UzKPwEpacDD/afU5W5aZhhchkpAH9t/kqKzvgXxia1VF
4hfOEcCMN21JO6QGqdnHASVNoIdV44O6BlUPhv5omAqofgU58tnbJ9G3/24zjecM
QhxTMGBv+aDB1DtQ+k9wDJTdPBLwhqyWUZWImN3RPVnQb1Ec1CVM8A==
=yLIB
-----END PGP SIGNATURE-----






Thread