When upgrading the cryptographic library from v3 to v4, how to initialize the B parameter to keep it backward compatible(to NULL value) while instantiating ECC curve? Keeping B parameter NULL when generating digital signature gives issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-03-20 10:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-03-30 5:20 AM
Hi @KMahe.1​ ,
Please refer to the wiki article Security:Migration from previous Cryptographic Library version.
In this article, we precise:
Does this answer your question?
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-04-03 9:36 PM
Hi @Amel NASRI​ ,
Thanks for the update. Actually I had gone through this WiKi page and also initialised the B curve to a value for Curve P-256 as per DSS standards (FIPS 186-3) but just wanted to make sure if initialising it to this value keeps it backward compatible with the code where we had initialised parameter B to NULL value (while using version3). Do we see any change in signature generation due to this change in value? Please share your inputs on the same. Thanks!!
