[19987] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Using a master key and principal name to derive password for

daemon@ATHENA.MIT.EDU (Roland C. Dowdeswell)
Wed Oct 16 07:15:53 2019

Date: Wed, 16 Oct 2019 12:15:45 +0100
From: "Roland C. Dowdeswell" <elric@imrryr.org>
To: Ts7 Coe <tm3y@hotmail.com>
Message-ID: <20191016111545.GB23133@xiombarg.imrryr.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <HK2PR06MB3539B86595CCCE03EBBACCE59C920@HK2PR06MB3539.apcprd06.prod.outlook.com>
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu

On Wed, Oct 16, 2019 at 10:33:29AM +0000, Ts7 Coe wrote:
>

>    > Then you don't actually need keys at all. If no one is going to
> 
>    make an AS_REQ or TGS_REQ with the principal as a target, then you
>    do not need keys.
> 
>    The principals will authenticate with each other, so any principal
>    could be a target of TGS_REQ. So I thinks there still must be keys
>    for every principal?

How will the principals know their keys?

--
    Roland C. Dowdeswell                   http://Imrryr.ORG/~elric/
_______________________________________________
krbdev mailing list             krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

home help back first fref pref prev next nref lref last post