CN112165385B - Universal digital signature method for Web application system - Google Patents
Universal digital signature method for Web application system Download PDFInfo
- Publication number
- CN112165385B CN112165385B CN202010840826.4A CN202010840826A CN112165385B CN 112165385 B CN112165385 B CN 112165385B CN 202010840826 A CN202010840826 A CN 202010840826A CN 112165385 B CN112165385 B CN 112165385B
- Authority
- CN
- China
- Prior art keywords
- signature
- user
- key
- digital signature
- private key
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
- H04L9/3249—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures using RSA or related signature schemes, e.g. Rabin scheme
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Storage Device Security (AREA)
Abstract
The invention discloses a universal digital signature method for a Web application system, which comprises the following steps: 1.1, a user applies for a key through a digital signature system; 1.2, the background of the digital signature system distributes a key pair to a user, encrypts a private key into a private key ciphertext and generates a key signature; 1.3 the user signs the page signature in the application system; 1.4, the background of the digital signature system takes out a private key ciphertext from the digital signature database, decrypts the private key to obtain a private key of a user, and then signs the data needing to be signed by the private key; 1.5 displaying the signature needing to be verified on a digitally signed signature page of the application system; 1.6 the background of the digital signature system takes out the public key of the user from the digital signature database, verifies the signature result and feeds back the signature verification result to the signature page of the application system; 1.7 the signature page of the application system displays the signature checking result. The invention is suitable for various operating systems and browsers, has good compatibility, is favorable for popularization and application, and can be widely applied to Web application systems.
Description
Technical Field
The invention relates to a digital signature method, in particular to a universal digital signature method for a Web application system.
Background
The improvement of management level through informatization is a common consensus of various industries. The information system is mostly a Web application system with a B/S framework, and the basic framework of the information system is a front-end page, a background application and a database system. A user accesses a front-end page through a browser and submits data or a query request to a background application; the background application calculates data or query requests submitted by users, stores the data or calculation results into the database system, or inquires the data from the database system, calculates, and feeds back the data or calculation results to the users through front-end pages.
However, many enterprises and institutions are required to receive superior or competent audit internally. In the case of paper office, the handwritten signature on the examination and approval sheet is the basis for confirming that the examination and approval sheet is submitted by an operator/auditor for auditing/approving by an approver. In a Web application system, through role, authority and workflow control, a user can only carry out authorized operation and access authorized data. However, this only guarantees at best that the user's operations of the Web application are role, authority and workflow controlled, and does not prove that the data in the database has not been tampered with by other means.
A digital signature system is required to ensure that data is not modified in the database. At present, publicly available digital signature systems suitable for Web application systems are basically implemented based on browser controls. This method has higher security, but also has the compatibility problem of the operating system and the browser, which is not favorable for the popularization of the digital signature system.
Disclosure of Invention
The present invention is to overcome the above-mentioned shortcomings of the background art, and provides a universal digital signature method for Web application system, especially a digital signature method for Web application system independent of the operating system and browser. The digital signature method of the invention is universal for various operating systems and browsers, has no compatibility problem, and is beneficial to popularization and application of the digital signature system.
The invention provides a universal digital signature method for a Web application system, which comprises the following steps: 1.1, a user signs and manages a front-end page application key pair through a digital signature system, and submits a private key password, key pair validity time and invalidation time at the same time; 1.2, the background of the digital signature system distributes a key pair for a user, encrypts a private key into a private key ciphertext by using a private key password submitted by the user, generates a key signature, and then stores data into a digital signature database; 1.3 when the user signs the page signature in the application system, submitting the page identification, the data identification, the signature domain, the data and the private key password to be signed to a background of the digital signature system; 1.4, the background of the digital signature system takes out a current valid private key ciphertext of a user from a digital signature database, decrypts the ciphertext by using a private key password submitted by the user to obtain a private key of the user, signs data to be signed by using the private key, and stores a page identifier, a data identifier, a signature domain, a signature user identifier, signature time and a signature result into the digital signature database; 1.5 when the application system signature page which is digitally signed displays that a signature needs to be verified, submitting page identification, data identification, a signature domain, a signature user identification and data which needs to be signed to a background of a digital signature system; 1.6 the background of the digital signature system takes out the page identification, the data identification, the signature domain, the signature result corresponding to the signature user and the signature time from the digital signature database, further takes out the corresponding user public key, verifies the signature result by using the public key of the user and feeds back the signature verification result to the signature page of the application system; and 1.7, displaying the signature verification result fed back by the background of the digital signature system by the signature page of the application system.
In the above technical solution, the specific steps of step 1.2 include: 1.2.1 determining the validation time t of the key pair newly applied by the user b Time to failure t e . If the key pair of the user does not exist in the digital signature database, the validation time t submitted by the user b0 And time to failure t e0 Then t is b =t b0 ，t e =t e0 (ii) a Otherwise, the latest key pair failure time t of the user in the digital signature database is taken out e1 ，t b =t e1 ，t e =t e1 +t e0 -t b0 (ii) a 1.2.2 selecting a key algorithm and a key length as required to generate a key pair; 1.2.3, selecting an encryption algorithm according to needs, and encrypting a private key by using a private key password submitted by a user to obtain a private key ciphertext; 1.2.4 generating a key signature for the user identification, the public key, the effective time and the invalid time; 1.2.5, the private key cryptograph, the public key and the key signature are stored in a digital signature database together with the user identification, the validation time and the expiration time.
In the above technical solution, in the step 1.3, before the user signs the signature on the application system signature page, 1.3.1 the user submits the signature display picture on the front end page through the signature management of the digital signature system, and submits the pair validity time and the expiration time at the same time; 1.3.2 the background of the digital signature system generates a signature effective picture and a signature ineffective picture according to the signature display picture, and stores the signature effective picture and the signature ineffective picture in a digital signature database together with the user identification, the validation time and the invalidation time.
In the above technical solution, in step 1.5, when the signature page of the application system that is digitally signed needs to verify the signature, a signature picture is displayed, and a request for verifying the signature is made to the background of the digital signature system.
In the above technical solution, in step 1.6, after the digital signature system verifies the signature in the background, a signature valid picture or a signature invalid picture is returned to the application system signature page according to the verification result.
In the above technical solution, in step 1.7, the image returned by the background verification signature of the digital signature system is updated to the signature image by the signature page of the application system subjected to digital signature.
In the above technical solution, in the step 1.2, the digital signature database has three data tables: and the user key table keyPairs, the signature table sigPict and the signature record table sigLog are used for storing the private key ciphertext, the public key and the key signature, as well as the user identification, the validation time and the expiration time in the user key table keyPairs.
In the above technical solution, the specific steps of step 1.4 are as follows: 1.4.1, inquiring a user key table keyPairs of a digital signature database to obtain a current effective private key ciphertext character string secPri and a public key keyPub; 1.4.2, decrypting by using a private key password strKey to obtain a private key character string keyPri of the user; 1.4.3 signing the data strData to be signed to generate a signature character string dataSig; 1.4.4, storing the page identification, the data identification, the signature domain, the signature user identification, the signature time and the signature result dataSig into a signature record table sigLog in a digital signature database.
In the above technical solution, the specific steps of step 1.6 are as follows: 1.6.1 inquiring a signature record table sigLog of a digital signature database, and taking out a page identifier, a data identifier, a signature domain, a signature result dataSig corresponding to a signature user and a signature time sigTime; 1.6.2 inquiring a user key table keyPairs in a digital signature database, and finding out a public key character string keyPub with effective user identification at signature time sigTime; 1.6.3 using the public key of the user to verify whether the data strData needing to verify the signature is consistent with the signature result dataSig; 1.6.4 feeds back the result of the checkmark to the application system signature page.
In the above technical solution, in step 1.2.2, in JDK1.8, a key pair is generated for the objects rsaPub, rsaPri, and a key pair character string keyPub, keyPri based on RSA key algorithm and 1024-bit length; in the step 1.2.3, in JDK1.8, based on the 3DES encryption algorithm, a string strKey is set as a private key password, and a private key keyPri is encrypted to obtain a private key ciphertext string secPri; in the step 1.2.4, in JDK1.8, based on the RSA key algorithm and the 1024-bit length, a key signature string keySig is generated for the user identification string userId, the public key keyPub, the effective time string begTime, and the expiration time string invTime; in the step 1.3.2, in JDK1.8, based on java.at.image.buffer image class library, signature valid picture valid.png is generated into signature invalid picture invalid.png, and then the related data is stored in the sigPict table in the digital signature database.
The universal digital signature method for the Web application system has the following beneficial effects: the digital signature method of the invention is universal for various operating systems and browsers, has no compatibility problem, and is beneficial to popularization and application of the digital signature system.
Drawings
FIG. 1 is a diagram of the system architecture upon which the generic digital signature method for Web application systems of the present invention relies;
FIG. 2 is a flow chart of a generic digital signature method for a Web application system according to the present invention;
FIG. 3 is a flowchart of the steps of step 1.2 of the universal digital signature method for Web application system according to the present invention;
fig. 4 is a flowchart of a signature verification result display method in the universal digital signature method for the Web application system according to the present invention.
Detailed Description
The invention is described in further detail below with reference to the following figures and examples, which should not be construed as limiting the invention.
Referring to fig. 1, the universal digital signature method for Web application system of the present invention relies on a digital signature system composed of a signature management front end S01, a digital signature system background S02 and a digital signature database S03, and an application system composed of an application system signature page S04, an application system background S05 and an application system database S06. Wherein the application system signature page S04 is based on digital signature system background S02.
Referring to fig. 2, the universal digital signature method for the Web application system of the present invention includes the following steps:
1.1, a user signs and manages a front-end page application key pair through a digital signature system, and submits a private key password, key pair validity time and expiration time simultaneously;
the step is that the private key password, the key pair validity time and the failure time information are input at the front-end page of the key application of the user, and the step can be realized on the page;
1.2, the background of the digital signature system distributes a key pair for a user, encrypts a private key into a private key ciphertext by using a private key password submitted by the user, generates a key signature, and then stores data into a digital signature database; referring to fig. 3, the specific steps of step 1.2 include:
1.2.1 determining the validation time t of the key pair newly applied by the user b Time to failure t e . If the key pair of the user does not exist in the digital signature database, the validation time t submitted by the user b0 And time to failure t e0 Then t is b =t b0 ，t e =t e0 (ii) a Otherwise, the latest key pair failure time t of the user in the digital signature database is taken out e1 ，t b =t e1 ，t e =t e1 +t e0 -t b0 ；
1.2.2 selecting a key algorithm and a key length as required to generate a key pair, in this embodiment, in a digital signature database JDK1.8, based on an RSA key algorithm and a 1024-bit length, generating a key pair object rsaPub, rsaPri, and a key pair string keyPub, keyPri;
1.2.3 select the encryption algorithm as required, encrypt the private key with the private key password submitted by the user to obtain the private key ciphertext, in this embodiment, in JDK1.8, on the basis of the 3DES encryption algorithm, set the string strKey as the private key password, encrypt the private key keyPri to obtain the private key ciphertext string secPri;
1.2.4 generates a key signature for the user identifier, the public key, the validation time and the expiration time, and in this embodiment, in JDK1.8, based on the RSA key algorithm and the 1024-bit length, generates a key signature string keySig for the user identifier string userId, the public key keyPub, the validation time string begTime and the expiration time string invTime;
1.2.5, the private key ciphertext, the public key and the key signature are stored into a digital signature database together with the user identification, the validation time and the expiration time;
in this embodiment, there are three data tables in the digital signature database: the method comprises the steps that a user key table keyPairs, a signature table sigPict and a signature record table sigLog are used, and a private key ciphertext, a public key and a key signature are stored in the user key table keyPairs together with user identification, effective time and failure time;
1.3 user signature step in application system signature page:
1.3.1, a user submits a signature display picture through a digital signature system signature management front-end page, and submits pair validity time and invalidation time at the same time;
1.3.2 the background of the digital signature system generates a signature valid picture and a signature invalid picture according to a signature display picture, and stores the generated signature valid picture and the generated signature invalid picture together with a user identifier, an effective time and an invalid time into a digital signature database, wherein in the embodiment, in JDK1.8, a signature invalid picture invalidity.png is generated by a signature valid picture valid.png on the basis of a java.avt.image.buffer image class library, and then related data is stored into a sigPict table in the digital signature database;
1.3.3 when the user signs the page signature in the application system, submitting the page identification, the data identification, the signature domain, the data and the private key password to be signed to a background of the digital signature system;
1.4, the background of the digital signature system takes out a current valid private key ciphertext of a user from a digital signature database, decrypts the current valid private key ciphertext by using a private key password submitted by the user to obtain a private key of the user, signs data needing to be signed by using the private key, and stores a page identifier, a data identifier, a signature domain, a signature user identifier, signature time and a signature result into the digital signature database;
the specific steps of step 1.4 are as follows:
1.4.1, inquiring a user key table keyPairs of a digital signature database to obtain a current effective private key ciphertext character string secPri and a public key keyPub;
1.4.2, decrypting by using a private key password strKey to obtain a private key character string keyPri of the user;
1.4.3 signing the data strData needing to be signed to generate a signature character string dataSig;
1.4.4, storing the page identifier, the data identifier, the signature domain, the signature user identifier, the signature time and the signature result dataSig into a signature record table sigLog in a digital signature database;
1.5 when the application system signature page which is subjected to digital signature displays that the signature needs to be verified, displaying a signature picture, requesting the background of the digital signature system for verifying the signature, and then submitting the page identification, the data identification, the signature domain, the signature user and the data which needs to verify the signature to the background of the digital signature system;
1.6 the background of the digital signature system takes out the page identification, the data identification, the signature domain, the signature result corresponding to the signature user and the signature time from the digital signature database, further takes out the corresponding public key of the user, verifies the signature result by using the public key of the user, and feeds back the signature verification result to the signature page of the application system;
the specific steps of step 1.6 are as follows:
1.6.1 inquiring a signature record table sigLog of a digital signature database, and taking out a page identifier, a data identifier, a signature domain, a signature result dataSig corresponding to a signature user and a signature time sigTime;
1.6.2 inquiring a user key table keyPairs in a digital signature database, and finding out a public key character string keyPub with effective user identification at signature time sigTime;
1.6.3 using the public key of the user to verify whether the data strData needing to verify the signature is consistent with the signature result dataSig; using JDK1.8, RSA key algorithm as follows:
1.6.4, feeding back a result of the signature verification to the signature page of the application system;
1.7 the signature page of the application system displays the signature verification result fed back by the background of the digital signature system, in this embodiment, the signature page of the application system which is digitally signed updates the picture returned by the background verification signature of the digital signature system to the signature picture.
Referring to fig. 4, the method for displaying the signature verification result of the universal digital signature method of the Web application system of the present invention includes the following steps:
2.1, submitting a signature display picture through a digital signature system signature management front-end page by a user, and simultaneously submitting effective time and failure time;
2.2, the background of the digital signature system generates a signature effective picture and a signature ineffective picture according to the signature display picture, and stores the signature effective picture and the signature ineffective picture together with the user identification, the validation time and the invalidation time into a digital signature database;
taking JKD1.8 and using java, awt, image, buffer image class library as an example, generating a signature valid picture invalid picture invalid.png from a signature valid picture valid.png:
and then storing the related data into a sigPict table in a digital signature database, wherein the specific method can be realized in various Web application background development environments.
2.3 when the signature page of the application system which is subjected to the digital signature needs to verify the signature, displaying a signature picture and requesting a background of the digital signature system to verify the signature;
2.4 after the background of the digital signature system verifies the signature, a signature effective picture or a signature ineffective picture is returned to the signature page of the application system according to the verification result;
returning valid. png when result is true in the step 2.2 example; when result is false, invalid. png is returned. The specific method can be easily realized in various Web application background development environments.
And 2.5, updating the picture returned by the background verification signature of the digital signature system to the signature picture through the signature page of the digital signature application system.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Those not described in detail in this specification are within the skill of the art.
Claims (10)
1. A universal digital signature method for Web application system is characterized in that: the method comprises the following steps:
1.1, a user signs and manages a front-end page application key pair through a digital signature system, and submits a private key password, key pair validity time and expiration time simultaneously;
1.2, a background of the digital signature system distributes a key pair for a user, encrypts a private key into a private key ciphertext by using a private key password submitted by the user, generates a key signature for user identification, a public key, effective time and failure time, and then stores data into a digital signature database, wherein the data are the private key ciphertext, the public key and the key signature;
1.3 when the user signs the page signature in the application system, submitting the page identification needing signature, the data identification corresponding to the data, the signature domain, the data and the private key password to a background of the digital signature system;
1.4, the background of the digital signature system takes out a current valid private key ciphertext of a user from a digital signature database, decrypts the ciphertext by using a private key password submitted by the user to obtain a private key of the user, signs data to be signed by using the private key, and stores a page identifier, a data identifier, a signature domain, a signature user identifier, signature time and a signature result into the digital signature database;
1.5 when the application system signature page which is digitally signed displays that a signature needs to be verified, submitting page identification, data identification, a signature domain, a signature user identification and data which needs to be signed to a background of a digital signature system;
1.6 the background of the digital signature system takes out the page identification, the data identification, the signature domain, the signature result corresponding to the signature user and the signature time from the digital signature database, further takes out the corresponding user public key, verifies the signature result by using the public key of the user and feeds back the signature verification result to the signature page of the application system;
and 1.7, displaying the signature verification result fed back by the background of the digital signature system by the signature page of the application system.
2. The universal digital signature method for Web application system as claimed in claim 1, wherein: the specific steps of step 1.2 include:
1.2.1 determining the validation time t of the key pair newly applied by the user b Time to failure t e If the key pair of the user does not exist in the digital signature database, the validation time t submitted by the user b0 And time to failure t e0 Then t is b =t b0 ，t e =t e0 (ii) a Otherwise, the latest key pair failure time t of the user in the digital signature database is taken out e1 ，t b =t e1 ，t e =t e1 +t e0 -t b0 ；
1.2.2 selecting a key algorithm and a key length as required to generate a key pair;
1.2.3, selecting an encryption algorithm as required, and encrypting a private key by using a private key password submitted by a user to obtain a private key ciphertext;
1.2.4 generating a key signature for the user identification, the public key, the effective time and the invalid time;
1.2.5, the private key ciphertext, the public key and the key signature are stored in a digital signature database together with the user identification, the validation time and the expiration time.
3. The universal digital signature method for Web application system as claimed in claim 2, wherein: in step 1.3, before the user signs the page signature on the application system,
1.3.1 the user submits a signature display picture, and simultaneously submits a pair effect time and a failure time through a digital signature system signature management front-end page;
1.3.2 the background of the digital signature system generates a signature valid picture and a signature invalid picture according to the signature display picture, and stores the signature valid picture and the signature invalid picture together with the user identification, the validation time and the invalidation time into a digital signature database.
4. The universal digital signature method for Web application system as claimed in claim 3, wherein: in step 1.5, when the signature page of the application system subjected to the digital signature needs to verify the signature, a signature picture is displayed, and a request for verifying the signature is sent to a background of the digital signature system.
5. The universal digital signature method for Web application system as recited in claim 4, wherein: in the step 1.6, after the background of the digital signature system verifies the signature, a signature valid picture or a signature invalid picture is returned to the signature page of the application system according to the verification result.
6. The universal digital signature method for Web application systems as recited in claim 5, wherein: in the step 1.7, the image returned by the background verification signature of the digital signature system is updated to the signature image through the signature page of the digitally signed application system.
7. The universal digital signature method for Web application systems as recited in claim 6, wherein: in step 1.2, there are three data tables in the digital signature database: and the user key table keyPairs, the signature table sigPict and the signature record table sigLog are used for storing the private key ciphertext, the public key and the key signature, as well as the user identification, the validation time and the expiration time in the user key table keyPairs.
8. The universal digital signature method for Web application systems as recited in claim 7, wherein: the specific steps of step 1.4 are as follows:
1.4.1, querying a user key table keyPairs of a digital signature database to obtain a current effective private key ciphertext character string secPri and a public key keyPub;
1.4.2, decrypting by using a private key password strKey to obtain a private key character string keyPri of the user;
1.4.3 signing the data strData to be signed to generate a signature character string dataSig;
1.4.4, storing the page identification, the data identification, the signature domain, the signature user identification, the signature time and the signature result dataSig into a signature record table sigLog in a digital signature database.
9. The universal digital signature method for Web application system as recited in claim 8, wherein: the specific steps of step 1.6 are as follows:
1.6.1 inquiring a signature record table sigLog of a digital signature database, and taking out a page identifier, a data identifier, a signature domain, a signature result dataSig corresponding to a signature user and a signature time sigTime;
1.6.2 inquiring a user key table keyPairs in a digital signature database, and finding out a public key character string keyPub with effective user identification at signature time sigTime;
1.6.3 using the public key of the user to verify whether the data strData needing to verify the signature is consistent with the signature result dataSig;
1.6.4 feeds back the result to the application system signature page.
10. The universal digital signature method for Web application systems as recited in claim 9, wherein: in the step 1.2.2, in a library JDK1.8, a key pair object rsaPub and rsaPri and a key pair character string keyPub and keyPri are generated based on an RSA key algorithm and a 1024-bit length;
in the step 1.2.3, in JDK1.8, based on the 3DES encryption algorithm, a string strKey is set as a private key password, and a private key keyPri is encrypted to obtain a private key ciphertext string secPri;
in the step 1.2.4, in JDK1.8, based on the RSA key algorithm and the 1024-bit length, a key signature string keySig is generated for the user identification string userId, the public key keyPub, the effective time string begTime, and the expiration time string invTime;
in the step 1.3.2, in JDK1.8, based on java.aawt.image.buffer image class library, a signature valid picture valid.png is generated into a signature invalid picture invalid.png, and then related data is stored in a sigPict table in a digital signature database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010840826.4A CN112165385B (en) | 2020-08-20 | 2020-08-20 | Universal digital signature method for Web application system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010840826.4A CN112165385B (en) | 2020-08-20 | 2020-08-20 | Universal digital signature method for Web application system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112165385A CN112165385A (en) | 2021-01-01 |
| CN112165385B true CN112165385B (en) | 2022-09-09 |
Family
ID=73859676
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010840826.4A Active CN112165385B (en) | 2020-08-20 | 2020-08-20 | Universal digital signature method for Web application system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112165385B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102413064A (en) * | 2010-09-25 | 2012-04-11 | 上海中标软件有限公司 | Browser control-based webmail signing encrypting method |
| CN102651747A (en) * | 2012-05-24 | 2012-08-29 | 电子科技大学 | Forward secure digital signature method on basis of unbelievable updating environment |
| CN103124215A (en) * | 2013-01-25 | 2013-05-29 | 匡创公司 | Self-certifying method with time marks |
| CN103490892A (en) * | 2013-08-28 | 2014-01-01 | 广东数字证书认证中心有限公司 | Digital signing method and system, application server and cloud cipher server |
| CN108038388A (en) * | 2018-01-18 | 2018-05-15 | 北京书生电子技术有限公司 | The implementation method and client of Web page seal, server |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2491628A1 (en) * | 2002-07-03 | 2004-01-15 | Aurora Wireless Technologies, Ltd. | Biometric private key infrastructure |
-
2020
- 2020-08-20 CN CN202010840826.4A patent/CN112165385B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102413064A (en) * | 2010-09-25 | 2012-04-11 | 上海中标软件有限公司 | Browser control-based webmail signing encrypting method |
| CN102651747A (en) * | 2012-05-24 | 2012-08-29 | 电子科技大学 | Forward secure digital signature method on basis of unbelievable updating environment |
| CN103124215A (en) * | 2013-01-25 | 2013-05-29 | 匡创公司 | Self-certifying method with time marks |
| CN103490892A (en) * | 2013-08-28 | 2014-01-01 | 广东数字证书认证中心有限公司 | Digital signing method and system, application server and cloud cipher server |
| CN108038388A (en) * | 2018-01-18 | 2018-05-15 | 北京书生电子技术有限公司 | The implementation method and client of Web page seal, server |
Non-Patent Citations (2)
| Title |
|---|
| 安全电子邮件系统的设计与分析;陈勇;《舰船电子工程》;20060820(第04期);全文 * |
| 数字签名技术在电子商务系统中的应用;祝洪杰等;《山东轻工业学院学报(自然科学版)》;20071215(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112165385A (en) | 2021-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11526631B2 (en) | Distributed blockchain-based method for maintaining the validity of a file | |
| TWI700916B (en) | Method and device for providing and obtaining safety identity information | |
| US5872848A (en) | Method and apparatus for witnessed authentication of electronic documents | |
| US9985936B2 (en) | Method and system for the supply of data, transactions and electronic voting | |
| US6539093B1 (en) | Key ring organizer for an electronic business using public key infrastructure | |
| US20240143843A1 (en) | Method and Device for Implementing Identity Endorsement On Blockchain | |
| US6959382B1 (en) | Digital signature service | |
| US7028180B1 (en) | System and method for usage of a role certificate in encryption and as a seal, digital stamp, and signature | |
| EP0869637A2 (en) | Digital certification system | |
| US20090271321A1 (en) | Method and system for verification of personal information | |
| WO2018114587A1 (en) | Distributed blockchain-based method for maintaining the validity of a file | |
| KR102099861B1 (en) | System and method for verifying documents using blockchain | |
| JP2001320356A (en) | Data communication system using public key system cypher, and data communication system constructing method | |
| JP2004023796A (en) | Selectively disclosable digital certificate | |
| JP2000122973A (en) | Qualification managing method and device | |
| US6839842B1 (en) | Method and apparatus for authenticating information | |
| JP2005333596A (en) | Electronic application system, and electronic application apparatus | |
| CN112165385B (en) | Universal digital signature method for Web application system | |
| KR20240059302A (en) | Method and apparatus for encryption/decryption communication of service based on decentralized identifier | |
| US20210067351A1 (en) | Communication apparatus and communication method | |
| KR20010038208A (en) | Administrative information management method of X.509-base public key certification authority | |
| JP2002229451A (en) | System, method, and program for guaranteeing date and hour of creation of data | |
| EP1205888A2 (en) | Certificate issuing method, system and computer readable storage medium | |
| KR102569582B1 (en) | Method for Selective Disclosure of Attribute Information and Zero-Knowledge Proof Using Attribute-Based Encryption | |
| KR20160020850A (en) | Method and server for issuing certificate and mandating digital signature |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |