🚀 go-pugleaf

In article <Bwq6DM.AC0@immd4.informatik.uni-erlangen.de> 
(Markus Kuhn) writes: 
              ....
> Using encription or signature keys (even public ones) makes only sense,
> if they are distributed over a system completely independent from the
> system used for transporting the message. Otherwise intermediate nodes

        Here we go again! Read My Lips: Routinely published public
        keys are for _privacy_. If you have deep, dark secrets to
        protect, by all means, use a multi-channel key management
        protocol.

        On the other hand, if you don't think you are likely to be the
        target of a very expensive intercept operation, if you don't
        want everybody in every computer room along the Internet
        (including your boss and the loud-mouthed kid they just hired
        as email sysadmin on your site) reading your mail, and if you
        don't want your messages routinely scanned for key words by a
        half-dozen lettered agencies on fishing expeditions, publish a
        public key.

        Every so often, find a separate channel to check that your
        published key is in fact the one you sent (log in as 'guest'
        to a FreeNet host, or have a friend at another site print off
        one of your postings). If it doesn't match, call your lawyer;
        you are probably in very deep doo-doo with some very powerful
        people.

        For you 'security experts' out there: Try to see through your
        paranoid fog long enough to understand that there's more than
        one use for crypto. Every one of you knows that a locked door
        won't keep out a determined burglar - but you lock your doors
        anyway. Published keys work the same way: they make sure that
        an invasion of privacy takes extraordinary measures that are
        likely to be detected.


---
 Marc Thibault        |  Consulting Systems Analyst  |  The PC: Colt '45
 marc@tanda.isis.org  |  R.R.1, Oxford Mills,        |  of the information
 CIS:71441,2226       |  Ontario, Canada  K0G 1S0    |   frontier
 NC FreeNet: aa185    |                              |

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.0

mQBNAiqxYTkAAAECALfeHYp0yC80s1ScFvJSpj5eSCAO+hihtneFrrn+vuEcSavh
AAUwpIUGyV2N8n+lFTPnnLc42Ms+c8PJUPYKVI8ABRG0I01hcmMgVGhpYmF1bHQg
PG1hcmNAdGFuZGEuaXNpcy5vcmc+
=HLnv
-----END PGP PUBLIC KEY BLOCK-----