jeff/NSspi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add usage of the sequenceNumber and qualityOfProtection parameters, at least at the bottom layer. Upper layers don't right now, but we can change that later.

Browse Source
This commit is contained in:
antiduh
2014-07-01 21:59:42 +00:00
parent c891b70625
commit 57c2e8cc52
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
NSspi/Contexts/ContextNativeMethods.cs
View File

@@ -204,9 +204,9 @@ namespace NSspi.Contexts
{
status = ContextNativeMethods.EncryptMessage(
ref handle.rawHandle,
0,
qualityOfProtection,
bufferAdapter.Handle,
0
sequenceNumber
);
handle.DangerousRelease();
@@ -247,8 +247,8 @@ namespace NSspi.Contexts
status = ContextNativeMethods.DecryptMessage(
ref handle.rawHandle,
bufferAdapter.Handle,
0,
0
sequenceNumber,
qualityOfProtection
);
handle.DangerousRelease();
@@ -288,9 +288,9 @@ namespace NSspi.Contexts
{
status = ContextNativeMethods.MakeSignature(
ref handle.rawHandle,
0,
qualityOfProtection,
adapter.Handle,
0
sequenceNumber
);
handle.DangerousRelease();
@@ -331,8 +331,8 @@ namespace NSspi.Contexts
status = ContextNativeMethods.VerifySignature(
ref handle.rawHandle,
adapter.Handle,
0,
0
sequenceNumber,
qualityOfProtection
);
handle.DangerousRelease();