PowerShell 7 nTSecurityDescriptor missing properties

[mrhousz]

Environment:
Locksmith 2024.3, installed from PSGallery using Install-Module Locksmith
Windows 10 Enterprise 22H2, July 2024 security updates
PowerShell 7.4.4

Issue:

Running Invoke-Locksmith in PowerShell 7 returns errors:

A constructor was not found. Cannot find an appropriate constructor for type System.Security.Principal.NTAccount.

This is due to missing object properties in the nTSecurityDescriptor object collected by Get-ADCSObject function.

Potential fix/workaround:

PowerShell/PowerShell#21540 (comment)

Import-Module Microsoft.PowerShell.Security prior to running Invoke-Locksmith results in the objects collected by Get-ADCSObject having the needed nTSecurityDescriptor properties

[SamErde]

Good find. We should be able to test that and add to the module manifest so you don't need to manually import it.

[TrimarcJake]

Agreed. Should be way fix. @SamErde you wanna handle or me?

[SamErde]

On it!

…

On Fri, Jul 26, 2024 at 6:50 AM Jake Hildreth ***@***.***> wrote: Agreed. Should be way fix. @SamErde <https://github.com/SamErde> you wanna handle or me? — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE4HWGISBGQQNYJALUQAI43ZOISXFAVCNFSM6AAAAABLPPQBUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJSGUYDAMZQHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[TrimarcJake]

Thank you, friend.

[mrhousz]

Thank you for this module and glad I could help. This was my first Github issue.