Searched hist:"897357879 e4a88587bb91d8f7e9dd66e2b3c4d6f" (Results 1 – 3 of 3) sorted by relevance
| /optee_os/ta/pkcs11/src/ |
| H A D | pkcs11_attributes.h | 897357879e4a88587bb91d8f7e9dd66e2b3c4d6f Tue Jan 12 09:15:03 UTC 2021 Ruchika Gupta <ruchika.gupta@linaro.org> ta: pkcs11: Deal with the private objects in C_Logout
The logic to deal with the private objects was missing in the
C_Logout() implementation.
PKCS#11 specification states that :
When C_Logout successfully executes, any of the application’s
handles to private objects should become invalid (even if a user
is later logged back into the token, those handles remain invalid).
In addition, all private session objects from sessions belonging
to the application should also be destroyed.
In addition, also release any ongoing cryptographic or
object-finding operations that may be associated with the session
while logging out.
Signed-off-by: Ruchika Gupta <ruchika.gupta@linaro.org>
Reviewed-by: Etienne Carriere <etienne.carriere@linaro.org>
|
| H A D | pkcs11_token.c | 897357879e4a88587bb91d8f7e9dd66e2b3c4d6f Tue Jan 12 09:15:03 UTC 2021 Ruchika Gupta <ruchika.gupta@linaro.org> ta: pkcs11: Deal with the private objects in C_Logout
The logic to deal with the private objects was missing in the
C_Logout() implementation.
PKCS#11 specification states that :
When C_Logout successfully executes, any of the application’s
handles to private objects should become invalid (even if a user
is later logged back into the token, those handles remain invalid).
In addition, all private session objects from sessions belonging
to the application should also be destroyed.
In addition, also release any ongoing cryptographic or
object-finding operations that may be associated with the session
while logging out.
Signed-off-by: Ruchika Gupta <ruchika.gupta@linaro.org>
Reviewed-by: Etienne Carriere <etienne.carriere@linaro.org>
|
| H A D | pkcs11_attributes.c | 897357879e4a88587bb91d8f7e9dd66e2b3c4d6f Tue Jan 12 09:15:03 UTC 2021 Ruchika Gupta <ruchika.gupta@linaro.org> ta: pkcs11: Deal with the private objects in C_Logout
The logic to deal with the private objects was missing in the
C_Logout() implementation.
PKCS#11 specification states that :
When C_Logout successfully executes, any of the application’s
handles to private objects should become invalid (even if a user
is later logged back into the token, those handles remain invalid).
In addition, all private session objects from sessions belonging
to the application should also be destroyed.
In addition, also release any ongoing cryptographic or
object-finding operations that may be associated with the session
while logging out.
Signed-off-by: Ruchika Gupta <ruchika.gupta@linaro.org>
Reviewed-by: Etienne Carriere <etienne.carriere@linaro.org>
|