[Opensc-commits] [OpenSC/OpenSC] 5713f5: pkcs11: Add CK_GCM_MESSAGE_PARAMS and CK_GENERATOR...

[Jakub J. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/OpenSC/OpenSC
  Commit: 5713f5053cec5a852f46673d81858fd99011818a
      https://github.com/OpenSC/OpenSC/commit/5713f5053cec5a852f46673d81858fd99011818a
  Author: Jakub Jelen <jj...@re...>
  Date:   2025-05-30 (Fri, 30 May 2025)

  Changed paths:
    M src/pkcs11/pkcs11-display.c
    M src/pkcs11/pkcs11-display.h
    M src/pkcs11/pkcs11.h

  Log Message:
  -----------
  pkcs11: Add CK_GCM_MESSAGE_PARAMS and CK_GENERATOR_FUNCTION definitions

Signed-off-by: Jakub Jelen <jj...@re...>


  Commit: 5b7fb6d26d745e460291c839185a26daf0d18f61
      https://github.com/OpenSC/OpenSC/commit/5b7fb6d26d745e460291c839185a26daf0d18f61
  Author: Jakub Jelen <jj...@re...>
  Date:   2025-05-30 (Fri, 30 May 2025)

  Changed paths:
    M src/pkcs11/pkcs11-spy.c

  Log Message:
  -----------
  pkcs11-spy: Improve printing mechanism parameters

Some mechanisms in PKCS#11 3.0 have different parameters so when printing them, we need to take into the
account the context where the parameter is provided. In this case, the AES-GCM mechanisms has different
parameters when called with normal C_Encrypt() API and message based C_MessageEncryptInit() API. Not following
the context leads into printing nonsense.

I also took the opportunity here to make sure the parameters length is verified against the expected parameter
size and possible inconsistencies reported.

Signed-off-by: Jakub Jelen <jj...@re...>


Compare: https://github.com/OpenSC/OpenSC/compare/2742f82e74db...5b7fb6d26d74

To unsubscribe from these emails, change your notification settings at https://github.com/OpenSC/OpenSC/settings/notifications