We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In our project, we need to work with SHA256 (for security reasons).
There is a call of the openssl_sign function here: https://github.com/Pixidos/gpwebpay-core/blob/master/src/Signer/Signer.php#L56, but there is no way how to provide the fourth argument that determines the algorithm used.
openssl_sign
Is there a change that the API will be extended or should I send a pull request?
Thank you very much,
Vojtěch
The text was updated successfully, but these errors were encountered:
feat: add optional parameter for configure ssl algorithm in Singer / #35
e66df50
I have released version 2.2.1 which allows setting the encryption algorithm as the 3rd parameter in the Singer constructor.
Sorry, something went wrong.
1390666
This was super fast. 👍🙂 Thank you!
No branches or pull requests
In our project, we need to work with SHA256 (for security reasons).
There is a call of the
openssl_sign
function here: https://github.com/Pixidos/gpwebpay-core/blob/master/src/Signer/Signer.php#L56, but there is no way how to provide the fourth argument that determines the algorithm used.Is there a change that the API will be extended or should I send a pull request?
Thank you very much,
Vojtěch
The text was updated successfully, but these errors were encountered: