How to make sure SSPI crypt/sign functions does not change the input data buffer?   

HI All

I'm playing with EncryptMessage/DecryptMessage/MakeSignature/
VerifySignature functions on SSPI/Kerberos. There seems quite a lot of
combination to arrange the SecBufferDest argument. Is there a way to
make sure that the input data (includes data and signature) are never
changed in-place?

Thanks
Speedo

date: Mon, 7 Jul 2008 02:48:03 -0700 (PDT)   author:   Speedo

Re: How to make sure SSPI crypt/sign functions does not change the input data buffer?   

On Jul 7, 2:48 am, Speedo  wrote:
> HI All
>
> I'm playing with EncryptMessage/DecryptMessage/MakeSignature/
> VerifySignature functions on SSPI/Kerberos. There seems quite a lot of
> combination to arrange the SecBufferDest argument. Is there a way to
> make sure that the input data (includes data and signature) are never
> changed in-place?
>
> Thanks
> Speedo

Nope, I don't think so. If it's important to preserve the encrypted
bytes just make a copy and either perform the decrypt on the copied
bytes or the original but save the copy.

HTH,
Dave

date: Thu, 10 Jul 2008 06:18:38 -0700 (PDT)   author:   DaveMo