[20443] in Kerberos_V5_Development
Re: [External] : Re: Windows Credential Guard with MSLSA
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Sep 6 16:59:37 2023
From: Sam Hartman <hartmans@debian.org>
To: Seshan Parameswaran <seshan.parameswaran@oracle.com>,
"krbdev@mit.edu"
<krbdev@mit.edu>
In-Reply-To: <BYAPR10MB3479DDC2FF102C56220FA65A9DEFA@BYAPR10MB3479.namprd10.prod.outlook.com>
Date: Wed, 06 Sep 2023 14:58:30 -0600
Message-ID: <tsly1hjt3wp.fsf@suchdamage.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
>>>>> "Seshan" == Seshan Parameswaran <seshan.parameswaran@oracle.com> writes:
Seshan> I am running on Oracle Enterprise Linux and using MIT
Seshan> libraries. I am aware of the AllowTgtSessionKey Registry
Seshan> setting parameter that works when MSLSA is used without the
Seshan> Credential Guard. My query is specific to MSLSA used with
Seshan> Windows Credential Guard.
Your question doesn't make sense.
MSLSA is not a Linux thing:
MS -> Microsoft
LSA -> local security authority
The LSA exists on Windows systems.
If you are not on a Windows system, you don't have one.
It may be that you want to be asking about credential guard and Linux.
But involvind MSLSA or LSA in the discussion only confuses everyone.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
