PKCS.rar_pkcs_pkcs-10_pkcs-1v2-1.pdf_安全协议

共13个文件

pdf：12个

txt：1个

版权申诉

pkcs

安全协议

115 浏览量 2022-09-21 04:46:06 上传评论收藏 1.53MB RAR 举报

资源推荐

资源详情

资源评论

收起资源包目录

PKCS.rar （13个子文件）

PKCS

pkcs-15v1_1.pdf 371KB

pkcs-12v1.pdf 69KB

pkcs-9v2-0a1.pdf 62KB

pkcs-5v2_1.pdf 255KB

pkcs-8v1-2.pdf 100KB

pkcs-7v1-5.pdf 180KB

pkcs-6v1-5.pdf 138KB

pkcs-1v2-1.pdf 172KB

pkcs-11v2-20a3.pdf 232KB

PKCS.pdf 53KB

pkcs-10v1_7.pdf 36KB

pkcs-3v1-4.pdf 117KB

www.pudn.com.txt 218B

identified as “RSA Security Inc. Public-Key Cryptography Standards (PKCS)” in all material mentioning or

referencing this document.

003-903078-110-001-000

PKCS #15 v1.1: Cryptographic Token Information Syntax

Standard

RSA Laboratories

June 6, 2000

Table of Contents

1 INTRODUCTION ...............................................................................................................................2

1.1 B

ACKGROUND

...................................................................................................................................2

1.2 I

NFORMATION ACCESS MODEL

...........................................................................................................4

2 TERMS AND DEFINITIONS............................................................................................................4

3 SYMBOLS, ABBREVIATED TERMS AND DOCUMENT CONVENTIONS.............................7

3.1 S

YMBOLS

...........................................................................................................................................7

3.2 A

BBREVIATED TERMS

........................................................................................................................7

3.3 D

OCUMENT CONVENTIONS

................................................................................................................8

4 OVERVIEW.........................................................................................................................................8

4.1 O

BJECT MODEL

..................................................................................................................................8

5 IC CARD FILE FORMAT .................................................................................................................9

5.1 O

VERVIEW

.........................................................................................................................................9

5.2 IC

CARD REQUIREMENTS

...................................................................................................................9

5.3 C

ARD FILE STRUCTURE

....................................................................................................................10

5.4 MF

DIRECTORY CONTENTS

..............................................................................................................10

5.5 PKCS #15

APPLICATION DIRECTORY CONTENTS

..............................................................................11

5.6 F

ILE IDENTIFIERS

.............................................................................................................................16

5.7 T

PKCS #15

APPLICATION

..........................................................................................................17

5.8 O

BJECT MANAGEMENT

....................................................................................................................18

6 INFORMATION SYNTAX IN ASN.1.............................................................................................20

6.1 B

ASIC

ASN.1

DEFINED TYPES

..........................................................................................................20

6.2 PKCS15O

BJECTS

............................................................................................................................29

6.3 P

RIVATE KEYS

.................................................................................................................................30

6.4 P

UBLIC KEYS

...................................................................................................................................34

6.5 S

ECRET KEYS

...................................................................................................................................37

6.6 C

ERTIFICATES

..................................................................................................................................38

6.7 D

ATA OBJECTS

.................................................................................................................................42

6.8 A

UTHENTICATION OBJECTS

..............................................................................................................43

6.9 T

HE CRYPTOGRAPHIC TOKEN INFORMATION FILE

, EF(T

OKEN

NFO

).................................................48

7 SOFTWARE TOKEN (VIRTUAL CARD) FORMAT..................................................................51

7.1 I

NTRODUCTION

................................................................................................................................51

7.2 U

SEFUL TYPES

.................................................................................................................................51

7.3 T

PKCS15T

OKEN TYPE

...............................................................................................................52

7.4 P

ERMITTED ALGORITHMS

.................................................................................................................53

A. ASN.1 MODULE...............................................................................................................................54

B. FILE ACCESS CONDITIONS.........................................................................................................67

B.1 S

COPE

..............................................................................................................................................67

B.2 B

ACKGROUND

.................................................................................................................................68

PKCS #15

1.1: C

RYPTOGRAPHIC

OKEN

NFORMATION

YNTAX

TANDARD

B.3 R

EAD

-O

NLY AND

EAD

-W

RITE CARDS

...........................................................................................68

C. AN ELECTRONIC IDENTIFICATION PROFILE OF PKCS #15 .............................................70

C.1 S

COPE

..............................................................................................................................................70

C.2 PKCS #15

OBJECTS

.........................................................................................................................70

C.3 O

THER FILES

....................................................................................................................................72

C.4 C

ONSTRAINTS ON

ASN.1

TYPES

......................................................................................................72

C.5 F

ILE RELATIONSHIPS IN THE

CARD CASE

......................................................................................72

C.6 A

CCESS CONTROL RULES

.................................................................................................................73

D. EXAMPLE PKCS #15 TOPOLOGIES...........................................................................................75

E. USING PKCS #15 SOFTWARE TOKENS.....................................................................................76

E.1 C

ONSTRUCTING A

PKCS#15

TOKEN IN SOFTWARE

..........................................................................76

F. NOTES TO IMPLEMENTORS.......................................................................................................78

F.1 D

IFFIE

-H

ELLMAN

, DSA

AND

KEA

PARAMETERS

............................................................................78

F.2 E

XPLICIT TAGGING OF PARAMETERIZED TYPES

................................................................................78

G. INTELLECTUAL PROPERTY CONSIDERATIONS..................................................................78

H. REVISION HISTORY......................................................................................................................78

I. REFERENCES ..................................................................................................................................78

J. ABOUT PKCS ...................................................................................................................................81

Introduction

1.1

Background

Cryptographic tokens, such as Integrated Circuit Cards (or IC cards) are intrinsically

secure computing platforms ideally suited to providing enhanced security and privacy

functionality to applications. They can handle authentication information such as digital

certificates and capabilities, authorizations and cryptographic keys. Furthermore, they are

capable of providing secure storage and computational facilities for sensitive information

such as:

− private keys and key fragments;

− account numbers and stored value;

− passwords and shared secrets; and

− authorizations and permissions.

At the same time, many of these tokens provides an isolated processing facility capable of

using this information without exposing it within the host environment where it is at

potential risk from hostile code (viruses, Trojan horses, and so on). This becomes

critically important for certain operations such as:

− generation of digital signatures, using private keys, for personal identification;

− network authentication based on shared secrets;

− maintenance of electronic representations of value; and

PKCS #15

1.1: C

RYPTOGRAPHIC

OKEN

NFORMATION

YNTAX

TANDARD

− portable permissions for use in off-line situations.

Unfortunately, the use of these tokens for authentication and authorization purposes has

been hampered by the lack of interoperability at several levels. First, the industry lacks

standards for storing a common format of digital credentials (keys, certificates, etc.) on

them. This has made it difficult to create applications that can work with credentials from

a variety of technology providers. Attempts to solve this problem in the application

domain invariably increase costs for both development and maintenance. They also create

a significant problem for the end-user since credentials are tied to a particular application

running against a particular application-programming interface to a particular hardware

configuration.

Second, mechanisms to allow multiple applications to effectively share digital credentials

have not yet reached maturity. While this problem is not unique to cryptographic cards - it

is already apparent in the use of certificates with World Wide Web browsers, for example

- the limited room on many cards together with the consumer expectation of universal

acceptance will force credential sharing on credential providers. Without agreed-upon

standards for credential sharing, acceptance and use of them both by application

developers and by consumers will be limited.

To optimize the benefit to both the industry and end-users, it is important that solutions to

these issues be developed in a manner that supports a variety of operating environments,

application programming interfaces, and a broad base of applications. Only through this

approach can the needs of constituencies be supported and the development of

credentials-activated applications encouraged, as a cost-effective solution to meeting

requirements in a very diverse set of markets.

The objectives of this document are therefore to:

− enable interoperability among components running on various platforms (platform

neutral);

− enable applications to take advantage of products and components from multiple

manufacturers (vendor neutral);

− enable the use of advances in technology without rewriting application-level

software (application neutral); and

− maintain consistency with existing, related standards while expanding upon them

only where necessary and practical.

As a practical example, the holder of an IC card containing a digital certificate should be

able to present the card to any application running on any host and successfully use the

card to present the contained certificate to the application.

As a first step to achieve these objectives, this document specifies a file and directory

format for storing security-related information on cryptographic tokens. It has the

following characteristics:

− dynamic structure enables implementations on a wide variety of media, including

stored value cards;

PKCS #15

1.1: C

RYPTOGRAPHIC

OKEN

NFORMATION

YNTAX

TANDARD

− allows multiple applications to reside on the card (even multiple EID applications);

− supports storage of any type of objects (keys, certificates and data); and

− support for multiple PINs whenever the token supports it

In general, an attempt has been made to be flexible enough to allow for many different

token types, while still preserving the requirements for interoperability. A key factor for

this in the case of IC cards is the notion of “Directory Files” (See Section 5.5) which

provides a layer of indirection between objects on the card and the actual format of these

objects.

This document supersedes PKCS #15 v1.0 [31], but is backward compatible.

1.2 Information access model

The PKCS #15 token information may be read when a token is presented containing this

information, and is used by a PKCS #15 interpreter which is part of the software

environment, e.g. as shown in the figure below.

Figure 1 – Embedding of a PKCS #15 interpreter (example)

Terms and definitions

For the purposes of this document, the following definitions apply:

application the data structure, data elements and program

modules needed for a specific functionality to be

satisfied ([17])

ard Terminal-

nterface

ard

ndependent

pplication

river

KCS#15

nterpreter

Application

KCS#11-

nterface

PKCS #15

1.1: C

RYPTOGRAPHIC

OKEN

NFORMATION

YNTAX

TANDARD

application identifier data element that identifies an application in a

card

NOTE – Adapted from [14]

application protocol data unit message between the card and the interface

device, e.g. host computer

NOTE – Adapted from [13]

application provider entity that provides an application

NOTE – Adapted from [14]

authentication object directory file optional elementary file contaning information

about authentication objects known to the PKCS

#15 application

binary coded decimal Number representation where a number is

expressed as a sequence of decimal digits and then

each decimal digit is encoded as a four bit binary

number

Example – Decimal 92 would be encoded as the

eight bit sequence 1001 0010.

cardholder person for whom the card was issued

card issuer organization or entity that issues smart cards and

card applications

certificate directory file optional elementary file containing information

about certificate known to the PKCS #15

application

command message that initiates an action and solicits a

response from the card

data object directory file optional elementary file containing information

about data objects known to the PKCS #15

application

dedicated file file containing file control information, and,

optionally, memory available for allocation, and

which may be the parent of elementary files

and/or other dedicated files

NOTE – Adapted from [13]

directory (DIR) file optional elementary file containing a list of

applications supported by the card and optional

related data elements

NOTE – Adapted from [14]

elementary file set of data units or records that share the same

评论收藏

内容反馈

版权申诉

周楷雯

粉丝: 116

PKCS.rar_pkcs_pkcs-10_pkcs-1v2-1.pdf_安全协议_完整

最新资源

PKCS.rar_pkcs_pkcs-10_pkcs-1v2-1.pdf_安全协议_完整

pkcs文档,

pkcs标准文档分享

PKCS 中文简介 pdf

PKCS全套1到15规范打包下载

PKCS #1 规范 中文版

pkcs_11v2.11-CH.pdf.zip_PKCS11 PDF_pkcs-11v2-20.pdf_pkcs11_pkcs_

PKCS.rar_PKCS1_PKCS＃11_pkcs_pkcs#

pkcs-11v2-20d3.rar_PKCS#1_PKCS#11 USBKey_RSA PKCS_pkcs_usbkey

PKCS11导入证书.rar_pkcs11_PKCS11示例_源码

pkcs11-helper-1.06.rar_PKCS＃11_pkcs_pkcs11_pkcs11-helper_pkcs11-

PKCS (公钥密码标准)

按PKCS#10数据格式封装PKCS#10数据

RSA公司的PKCS系列标准

pkcs-1v2-1 RSA Cryptography Standard 中文版

pkcs10 规范

pkcs7_trust.rar_The Chain_pkcs7_pkcs7#_trust

pkcs7.rar_pkcs7_return

pkcs7_key_type.rar_pkcs7_trusted

pkcs11-helper-1.11-3.el7.x86_64.rpm

pkcs7.rar_openssl 签名_openssl pkcs7_openssl数字签名_openssl签名_pkcs7签

智能卡安全规范 PKCS标准

安全协议导论课件

p12_npas.rar_Change_pkcs

补位函数RSA_padding_add_PKCS1_type_1等

rsa.rar_RSA算法_open ssl rsa_rsa ssl_rsa_sign c_rsades

bind-devel-9.11.4-26.P2.el7_9.4.x86_64.rpm

[centos8 & centos_stream]openssh8.5p1.tar

PKCS__1_v2.1_RSA_算法标准+RSA-oaep_spec

PKCS11papers.rar_pkcs11

ElAES.zip_AES CBC pkcs7_EISE单元加密_aes pkcs7_aes Pkcs7 cbc_aes加密

王者荣耀-数模校赛一等奖论文分享(文末链接免费分享)

a是一个list，里边每个元素都是set，如何判断a中是否有set是有元素的

最新资源

PKCS #1 规范中文版