1996-02-01 - Re: Authentication of crypto clients

Header Data

From: andreas@horten.artcom.de (Andreas Bogk)
To: Raph Levien <raph@c2.org>
Message Hash: cca1fcb4499b7a3dcbf69ff9cc68911671ad4f77d34e04e43ca3b446eac80c8c
Message ID: <y8aviluxq4k.fsf@horten.artcom.de>
Reply To: <Pine.SUN.3.91.960129160857.27262A-100000@infinity.c2.org>
UTC Datetime: 1996-02-01 07:01:47 UTC
Raw Date: Thu, 1 Feb 1996 15:01:47 +0800

Raw message

From: andreas@horten.artcom.de (Andreas Bogk)
Date: Thu, 1 Feb 1996 15:01:47 +0800
To: Raph Levien <raph@c2.org>
Subject: Re: Authentication of crypto clients
In-Reply-To: <Pine.SUN.3.91.960129160857.27262A-100000@infinity.c2.org>
Message-ID: <y8aviluxq4k.fsf@horten.artcom.de>
MIME-Version: 1.0
Content-Type: text/plain


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

>>>>> "Raph" == Raph Levien <raph@c2.org> writes:

    Raph> The issue is: how does the crypto provider authenticate the
    Raph> client?

If you consider the client to be untrusted software, I'm afraid the
answer is probably not at all.

Andreas


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAgUBMQ2eeUyjTSyISdw9AQG6RgP+KNg7GbFVvs+L2AxmyWL6rsBBZ8lB7gX9
ZrK7Xros5SclXVmxqIPdlJsl6KqzrTCkk21ZzDsAtbvRCPdaEHouQ2l5tPqMr3BY
OQYpL7+hQmq9KHuh6VT8YLYn3JqMMcPevOb922wd2WpC2VlyjrPDY31sEwRizj2q
39UgEI/XMZE=
=zaAv
-----END PGP SIGNATURE-----





Thread