Decryption and Signing #2
sujeets-protean
started this conversation in
General
Replies: 4 comments 23 replies
-
Code Snippet for Decryption
|
Beta Was this translation helpful? Give feedback.
11 replies
-
Sample Encryption Key Pairs, Plain Text Challenge String, Encrypted Challenge String, ONDC Public Key
|
Beta Was this translation helpful? Give feedback.
5 replies
-
NPs can generate X25519 Encryption Key Pairs ======================================== openssl genpkey -algorithm x25519 -out x25519-priv.pem openssl pkey -in x25519-priv.pem -pubout -out x25519-pub.pem cat x25519-pub.pem cat x25519-priv.pem |
Beta Was this translation helpful? Give feedback.
3 replies
-
These are steps to generate ENCRYPTION key pairs that are used during registration and amendments.
For Header creation, please generate and use SIGNING key pairs.
Warm Regards,
Sujeet
From: krishna404 ***@***.***>
Sent: 03 September 2022 21:29
To: ONDC-Official/Pre-production ***@***.***>
Cc: Sujeet Suryawanshi ***@***.***>; Mention ***@***.***>
Subject: [External] Re: [ONDC-Official/Pre-production] Decryption and Signing (Discussion #2)
@sujeets-protean<https://github.com/sujeets-protean> using the keys generated using above method, when we try to create auth headers using in nodejs (as described here https://docs.google.com/document/d/1gfbhbhFMKnsRUHkJq9FfZ-9-KjNS0uCiW0kBkwTAOfA/edit?usp=sharing ) or using python ( as described here https://github.com/ONDC-Official/Pre-production/tree/main/signing_and_verification), we are getting the error invalid privateKey length
The private key generated using the openssl method described here is of 64 characters, whereas the scripts (python & nodejs) above are expecting a key of 88 characters. Pls advise.
—
Reply to this email directly, view it on GitHub<#2 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZUOXBLTYLBL65BYQTGRB7TV4NYUXANCNFSM53CDA7TA>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#2 (reply in thread)", "url": "#2 (reply in thread)", "name": "View Discussion" }, "description": "View this Discussion on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
****************************************************************************************************************************************************************************************************************This message is for the named addresses' use only. It may contain NSDL confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it. You must not, directly or indirectly,use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Unless otherwise stated, any commercial information given in this message does not constitute an offer to deal on any terms quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation.
*******************************************************************************************************************************************************************************************
|
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For Signing Key Pair Generation,
For Signing
Encryption/Decryption Key Pair Generation
For Decryption,
Beta Was this translation helpful? Give feedback.
All reactions