"Gary Feldman" <GaryFeldman@discussions.microsoft.com> wrote in message
news:82C45463-30B4-4E01-8AA6-448E1B5D274C@microsoft.com...
> Does anyone know which encryption algorithm is used by NegotiateStream for
> encrypting the content? I can't find this anywhere in the documentation.
>
> And how long is the key, if that's not implied by the algorithm?
>
> Thanks,
>

"Joe Kaplan (MVP - ADSI)" wrote:

> Unfortunately, it isn't that straightforward as the encryption is whatever
> is negotiated by the negotiate protocol.

"Gary Feldman" <GaryFeldman@discussions.microsoft.com> wrote in message
news:7C478F3E-BA8B-4DD5-9C63-D66B05A04FC2@microsoft.com...
>
>
> "Joe Kaplan (MVP - ADSI)" wrote:
>
>> Unfortunately, it isn't that straightforward as the encryption is
>> whatever
>> is negotiated by the negotiate protocol.
>
> Thanks. Your reply triggered my memory of looking at the Microsoft
> CryptoAPI several years ago, includind seeing a table of CSPs that
> normally
> ship with each operating system (but which I can't find anymore).
>
> Intuitively, the implementation should either be using one of the
> providers
> defined in system.security.cryptography, or one that's available via the
> CryptoAPI. Correct? If the latter, they can be found in the registry,
> but
> it's not clear how .Net may get repackaged for different countries. Or
> perhaps the .Net system.security.cryptography package is the same
> everywhere,
> and it's the presence or absence of the underlying CSP that determines
> whether or not that particular feature is available.
>
> That still leaves one question in my mind? Is there any insight into how
> the negotiate protocol picks one from the available matches?
>
> Thanks

> "Joe Kaplan (MVP - ADSI)" wrote:
>
>> Unfortunately, it isn't that straightforward as the encryption is
>> whatever is negotiated by the negotiate protocol.
>>
> Thanks. Your reply triggered my memory of looking at the Microsoft
> CryptoAPI several years ago, includind seeing a table of CSPs that
> normally ship with each operating system (but which I can't find
> anymore).
>
> Intuitively, the implementation should either be using one of the
> providers defined in system.security.cryptography, or one that's
> available via the CryptoAPI. Correct? If the latter, they can be
> found in the registry, but it's not clear how .Net may get repackaged
> for different countries. Or perhaps the .Net
> system.security.cryptography package is the same everywhere, and it's
> the presence or absence of the underlying CSP that determines whether
> or not that particular feature is available.
>
> That still leaves one question in my mind? Is there any insight into
> how the negotiate protocol picks one from the available matches?
>
> Thanks
>