Compatibility Issues with OpenSSL

Hello All,

We are currently integrating *OpenSSL* with *Windows Schannel SSPI* in a
bidirectional setup—where OpenSSL acts both as a *client* and a *server*,
and vice versa.

Our observations are as follows:

   -

   When using the *SCHANNEL_CREDENTIALS* structure with Schannel, the
   implementation works as expected—successfully performing the TLS handshake,
   data encryption, and decryption without issues.
   -

   However, when switching to the *SCH_CREDENTIALS* structure, we encounter
   an unexpected behavior:
   -

      The *TLS handshake completes successfully*, indicating that the
      initial authentication works.
      -

      Yet, *data encryption and decryption operations fail*, preventing
      secure communication post-handshake.

This discrepancy suggests that while SCH_CREDENTIALS supports the initial
authentication phase, it might lack certain configurations required for
subsequent cryptographic operations.

*Request for Assistance:*
Has anyone encountered a similar issue when using SCH_CREDENTIALS with
OpenSSL? If so, could you provide insights or recommendations on how to
resolve this? Possible considerations include:

   -

   Required flags or settings in SCH_CREDENTIALS for enabling
   encryption/decryption.
   -

   Differences in behavior between SCHANNEL_CREDENTIALS and SCH_CREDENTIALS in
   this context.
   -

   Any known compatibility issues between Schannel’s credential structures
   and OpenSSL.

We appreciate any guidance or references to documentation that could help
resolve this problem.

-- 
Regards,
Siddharth

-- 
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/CAN3pozF%3D9y%3DV2QV%2BfutWiziUnZSt0UMF7OwXMQUmGYZXh-Pe7A%40mail.gmail.com.