I am required to store a certificate as ".arm" file only for a public key that is intended for use in RSA Encryption. I am currently able to generate the public key as ".key" file.
P.S I am new to encryption so, this may be a basic question.
|
I am required to store a certificate as ".arm" file only for a public key that is intended for use in RSA Encryption. I am currently able to generate the public key as ".key" file. P.S I am new to encryption so, this may be a basic question. |
||||
|
|
|
Neither I can only guess The PEM format is exactly that. Assuming
|
|||||||||
|
|
Have no fears on being new - you've hit on a weird one. I swear I've seen *.arm used as an extension - but not often. Typically certificates (which include the public key as part of the data) are stored in either a binary (commonly called DER) or as ASCII (commonly called PEM). Most likely an *.arm certificate is one of those, hopefully without extra formatting. Here's a quick rundown of the really common types of storage along with some command line instructions for one of the most common open source tools for certificate manipulation - OpenSSL. It's probably worthwhile to ask what the consumer of this data will be, get access to the software or a test kit and run tests. You try a basic PEM or DER encoding and change the file type to *.arm just to see if it works. Given that this is non-standard, you may have to check back with the stakeholders who need this requirement to see if they can give you the format of this... sadly, you may end up developing it yourself - unless they can also give you an API for generating it... |
|||
|
|
|
Following code solved my problem.
|
|||
|
|