[38759] in Kerberos
Re[2]: MIT Kerberos Master principal deletion
daemon@ATHENA.MIT.EDU (Chris Hecker)
Thu Jun 11 18:57:02 2020
From: "Chris Hecker" <checker@d6.com>
To: "Nico Williams" <nico@cryptonector.com>
Date: Thu, 11 Jun 2020 22:54:32 +0000
Message-ID: <emfc355d5e-e51f-43fa-a88a-4cf2cb5ca3de@checker-t530>
In-Reply-To: <20200611222158.GD3080@localhost>
MIME-Version: 1.0
Cc: Harshawardhan Kulkarni <harshawardhan.rk@gmail.com>,
"kerberos@mit.edu" <kerberos@mit.edu>
Reply-To: Chris Hecker <checker@d6.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
> I don't think it would make it harder.
I just mean because you won't be able to set a breakpoint at a function
that uses the key, you'll have to actually chase it around in memory
(assuming you use something like gcore to dump it as fast as possible
without regard to where it is executing when it's dumped).
If I was doing this live, I'd set a breakpoint on some function that
used the key to decrypt and then inspect there, but with a core file
you'll need to make sure you can find all the structures first.
Is realm_mkey in the kdc_realm_data struct the one he wants?
Chris
------ Original Message ------
From: "Nico Williams" <nico@cryptonector.com>
To: "Chris Hecker" <checker@d6.com>
Cc: "Harshawardhan Kulkarni" <harshawardhan.rk@gmail.com>;
"kerberos@mit.edu" <kerberos@mit.edu>
Sent: 2020-06-11 15:31:28
Subject: Re: MIT Kerberos Master principal deletion
>On Thu, Jun 11, 2020 at 10:19:39PM +0000, Chris Hecker wrote:
>> Maybe dump the core of the running process so you don't accidentally crash
>> it while trying to debug it live? But that would make finding it in memory
>> even harder...
>
>I don't think it would make it harder.
>
>BTW, we should make it much harder to delete important principals...
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
