Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA07631; Tue, 5 Dec 95 05:11:52 EST
Received: from MITVMA.MIT.EDU by MIT.EDU with SMTP
	id AA29000; Tue, 5 Dec 95 05:10:46 EST
Message-Id: <9512051010.AA29000@MIT.EDU>
Received: from MITVMA.MIT.EDU by mitvma.mit.edu (IBM VM SMTP V2R3)
   with BSMTP id 8316; Tue, 05 Dec 95 05:11:41 EST
Received: from CNSIBM.ALBANY.EDU (NJE origin MAILER@ALBNYVM1) by MITVMA.MIT.EDU
 (LMail V1.2a/1.8a) with BSMTP id 1652; Tue, 5 Dec 1995 05:11:41 -0500
Received: from CNSIBM.ALBANY.EDU (NJE origin MAILER@ALBNYVM1) by
 CNSIBM.ALBANY.EDU (LMail V1.2a/1.8a) with BSMTP id 4335; Tue,
 5 Dec 1995 05:09:37 -0500
Date:     Tue, 5 Dec 1995 05:09:36 -0500
Reply-To: Postmaster@CNSIBM.ALBANY.EDU
From: RFC822 mailer (LMail release 1.2a/1.8a) <MAILER@CNSIBM.ALBANY.EDU>
Subject:  Undelivered mail
To: owner-kerberos@MIT.EDU
X-Report-Type: Nondelivery; boundary="> Error description:"

An error was detected while processing the enclosed message. A list of
the affected recipients follows. This list is in a special format that
allows software like LISTSERV to automatically take action on incorrect
addresses; you can safely ignore the numeric codes.

--> Error description:
Error-For:  JEO01@ALBNYDH2.BITNET
Error-Code: 1
Error-Text: Node ALBNYDH2 is unknown as of VERS9512.

Error-End:  One error reported.

------------------------- Rejected message (34 lines) -------------------------
Received: from MIT.EDU by CNSIBM.ALBANY.EDU (IBM VM SMTP V2R2) with TCP;
   Tue, 05 Dec 95 05:09:35 EST
Received: from pad-thai.cam.ov.com by MIT.EDU with SMTP
        id AA26661; Tue, 5 Dec 95 04:07:08 EST
Received:  by pad-thai.cam.ov.com (8.6.12/)
        id <EAA03851@pad-thai.cam.ov.com>; Tue, 5 Dec 1995 04:10:54 -0500
Received: from GATEWAY by pad-thai.cam.ov.com with netnews
        for kerberos-wrapper@cam.ov.com (kerberos@mit.edu)
To: kerberos@MIT.EDU
Date: 4 Dec 1995 10:35:22 GMT
From: aldini@zeus.csr.unibo.it (Alessandro Aldini mat.1193)
Message-Id: <49uita$o5i@sirio.cineca.it>
Organization: Cineca
Sender: usenet@cam.ov.com
Subject: Help about Kerberos (TGT request)

 I read from "Firewalls and Internet Security" about the Kerberos
 Authentication System :
 Kerberos principals may obtain tickets for services from a special server
 known as the Ticket Granting Server (TGS).
 The client "speaks" to TGS with a private key and he obtains this key at
 session-start time from KDC (key distribution centre). The client
 makes a request to the KDC to obtain this key (and other information for
 the TGS) and the KDC reply with an encrypted messagge; the key used for this
 messagge is
 the client private key, so the KDC must know the private key of every user.
 The client key is derived from a noninvertible transform of the user's
 typed password. I suppose that KDC uses a secret algorithm to obtain the
 private key from the password and every client knows his own password and
 key but not the algorithm password-to-key. Is it true ? Otherwise how can
 KDC know every client private key ?
 Please answer me in e-mail. Thank you for your help.
 CIAO, Alessandro.

