Current location - Quotes Website - Signature design - 14 Jumping Boot: pdf Electronic Signature
14 Jumping Boot: pdf Electronic Signature
In the last issue, we talked about the operation of pdf documents. This issue talks about the electronic signature of a small business of the company, which mainly realizes 1) online registration of student information, 2) online payment, 3) electronic signature, and 4) generating a pdf receipt with the company's electronic signature.

I will talk about online payment and electronic signature in subsequent chapters, and pdf electronic signature in this issue.

I. Application for Electronic Seal

Second, generate PKCS 12 certificate.

1 introduction. PKCS

PKCS: Public-key cryptography standards (PKCS for short) is a set of public-key cryptography standards formulated by RSA Data Security Company and its partners in the United States, including a series of related protocols such as certificate application, certificate update, certificate revocation form release, certificate content expansion, digital signature, digital envelope format, etc.

By the end of 1999, PKCS has issued the following standards:

PKCS# 1: Defines the encryption and signature mechanism of RSA public key algorithm, which is mainly used to organize digital signatures and digital envelopes described in PKCS#7 [22].

PKCS#3: Define Diffie-Hellman key exchange protocol [23].

PKCS#5: Describes a method of encrypting a string using a security key derived from a password. Use MD2 or MD5 to derive the key from the password, and use DES-CBC mode for encryption. It is mainly used to encrypt private keys transmitted from one computer to another, and cannot be used to encrypt messages [24].

PKCS#6: Standard syntax for describing public key certificates, mainly describing the extended format of X.509 certificates [25].

PKCS#7: Define general message syntax, including encryption mechanisms, such as digital signature and encryption. PKCS#7 is compatible with PEM, so encrypted messages can be converted into PEM messages without other encryption operations [26].

PKCS#8: Describes the format of private key information, including the private key of public key algorithm and optional attribute set [27].

PKCS#9: Define some attribute types for PKCS#6 certificate extension, PKCS#7 digital signature and PKCS#8 private key encryption information [28].

PKCS# 10: Describes the certificate request syntax [29].

PKCS# 1 1: It is called Cyptoki and defines a set of technology-independent programming interfaces for encryption devices such as smart cards and PCMCIA cards.

PKCS# 12: Grammatical standard to describe personal information exchange. Describe the syntax of encapsulating the user's public key, private key, certificate and other related information [3 1].

PKCS# 13: elliptic curve cryptosystem standard [32].

PKCS# 14: Pseudo-random number generation standard.

PKCS# 15: Information format standard of password token [33].

PKCS 12, the above standard PKCS# 12, is mainly used to describe personal identity information.

2.JAVA generates PKCS 12 certificate and stores it.

The generated files keystore.cer and keystore.p 12 are placed in the configuration file of your own project for later call.

Third, electronic signature.

2. Signature tool class SignPdf

3. That is called business.