Project

General

Profile

Development #101

Do not check for proper loading of a public key in LassoProvider constructor

Added by Benjamin Dauvergne about 9 years ago. Updated about 9 years ago.

Status:
Fermé
Priority:
Normal
Category:
Core
Target version:
Start date:
18 Jun 2010
Due date:
18 Jun 2010
% Done:

90%

Estimated time:
4.00 h
Patch proposed:
No
Planning:
No

History

#1 Updated by Benjamin Dauvergne about 9 years ago

The check was removed. But I also made straight the error code for missing keys or chain of cert when checking signatures:
- if a public keys or chain of cert was put, and we cannot load it, we return an error in the LASSO_DS_ERROR namepsace (like PUBLIC_KEY_LOADING_FAILED OR CHAING_OF_CERT_LOADING_FAILED).
- if there is no public key (and no chain of cert for XML signatures) we return LASSO_PROVIDER_ERROR_MISSING_PUBLIC_KEY.

#2 Updated by Clément Oudot about 9 years ago

Benjamin Dauvergne a écrit:

The check was removed. But I also made straight the error code for missing keys or chain of cert when checking signatures:
- if a public keys or chain of cert was put, and we cannot load it, we return an error in the LASSO_DS_ERROR namepsace (like PUBLIC_KEY_LOADING_FAILED OR CHAING_OF_CERT_LOADING_FAILED).
- if there is no public key (and no chain of cert for XML signatures) we return LASSO_PROVIDER_ERROR_MISSING_PUBLIC_KEY.

It is ok when loading provider into Lasso::Server object, but I still have the check when I load Lasso::Server from dump.

#3 Updated by Benjamin Dauvergne about 9 years ago

  • Status changed from Nouveau to Fermé

Also available in: Atom PDF