Provide Structured SerializedData in PacCredentialInfo
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- authentication, security
Research direction
Start by locating the PacCredentialInfo structure and its CredentialType.SerializedData handling. Compare the current representation with the MS-PAC CredentialType specification linked in the issue, then define the structured result and verify that it supports the described WHfB and smartcard scenarios.
Written by the indexing model from the issue text.
Description
Hi, it would be nice to provide a solution to deal with the SerializedData in PAC's CredentialType (PacCredentialInfo structure).
This could be quite useful for WHfB/smartcard users to obtain their NTLM hash in that encrypted NTLM_SUPPLEMENTAL_CREDENTIAL blob after the User-to-User authentication, in order to perform NTLM authentication to access some dedicated resources.
At least the SerializedData should be further structured as described in https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-pac/2f9cae55-350a-423e-a692-1d16659e544a
- Dominant language
- C#
- Stars
- 567
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/Kerberos.NET
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dotnet/Kerberos.NET#394 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
dotnet/Kerberos.NET#435 · 4 reactions ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
dotnet/Kerberos.NET#434 · 4 reactions ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
dotnet/Kerberos.NET#433 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 66/100
dotnet/Kerberos.NET#428 · 8 comments ·
All issues in dotnet/Kerberos.NET
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·