通过API交换ECC密钥时有标准格式吗? [英] Is there a standard format when exchanging an ECC key through an API?

查看:93
本文介绍了通过API交换ECC密钥时有标准格式吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们将通过API公开ECC公共密钥(将来可能还会有其他非对称公共密钥),而我想知道返回ECC密钥时是否有标准格式可以使用? /p>

这种想法是,API的用户可以获得一个ECC公共密钥,用于加密数据,然后可以通过另一个API将其导入系统.用户可能正在使用其他平台来加密其数据,因此对于 公钥应该看起来像返回API一样?

例如,应该将x和y参数组合并作为一个十六进制字符串返回,还是应该返回十六进制的公共密钥Blob(公共密钥Blob是.NET特定对象)?还是应该返回一个xml格式标准?

 

解决方案

 

 

感谢您的问题,我们正在研究这种情况,可能需要一些时间才能回复您.


We'll be exposing an ECC public key (and perhaps other asymmetric public keys in the future) through an API, and I'm wondering if there is a standard format to use when returning the ECC key?

The thought is that the user of the API could get an ECC public key to use to encrypt data, that can then be imported into the system via a different API. The user may be using a different platform to encrypt their data, so is there a standard for what the public key should look like on the return of the API?

For example, should the x and y parameters be combined and returned as one hex string, or should the public key blob hex be returned (is the Public Key blob a .NET specific thing)? Or is there an xml format standard that should be returned?

 

解决方案

 

Hi,

 

Thank you for your question, we're doing research on this case, it might take some time before we get back to you.


这篇关于通过API交换ECC密钥时有标准格式吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆