ISO 7816如何使用多次计算签名命令apdu

发布于 2025-01-24 08:01:48 字数 546 浏览 0 评论 0原文

我会采取以下步骤将具有ISO7816标准的智能卡签署单个数据。

  1. 选择MF
  2. 选择DF
  3. 验证PIN管理
  4. 安全环境
  5. 计算数字签名

,如果我想签署多个数据,请按照以下步骤操作:

  1. 选择MF
  2. 选择DF验证
  3. PINIFY PIN
  4. 管理安全环境
  5. 计算数字签名1
  6. 验证PIN PIN
  7. 管理安全环境
  8. 计算数字签名2
  9. 验证PINIFY PIN
  10. MANAKANG安全环境
  11. 计算数字签名3

我是否必须每次进行验证并管理安全环境步骤?

如果我尝试以下步骤:

  1. 选择MF
  2. 选择DF
  3. 验证PIN
  4. 管理安全环境
  5. 计算数字签名1
  6. 计算数字签名2

我在步骤6中获得了69 82(不满足的安全状况)。

I do the following steps for signing a single data with a smart card with the ISO7816 standard.

  1. Select MF
  2. Select DF
  3. Verify Pin
  4. Manage security environment
  5. Compute digital signature

If I want to sign multiple data then I follow these steps :

  1. Select MF
  2. Select DF
  3. Verify Pin
  4. Manage security environment
  5. Compute digital signature 1
  6. Verify Pin
  7. Manage security environment
  8. Compute digital signature 2
  9. Verify Pin
  10. Manage security environment
  11. Compute digital signature 3

Do i have to do VerifyPin and manage security environment steps everytime?

If I try these steps:

  1. Select MF
  2. Select DF
  3. Verify Pin
  4. Manage security environment
  5. Compute digital signature 1
  6. Compute digital signature 2

I'm getting 69 82 (Security condition not satisfied.) in step 6.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

幻想少年梦 2025-01-31 08:01:48

您所描述的是通常称为 bulk签名的概念。它得到了某些卡的支持,但很可能需要修改用于在发行之前设置卡或其他订购选项的个性化序列。更安全的标准行为(如示例中所观察到的那样)是,签名过程使获得的访问权利耗尽。

有严重的法律障碍,因为数字签名被认为是A Willful Act ,因此暗示您意识到自己签名并打算通过输入PIN来做的事情。在要求A Bumb Signature 的条件下,通常必须将大量的组织安全规定补充到环境中,因此打算签署电子处方的医生必须使读取器保持在范围内。他/她的持续监督。

有更多限制的散装签名形式,其中不得每次都必须输入销钉,但是每次第10次都可以进入,因为无限的签名能力太危险了。

只是为了澄清这一点:如果每台引脚条目的单个签名刻连接卡片,则应用程序无能为力来实现散装签名。

总结:虽然PIN条目证明了合法卡持有人的存在,但这对于数字签名的 Willful ACT 方面都是不足的。

What you are describing is the concept typically called bulk signature. It is supported by some cards, but most likely this requires a modification of the personalization sequence used to setup the card before issuance or a different ordering option. The more secure standard behavior (as you observe in the example) is, that the acquired access right is exhausted by the signing process.

There are serious legal obstacles, since digital signatures are considered as a willful act, so imply that you were aware of what you signed and intended to do so by entering the PIN. Under conditions asking for a bulk signature, typically considerable organizational security provisions have to be supplemented to the environment, so a doctor, who intends to sign electronic prescriptions, has to make plausible, that the card reader is under his/her continuous supervision.

There are more restricted forms of bulk signature, where the PIN has not to be entered every time, but e.g. every 10th time, since the unlimited signature capability is too dangerous.

Just to clarify this: if a card is hardwired for single signature per PIN entry, there is nothing an application can do to achieve bulk signature instead.

Summarized: While a PIN entry proves the presence of the legitimate card holder, this is insufficent for the willful act aspect of digital signatures.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文