Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Legacyp12 playbook #464

Merged
merged 9 commits into from
May 8, 2024
Merged

Conversation

Pmaraveyias
Copy link
Collaborator

Addresses Issue #431. Allows the use of legacy p12 as an option in playbooks, but must be specifically chosen.

@BeardedPrincess
Copy link
Collaborator

I added a PR to update the playbook readme as well: #465

@BeardedPrincess
Copy link
Collaborator

Validated using Windows Server 2016 and the useLegacyPkcs12 flag in CAPI installation playbook worked. Also verified it's still broken if that flag is absent or set to false.

Additionally, tested both toggles true and false with an installation type of PKCS12. Worked as expected, based on openssl results:

useLegacyPkcs12: true :

MAC: sha1, Iteration 1
MAC length: 20, salt length: 8
PKCS7 Encrypted data: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048
Certificate bag
Certificate bag
Certificate bag
PKCS7 Data
Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants