feat(picky-krb): implement Kerberos encryption without a checksum #342
+534
−65
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I added the possibility of Kerberos encryption but without a checksum. We need this functionality to support
SECBUFFER_READONLY
andSECBUFFER_READONLY_WITH_CHECKSUM
flags for security buffers insspi-rs
. Related to: Devolutions/sspi-rs#120Additionally, I reviewed the
crypto
module inpicky-krb
. It seems like Kerberos encryption algorithms were implemented a long time ago. We can refactor it by usingcts
andaes
crates and get rid of the customcts
mode implementation. Let's create an issue for the future.Docs & reference:
SecBuffer
structure (sspi.h).