US20020046337A1 - Tree-based certificate revocation system - Google Patents
Tree-based certificate revocation system Download PDFInfo
- Publication number
- US20020046337A1 US20020046337A1 US09/947,478 US94747801A US2002046337A1 US 20020046337 A1 US20020046337 A1 US 20020046337A1 US 94747801 A US94747801 A US 94747801A US 2002046337 A1 US2002046337 A1 US 2002046337A1
- Authority
- US
- United States
- Prior art keywords
- certificate
- tree
- crl
- directory
- revoked
- 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.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- 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/3236—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 using cryptographic hash functions
-
- 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/3263—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 certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
- H04L9/3268—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 certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/30—Compression, e.g. Merkle-Damgard construction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/60—Digital content management, e.g. content distribution
-
- 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/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
Abstract
A method and system for overcoming the problems associated with certificate revocation lists (CRL's), for example, in a public key infrastructure. The invention uses a tree-based scheme to replace the CRL.
Description
- This application is based on U.S. provisional patent application No. 60/006,143 filed on Nov. 2, 1995.
- The present invention relates generally to secure communications and more particularly to schemes for certificate management.
- In many settings, it is necessary to certify certain data, as well as to revoke already issued certificates. For instance, in a Public-Key Infrastructure, (PKI) it is necessary to certify users' public keys.
- In a digital signature scheme, each user U chooses a signing key SKu and a matching verification key, PKu. User U uses SKu to compute easily his digital signature of a message m, SIGu(m), while anyone knowing that PKu is U's public key can verify that SIGu(m) is U's signature of m. Finding SIGu(m) without knowing SKu is practically impossible. On the other hand, knowledge of PKu does not give any practical advantage in computing SKu. For this reason, it is in U's interest to keep SKu secret (so that only he can digitally sign for U) and to make PKu as public as possible (so that everyone dealing with U can verify U's digital signatures). At the same time, in a world with millions of users, it is essential in the smooth flow of business and communications to be certain that PKu really is the legitimate key of user U. To this end, users' public keys are “certified.” At the same time it is also necessary to revoke some of the already-issued certificates.
- CERTIFICATION AND REVOCATION OF PUBLIC KEYS. Typically, certificates for users' public keys are produced and revoked by certifying authorities called CA's. A complete public-key infrastructure may involve other authorities (e.g., PCAS) who may also provide similar services (e.g., they may certify the public keys of their CA's). The present inventions can be easily applied to such other authorities. A CA can be considered to be a trusted agent having an already certified (or universally known) public key. To certify that PKu is U's public key, a CA typically digitally signs PKu together with (e.g., concatenating it with) U's name, a certificate serial number, the current date (i.e., the certification or issue date), and an expiration date. (Before certifying U's public key, it is necessary to perform additional steps, such as properly identifying user U. The present invention, however, does not depend on these additional steps). The CA's signature of PKu is then inserted in a Directory and/or given to U himself.
- Upon receiving the (alleged) digital signature of user U of a message M, SIGu(M), a recipient R needs to obtain a certificate for PKu. (Indeed, SIGu(M) may be a correct digital signature of M with respect to some public key PKu, but R has no guarantee that PKu is indeed U's public key). Recipient R may obtain this certificate from the Directory, or from his own memory (if he has previously cached it), or from U himself. Having done this, R verifies (1) the correctness of the CA's certificate for PKu with respect to the CA's public key, and (2) the correctness of SIGu(M) with respect to PKu. (If the CA's public key is not universally known, or cached with R, then a certificate for this key too must be obtained.)
- Certificate retrieval is thus possible, although not necessarily cheap. Unfortunately, however, this is not the only retrieval that R needs to do. Indeed, it is crucially important that R makes sure that the certificate for PKu has not been revoked. This check, of course, may not be needed after the certificate's expiration date, but is needed during the certificate's alleged lifetime. A user's certificate can be revoked for a variety of reasons, including key compromise and the fact that the user is no longer associated with a particular CA.
- To enable a recipient to establish whether a given certificate has been revoked, it is known that each CA periodically issues and gives the Directory a Certificate Revocation List (CRL for short), in general containing an indication of all the (not yet expired) certificates originally issued by it. A CRL typically consists of the issuer's digital signature of (1) a header comprising the issuer's name (as well as the type of his signature algorithm), the current date, the date of the last update, and the date of the next update, together with (2) a complete list of revoked certificates (whose date has not yet expired), each with its serial number and revocation date. Since it is expected that a CA revokes many of her certificates, a CRL is expected to be quite long.
- After performing some checks on the CA's CRL (e.g., checking the CA's digital signature, checking that the CRL has arrived at the expected time, that a certificate declared revoked in the previous CRL of that CA—and not yet expired—still is revoked in the current CRL, etc.), the Directory stores it under its CA name.
- When a user queries the Directory about the revocation of a certificate issued by a given CA, the Directory responds by sending to the user the latest CRL of that CA. The user can then check the CRL signature, the CRL dates (so as to receive a reasonable assurance that he is dealing with the latest one), and whether or not the certificate of interest to him belongs to it.
- While CRLs are quite effective in helping users establishing which certificates are no longer deemed valid, they are also extremely expensive, because they tend to be very long and need to be transmitted very often.
- The National Institute of Standards and Technology has tasked the MITRE Corporation to study the organization and cost of a PKI for the Federal Government. This study estimates that CRLs constitute by far the largest entry in the Federal PKI's cost list. According to MITRE's estimates/assumptions, in the Federal PKI there are about three million users, each CA serves 30,000 users, 10% of the certificates are revoked (5% because of key compromise and 5% because of change in affiliation with the organization connected to a given CA). CRLs are sent out bi-weekly, and, finally, the recipient of a digital signature requests certificate information 20% of the time. (The remaining 80% of the time he will be dealing with public keys in his cache). The study envisages that each revoked certificate is specified in a CRL by means of about 9 bytes: 20 bits of serial number and 48 bits of revocation date. Thus, in the Federal PKI, each CRL is expected to comprise thousands of certificate serial numbers and their revocation dates; the header, however, has a fixed length, consisting of just 51 bytes.
- At 2 cents per kilobyte, the impact of CRL transmission on the estimated yearly costs of running the Federal PKI is stunning: if each federal employee verifies 100 digital signatures per day on average, then the total PKI yearly costs are $10,848 Millions, of which $10,237 Millions are due to CRL transmission. If each employee is assumed to verify just 5 digital signatures a day on average, then the total PKI yearly costs are $732 Millions, of which 563 Millions are due to CRL transmission.
- The MITRE study thus suggests that any effort should be made to find alternative and cheaper CRL designs. This is indeed the goal of the present invention.
- To avoid the dramatic CRL costs, a novel Certification Revocation System is described, where requesting users no longer receive the latest list of revoked certificates (of a given CA). The scheme utilizes a known tree-based authentication technique in a novel way to overcome the problems associated with the prior art.
- It is thus a primary object of this invention to provide certificate management without providing CRL's to a user requesting information about the certificate (e.g, its validity). Although special CRL's still may be used between CA's and the Directory in this scheme, the tree-based technique allows the Directory to convince users of whether or not a given certificate is still valid in a way that is essentially individualized, and thus quite convenient.
- A known scheme for authenticating an item in a list of items is described in U.S. Pat. No. 4,309,569 to Merkle, and the disclosure therein is hereby incorporated by reference. Familiarity with the Merkle scheme is assumed in the following discussion.
- By way of brief background, assume that the set S of certificates consists of n items, where, for convenience, n is a power to two: n=2k (else, we may introduce “dummy” items so that this is the case). The set organizer sorts (e.g., lexicographically) the items in S and then tree-hashes them as taught by Merkle. That is, let H be a one-way hash function, mapping strings of any length into B-bit strings (e.g., B=200). Then conceptually, the organizer stores the ith item, Ii, into the ith leaf of a full binary tree with n leaves. Then, he fills the remaining nodes of the tree in a bottom-up fashion, by storing in every internal node the hash of the concatenation of the content of its two children. In order to develop a minimum of terminology, let N be an internal node where the left child is L and the right child is R, and let VL be the value stored in L and VR the value stored in R (we shall refer to VL and VR as, respectively, a left-value and a right-value). Then, the organizer stores in node N the B-bit value H(VLVR).
- In one embodiment of the invention it is assumed that there are two (2) distinct trees (or more precisely, “tree-hashes”), a first tree in which information about issued but non-revoked certificates is stored, and a second tree in which information about revoked certificates is stored. Thus, for example, if the system has had 30,000 certificates issued but 3,000 of these have been revoked, the first tree would include information about the 27,000 certificates that remain valid while the second tree would store the information about the 3,000 revoked certificates. Thus, in this embodiment there is a tree-hash for the non-revoked certificates and a separate tree-hash for the revoked ones. In such case, the root values of these trees may be digitally signed by a CA (together with other information deemed proper) either separately or together; and the Directory uses the first tree to prove to a user that a given certificate is still deemed valid, and the second tree to prove that a certificate has been revoked. The CA builds both trees so that a given certificate (serial number) does not belong to both, but the Directory can also check for this property. Again, this and other operations may be facilitated if the serial number or any representation of the certificate that is deemed proper are ordered when inserted in the tree leaves. Among the various representations of a certificate, of course, one may use the certificate itself.
- While the above technique is advantageous, in the preferred embodiment each leaf of the tree-hash stores the serial number of an issued and not-yet-expired certificate, together with an additional bit indicating whether or not the corresponding certificate is no longer valid (i.e., it has been revoked), and, if so, the revocation date. Of course, additional information can be stored about each or some of the serial numbers (e.g., certification date, etc.). Also, some of this information (e.g., the revocation date) can be removed or changed, and some other way of referring to a certificate can be used rather than the serial number, although within the scope of the present invention.
- Thus in this case the same tree-hash is used to represent the set of issued and not-yet-expired certificates as well as the set of revoked (not-yet-expired) certificates.
- In either embodiment, a problem may arise when the user queries the Directory with a serial number not corresponding to any issued certificate. (Indeed, while many times the user has already seen a certificate and accesses the Directory just to confirm the current validity of that certificate, at other times the user wishes to obtain the corresponding certificate from the Directory). If the corresponding certificate “does not exist,” the Directory is at a loss to proceed. If the Directory responds truthfully, it may not be believed by the user. If the Directory gives the users all the certificates in its possession (or those relative to a given CA) the user may suspect that the Directory left out the certificate of interest. This problem exists as well in a CRL-based system. Indeed, even if the Directory gives the user all possible tree-based information or just the latest CRL of a given CA, this does not prove to the user that the certificate in question does not exist. (In fact, the actions of the Directory may actually be interpreted as saying that the certificate is valid because it does not appear to have been revoked.) Thus in this thorny situation the Directory would have to be trusted.
- To rectify this problem, it is desired to have the Directory digitally sign that the certificate specified by the user is not among the existing or the not-yet-expired ones. This scheme at least may prevent frivolous answers by putting some liability on the Directory. Better yet, it is preferred that a CA periodically give the Directory a tree-hash specification of the status of all possible serial numbers at that time. For instance, because it is envisioned that a serial number consists of bits, the CA stores these serial numbers in the leaves of a depth-20 (full) tree-hash, together with an additional bit: 0 if not-yet-expired corresponding certificate exists, and 1 otherwise. After completing the hashing, the CA will digitally sign the root value (alone, or together with the root values of some other tree-hash) This enables the Directory to prove to the user that a serial number does not correspond to any issued and not-yet-expired certificate, namely, by giving the user the digital signature of the root value of this last tree-hash, and then the content of the leaf containing the serial number (or other specification) and the content of the siblings of the path from that leaf to the root.
- Just like in the preferred embodiment of the underlying tree-hash scheme itself, one may have two separate trees for this purpose: one tree-hashing the serial numbers of issued and not-yet-expired certificates, and the other tree-hashing the serial numbers not corresponding to issued and not-yet-expired certificates. Of course, one may wish instead to merge together all possible tree-hashes mentioned so far (and possibly others) by having a CA generate a single tree-hash with 220 leaves (i.e., with as many leaves as possible serial numbers), where each leaf stores the corresponding serial number, together with information specifying whether that serial number has been allocated or not, and, if so, whether its certificate has been revoked or not, and possibly other information (e.g, in case of revocation, the revocation date).
- It should be appreciated that the above envisions each leaf corresponding to a serial number for simplicity only. For instance if all the information deemed appropriate about a serial number is no more than 80 bits, each leaf may deal with two serial numbers, provided of course that the information is properly coded so as not to generate confusions, errors or ambiguity. Smaller tree hashes may be built this way.
- It should further be realized this type of digital signature allows batch processing. Namely, rather than signing n quantities separately, a signer tree-hashes them so as to obtain a single root-value, and then digitally signs this root-value (together with additional quantities if desired) when requested to give the signature of quantity i, the signer gives his digital signature of the root, and then the content of leaf i, and the content of the sibling of the party from that leaf to the root. This is a way to substitute n individual signatures (that can be expensive to obtain) with just one signature and n−1 hashing (which are not expensive at all). Notice that the signer does not need to be the one who supplies individualized signatures; if he transfers the n quantities (or the entire tree hash) together with his signature of the root to someone else, he may supply the signatures on demand. Notice that any signature scheme can be used for the root, including pen-written signatures, rather than digital ones.
- The foregoing has outlined some of the more pertinent objects and details of a preferred embodiment of the present invention. These objects and details should be construed to be merely illustrative of some of the more prominent features and applications of the invention. Many other beneficial results can be attained by applying the disclosed invention in a different manner or modifying the invention as will be described. Those skilled in the art will recognize that the invention can be practiced, with modification, in other and different certification methods and schemes within the spirit and scope of the invention.
- One of the preferred implementations of the various routines disclosed above is as a set of instructions in a code module resident in the random access memory of a computer. Until required by the computer, the set of instructions may be stored in another computer memory, for example, in a hard disk drive, or in a removable memory such as an optical disk (for eventual use in a CD ROM) or floppy disk (for eventual use in a floppy disk drive). In addition, although the various methods described are conveniently implemented in a general purpose computer selectively activated or reconfigured by software, one of ordinary skill in the art would also recognize that such methods may be carried out in hardware, in firmware, or in more specialized apparatus constructed to perform the required method steps.
- While the invention has been disclosed in connection with the preferred embodiments shown and described in detail, various modifications and improvements thereon will become readily apparent to those skilled in the art. Accordingly, the spirit and scope of the present invention is to be limited only by the following claim(s).
Claims (1)
1. A method for an intermediary to prove to an end user that certificate information is authenticated by an authority, comprising the steps of:
(a) obtaining at least a portion of an authenticated tree having certificate nodes corresponding to certificate values indicative of the information; and
(b) causing the end user to receive at least one of the following values: certificate values, authenticating values of certificate values, and one or more node values authenticated by an authority.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/947,478 US20020046337A1 (en) | 1995-11-02 | 2001-09-06 | Tree-based certificate revocation system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US614395P | 1995-11-02 | 1995-11-02 | |
US74160196A | 1996-11-01 | 1996-11-01 | |
US08/979,983 US6301659B1 (en) | 1995-11-02 | 1997-11-26 | Tree-based certificate revocation system |
US09/947,478 US20020046337A1 (en) | 1995-11-02 | 2001-09-06 | Tree-based certificate revocation system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/979,983 Continuation US6301659B1 (en) | 1995-11-02 | 1997-11-26 | Tree-based certificate revocation system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20020046337A1 true US20020046337A1 (en) | 2002-04-18 |
Family
ID=44622979
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/979,983 Expired - Lifetime US6301659B1 (en) | 1995-11-02 | 1997-11-26 | Tree-based certificate revocation system |
US09/947,478 Abandoned US20020046337A1 (en) | 1995-11-02 | 2001-09-06 | Tree-based certificate revocation system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/979,983 Expired - Lifetime US6301659B1 (en) | 1995-11-02 | 1997-11-26 | Tree-based certificate revocation system |
Country Status (1)
Country | Link |
---|---|
US (2) | US6301659B1 (en) |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003096339A2 (en) * | 2002-05-09 | 2003-11-20 | Matsushita Electric Industrial Co., Ltd. | Authentication communication system, authentication communication apparatus, and authentication communication method |
US20060059333A1 (en) * | 2004-08-31 | 2006-03-16 | Gentry Craig B | Revocation of cryptographic digital certificates |
US20060137006A1 (en) * | 2004-12-17 | 2006-06-22 | Ramzan Zulfikar A | Use of modular roots to perform authentication including, but not limited to, authentication of validity of digital certificates |
US7315941B2 (en) | 2004-12-17 | 2008-01-01 | Ntt Docomo Inc. | Multi-certificate revocation using encrypted proof data for proving certificate's validity or invalidity |
US20080136586A1 (en) * | 2006-10-27 | 2008-06-12 | Michael Backes | Verification method and system |
US20110038278A1 (en) * | 2007-05-28 | 2011-02-17 | Honeywell International Inc. | Systems and methods for configuring access control devices |
US20110071929A1 (en) * | 2008-01-30 | 2011-03-24 | Honeywell International Inc. | Systems and methods for managing building services |
US20110115602A1 (en) * | 2007-05-28 | 2011-05-19 | Honeywell International Inc. | Systems and methods for commissioning access control devices |
US20110153791A1 (en) * | 2009-12-17 | 2011-06-23 | Honeywell International Inc. | Systems and methods for managing configuration data at disconnected remote devices |
US20110167488A1 (en) * | 2010-01-07 | 2011-07-07 | Honeywell International Inc. | Systems and methods for location aware access control management |
US8232860B2 (en) | 2005-10-21 | 2012-07-31 | Honeywell International Inc. | RFID reader for facility access control and authorization |
US8787725B2 (en) | 2010-11-11 | 2014-07-22 | Honeywell International Inc. | Systems and methods for managing video data |
US8878931B2 (en) | 2009-03-04 | 2014-11-04 | Honeywell International Inc. | Systems and methods for managing video data |
US9019070B2 (en) | 2009-03-19 | 2015-04-28 | Honeywell International Inc. | Systems and methods for managing access control devices |
US9344684B2 (en) | 2011-08-05 | 2016-05-17 | Honeywell International Inc. | Systems and methods configured to enable content sharing between client terminals of a digital video management system |
US9614681B2 (en) * | 2015-01-09 | 2017-04-04 | Adobe Systems Incorporated | Private electronic signature service for electronic documents |
US9704313B2 (en) | 2008-09-30 | 2017-07-11 | Honeywell International Inc. | Systems and methods for interacting with access control devices |
US9894261B2 (en) | 2011-06-24 | 2018-02-13 | Honeywell International Inc. | Systems and methods for presenting digital video management system information via a user-customizable hierarchical tree interface |
US10038872B2 (en) | 2011-08-05 | 2018-07-31 | Honeywell International Inc. | Systems and methods for managing video data |
US10333696B2 (en) | 2015-01-12 | 2019-06-25 | X-Prime, Inc. | Systems and methods for implementing an efficient, scalable homomorphic transformation of encrypted data with minimal data expansion and improved processing efficiency |
US10362273B2 (en) | 2011-08-05 | 2019-07-23 | Honeywell International Inc. | Systems and methods for managing video data |
US10523903B2 (en) | 2013-10-30 | 2019-12-31 | Honeywell International Inc. | Computer implemented systems frameworks and methods configured for enabling review of incident data |
US11017065B2 (en) * | 2016-07-05 | 2021-05-25 | Advanced New Technologies Co., Ltd. | Authority revoking method and device |
Families Citing this family (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8732457B2 (en) | 1995-10-02 | 2014-05-20 | Assa Abloy Ab | Scalable certificate validation and simplified PKI management |
US7337315B2 (en) | 1995-10-02 | 2008-02-26 | Corestreet, Ltd. | Efficient certificate revocation |
US7353396B2 (en) | 1995-10-02 | 2008-04-01 | Corestreet, Ltd. | Physical access control |
US8015597B2 (en) | 1995-10-02 | 2011-09-06 | Corestreet, Ltd. | Disseminating additional data used for controlling access |
US7716486B2 (en) * | 1995-10-02 | 2010-05-11 | Corestreet, Ltd. | Controlling group access to doors |
US7822989B2 (en) | 1995-10-02 | 2010-10-26 | Corestreet, Ltd. | Controlling access to an area |
US7660994B2 (en) | 1995-10-24 | 2010-02-09 | Corestreet, Ltd. | Access control |
US8261319B2 (en) | 1995-10-24 | 2012-09-04 | Corestreet, Ltd. | Logging access attempts to an area |
WO2001022651A2 (en) | 1999-09-20 | 2001-03-29 | Ethentica, Inc. | Cryptographic server with provisions for interoperability between cryptographic systems |
US7260724B1 (en) * | 1999-09-20 | 2007-08-21 | Security First Corporation | Context sensitive dynamic authentication in a cryptographic system |
US6853988B1 (en) * | 1999-09-20 | 2005-02-08 | Security First Corporation | Cryptographic server with provisions for interoperability between cryptographic systems |
US7391865B2 (en) | 1999-09-20 | 2008-06-24 | Security First Corporation | Secure data parser method and system |
US6816900B1 (en) * | 2000-01-04 | 2004-11-09 | Microsoft Corporation | Updating trusted root certificates on a client computer |
US6748531B1 (en) * | 2000-03-28 | 2004-06-08 | Koninklijke Philips Electronics N.V | Method and apparatus for confirming and revoking trust in a multi-level content distribution system |
US7404080B2 (en) | 2001-04-16 | 2008-07-22 | Bjorn Markus Jakobsson | Methods and apparatus for efficient computation of one-way chains in cryptographic applications |
US7120793B2 (en) | 2001-09-28 | 2006-10-10 | Globalcerts, Lc | System and method for electronic certificate revocation |
US7240194B2 (en) | 2002-03-22 | 2007-07-03 | Microsoft Corporation | Systems and methods for distributing trusted certification authorities |
AU2003226458A1 (en) * | 2002-05-09 | 2003-11-11 | Matsushita Electric Industrial Co., Ltd. | Public key certificate revocation list generation apparatus, revocation judgement apparatus, and authentication system |
US20040064691A1 (en) * | 2002-09-26 | 2004-04-01 | International Business Machines Corporation | Method and system for processing certificate revocation lists in an authorization system |
AU2004208331A1 (en) * | 2003-01-25 | 2004-08-12 | Chockstone, Inc. | Micropayment processing method and system |
CA2525398C (en) * | 2003-05-13 | 2014-03-11 | Corestreet, Ltd. | Efficient and secure data currentness systems |
DE602004024553D1 (en) * | 2003-09-19 | 2010-01-21 | Ntt Docomo Inc | METHOD AND DEVICE FOR EFFICIENT CERTIFICATE CANCELLATION |
US8707030B2 (en) | 2003-11-19 | 2014-04-22 | Corestreet, Ltd. | Distributed delegated path discovery and validation |
CA2872032A1 (en) | 2004-01-09 | 2005-08-04 | Corestreet, Ltd. | Signature-efficient real time credentials for ocsp and distributed ocsp |
JP4607567B2 (en) * | 2004-01-09 | 2011-01-05 | 株式会社リコー | Certificate transfer method, certificate transfer apparatus, certificate transfer system, program, and recording medium |
CN101375284B (en) | 2004-10-25 | 2012-02-22 | 安全第一公司 | Secure data parser method and system |
KR100823254B1 (en) * | 2004-12-10 | 2008-04-17 | 삼성전자주식회사 | Method for revoking a public key of content provider |
US8874477B2 (en) | 2005-10-04 | 2014-10-28 | Steven Mark Hoffberg | Multifactorial optimization system and method |
ES2658097T3 (en) | 2005-11-18 | 2018-03-08 | Security First Corporation | Method and secure data analysis system |
US20070150744A1 (en) * | 2005-12-22 | 2007-06-28 | Cheng Siu L | Dual authentications utilizing secure token chains |
US8099603B2 (en) * | 2006-05-22 | 2012-01-17 | Corestreet, Ltd. | Secure ID checking |
US8166532B2 (en) * | 2006-10-10 | 2012-04-24 | Honeywell International Inc. | Decentralized access control framework |
CN103188081A (en) * | 2006-11-07 | 2013-07-03 | 安全第一公司 | Systems and methods for distributing and securing data |
CA2670597A1 (en) | 2006-12-05 | 2008-06-12 | Don Martin | Improved tape backup method using a secure data parser |
US20080172723A1 (en) * | 2007-01-16 | 2008-07-17 | Dominic Pesapane | System and method of collecting data in an access control system |
US9286481B2 (en) * | 2007-01-18 | 2016-03-15 | Honeywell International Inc. | System and method for secure and distributed physical access control using smart cards |
FR2912841B1 (en) * | 2007-02-15 | 2009-05-22 | Soitec Silicon On Insulator | METHOD OF POLISHING HETEROSTRUCTURES |
US8521650B2 (en) | 2007-02-26 | 2013-08-27 | Zepfrog Corp. | Method and service for providing access to premium content and dispersing payment therefore |
US20080244263A1 (en) * | 2007-03-29 | 2008-10-02 | Tc Trust Center, Gmbh | Certificate management system |
WO2009035674A1 (en) | 2007-09-14 | 2009-03-19 | Security First Corporation | Systems and methods for managing cryptographic keys |
US8473756B2 (en) | 2008-01-07 | 2013-06-25 | Security First Corp. | Systems and methods for securing data using multi-factor or keyed dispersal |
ES2449790T3 (en) | 2008-02-22 | 2014-03-21 | Security First Corp. | Systems and methods for secure management and communication in a work group |
CN102428686A (en) | 2009-05-19 | 2012-04-25 | 安全第一公司 | Systems and methods for securing data in the cloud |
CA2781872A1 (en) | 2009-11-25 | 2011-06-09 | Security First Corp. | Systems and methods for securing data in motion |
EP2553905B1 (en) | 2010-03-31 | 2018-05-09 | Security First Corp. | Systems and methods for securing data in motion |
US8824492B2 (en) | 2010-05-28 | 2014-09-02 | Drc Computer Corporation | Accelerator system for remote data storage |
WO2012040231A2 (en) | 2010-09-20 | 2012-03-29 | Orsini Rick L | Systems and methods for secure data sharing |
EP2956887A1 (en) | 2013-02-13 | 2015-12-23 | Security First Corp. | Systems and methods for a cryptographic file system layer |
US9425967B2 (en) * | 2013-03-20 | 2016-08-23 | Industrial Technology Research Institute | Method for certificate generation and revocation with privacy preservation |
US10031679B2 (en) | 2014-11-21 | 2018-07-24 | Security First Corp. | Gateway for cloud-based secure storage |
KR101977109B1 (en) * | 2015-11-17 | 2019-08-28 | (주)마크애니 | Large simultaneous digital signature service system based on hash function and method thereof |
US11025407B2 (en) | 2015-12-04 | 2021-06-01 | Verisign, Inc. | Hash-based digital signatures for hierarchical internet public key infrastructure |
US10153905B2 (en) | 2015-12-04 | 2018-12-11 | Verisign, Inc. | Hash-based electronic signatures for data sets such as DNSSEC |
TWI600334B (en) | 2016-03-23 | 2017-09-21 | 財團法人工業技術研究院 | Security certificate management method for a vehicular network node and vehicular network node applying the same |
US11399020B2 (en) | 2019-06-28 | 2022-07-26 | HCL Technologies Italy S.p.A | System and method for authenticating server identity during connection establishment with client machine |
Family Cites Families (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4200770A (en) | 1977-09-06 | 1980-04-29 | Stanford University | Cryptographic apparatus and method |
US4218582A (en) | 1977-10-06 | 1980-08-19 | The Board Of Trustees Of The Leland Stanford Junior University | Public key cryptographic apparatus and method |
US4309569A (en) * | 1979-09-05 | 1982-01-05 | The Board Of Trustees Of The Leland Stanford Junior University | Method of providing digital signatures |
US4326098A (en) | 1980-07-02 | 1982-04-20 | International Business Machines Corporation | High security system for electronic signature verification |
US4926480A (en) | 1983-08-22 | 1990-05-15 | David Chaum | Card-computer moderated systems |
US4943707A (en) | 1987-01-06 | 1990-07-24 | Visa International Service Association | Transaction approval system |
US4881264A (en) * | 1987-07-30 | 1989-11-14 | Merkle Ralph C | Digital signature system and method based on a conventional encryption function |
US5005200A (en) | 1988-02-12 | 1991-04-02 | Fischer Addison M | Public key/signature cryptosystem with enhanced digital signature certification |
US5016274A (en) | 1988-11-08 | 1991-05-14 | Silvio Micali | On-line/off-line digital signing |
US5003597A (en) | 1989-12-21 | 1991-03-26 | Xerox Corporation | Method and apparatus for data encryption |
US5136647A (en) | 1990-08-02 | 1992-08-04 | Bell Communications Research, Inc. | Method for secure time-stamping of digital documents |
US5136646A (en) | 1991-03-08 | 1992-08-04 | Bell Communications Research, Inc. | Digital document time-stamping with catenate certificate |
US5315657A (en) * | 1990-09-28 | 1994-05-24 | Digital Equipment Corporation | Compound principals in access control lists |
US5396624A (en) | 1990-12-20 | 1995-03-07 | Visa International Service Association | Account file for off-line transaction authorization |
US5340969A (en) | 1991-10-01 | 1994-08-23 | Dresser Industries, Inc. | Method and apparatus for approving transaction card based transactions |
US5157726A (en) | 1991-12-19 | 1992-10-20 | Xerox Corporation | Document copy authentication |
US5261002A (en) | 1992-03-13 | 1993-11-09 | Digital Equipment Corporation | Method of issuance and revocation of certificates of authenticity used in public key networks and other systems |
US5231666A (en) * | 1992-04-20 | 1993-07-27 | International Business Machines Corporation | Cryptographic method for updating financial records |
JP2583010B2 (en) | 1993-01-07 | 1997-02-19 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Method of maintaining consistency between local index table and global index table in multi-tier index structure |
US5432852A (en) * | 1993-09-29 | 1995-07-11 | Leighton; Frank T. | Large provably fast and secure digital signature schemes based on secure hash functions |
US5497422A (en) * | 1993-09-30 | 1996-03-05 | Apple Computer, Inc. | Message protection mechanism and graphical user interface therefor |
US5450493A (en) | 1993-12-29 | 1995-09-12 | At&T Corp. | Secure communication method and apparatus |
US5434919A (en) * | 1994-01-11 | 1995-07-18 | Chaum; David | Compact endorsement signature systems |
US5537475A (en) | 1994-02-01 | 1996-07-16 | Micali; Silvio | Efficient digital signature algorithm and use thereof technical field |
US5420927B1 (en) | 1994-02-01 | 1997-02-04 | Silvio Micali | Method for certifying public keys in a digital signature scheme |
US5544322A (en) | 1994-05-09 | 1996-08-06 | International Business Machines Corporation | System and method for policy-based inter-realm authentication within a distributed processing system |
CA2194475A1 (en) | 1994-07-19 | 1996-02-01 | Frank W. Sudia | Method for securely using digital signatures in a commercial cryptographic system |
US5606617A (en) | 1994-10-14 | 1997-02-25 | Brands; Stefanus A. | Secret-key certificates |
US5615268A (en) * | 1995-01-17 | 1997-03-25 | Document Authentication Systems, Inc. | System and method for electronic transmission storage and retrieval of authenticated documents |
US5677955A (en) | 1995-04-07 | 1997-10-14 | Financial Services Technology Consortium | Electronic funds transfer instruments |
US5717757A (en) | 1996-08-29 | 1998-02-10 | Micali; Silvio | Certificate issue lists |
US5717758A (en) | 1995-11-02 | 1998-02-10 | Micall; Silvio | Witness-based certificate revocation system |
US5604804A (en) * | 1996-04-23 | 1997-02-18 | Micali; Silvio | Method for certifying public keys in a digital signature scheme |
US5666416A (en) | 1995-10-24 | 1997-09-09 | Micali; Silvio | Certificate revocation system |
US5687235A (en) | 1995-10-26 | 1997-11-11 | Novell, Inc. | Certificate revocation performance optimization |
US5699431A (en) | 1995-11-13 | 1997-12-16 | Northern Telecom Limited | Method for efficient management of certificate revocation lists and update information |
US5826262A (en) | 1996-03-22 | 1998-10-20 | International Business Machines Corporation | Parallel bottom-up construction of radix trees |
US5903651A (en) * | 1996-05-14 | 1999-05-11 | Valicert, Inc. | Apparatus and method for demonstrating and confirming the status of a digital certificates and other data |
US5610982A (en) * | 1996-05-15 | 1997-03-11 | Micali; Silvio | Compact certification with threshold signatures |
-
1997
- 1997-11-26 US US08/979,983 patent/US6301659B1/en not_active Expired - Lifetime
-
2001
- 2001-09-06 US US09/947,478 patent/US20020046337A1/en not_active Abandoned
Cited By (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003096339A2 (en) * | 2002-05-09 | 2003-11-20 | Matsushita Electric Industrial Co., Ltd. | Authentication communication system, authentication communication apparatus, and authentication communication method |
US20040003239A1 (en) * | 2002-05-09 | 2004-01-01 | Motoji Ohmori | Authentication communication system, authentication communication apparatus, and authentication communication method |
WO2003096339A3 (en) * | 2002-05-09 | 2005-03-31 | Matsushita Electric Ind Co Ltd | Authentication communication system, authentication communication apparatus, and authentication communication method |
US7831831B2 (en) | 2002-05-09 | 2010-11-09 | Panasonic Corporation | Authentication communication system, authentication communication apparatus, and authentication communication method |
US8024562B2 (en) | 2004-08-31 | 2011-09-20 | Ntt Docomo, Inc. | Revocation of cryptographic digital certificates |
US8156327B2 (en) | 2004-08-31 | 2012-04-10 | Ntt Docomo, Inc. | Revocation of cryptographic digital certificates |
US7814314B2 (en) | 2004-08-31 | 2010-10-12 | Ntt Docomo, Inc. | Revocation of cryptographic digital certificates |
US8006086B2 (en) | 2004-08-31 | 2011-08-23 | Ntt Docomo, Inc. | Revocation of cryptographic digital certificates |
US20090265547A1 (en) * | 2004-08-31 | 2009-10-22 | Gentry Craig B | Revocation of cryptographic digital certificates |
US20090265548A1 (en) * | 2004-08-31 | 2009-10-22 | Gentry Craig B | Revocation of cryptographic digital certificates |
US20100287370A1 (en) * | 2004-08-31 | 2010-11-11 | Gentry Craig B | Revocation of cryptographic digital certificates |
US8209531B2 (en) | 2004-08-31 | 2012-06-26 | Ntt Docomo, Inc. | Revocation of cryptographic digital certificates |
US20060059333A1 (en) * | 2004-08-31 | 2006-03-16 | Gentry Craig B | Revocation of cryptographic digital certificates |
US7743252B2 (en) | 2004-12-17 | 2010-06-22 | Ntt Docomo, Inc. | Use of modular roots to perform authentication including, but not limited to, authentication of validity of digital certificates |
US7315941B2 (en) | 2004-12-17 | 2008-01-01 | Ntt Docomo Inc. | Multi-certificate revocation using encrypted proof data for proving certificate's validity or invalidity |
US7747857B2 (en) | 2004-12-17 | 2010-06-29 | Ntt Docomo, Inc. | Use of modular roots to perform authentication including, but not limited to, authentication of validity of digital certificates |
US20100153714A1 (en) * | 2004-12-17 | 2010-06-17 | Zulfikar Amin Ramzan | Use of modular roots to perform authentication including, but not limited to, authentication of validity of digital certificates |
US20100174904A1 (en) * | 2004-12-17 | 2010-07-08 | Ntt Docomo, Inc. | Use of modular roots to perform authentication including, but not limited to, authentication of validity of digital certificates |
US20060137006A1 (en) * | 2004-12-17 | 2006-06-22 | Ramzan Zulfikar A | Use of modular roots to perform authentication including, but not limited to, authentication of validity of digital certificates |
US7266692B2 (en) | 2004-12-17 | 2007-09-04 | Ntt Docomo, Inc. | Use of modular roots to perform authentication including, but not limited to, authentication of validity of digital certificates |
US8941464B2 (en) | 2005-10-21 | 2015-01-27 | Honeywell International Inc. | Authorization system and a method of authorization |
US8232860B2 (en) | 2005-10-21 | 2012-07-31 | Honeywell International Inc. | RFID reader for facility access control and authorization |
US20080136586A1 (en) * | 2006-10-27 | 2008-06-12 | Michael Backes | Verification method and system |
US20110115602A1 (en) * | 2007-05-28 | 2011-05-19 | Honeywell International Inc. | Systems and methods for commissioning access control devices |
US8351350B2 (en) | 2007-05-28 | 2013-01-08 | Honeywell International Inc. | Systems and methods for configuring access control devices |
US8598982B2 (en) | 2007-05-28 | 2013-12-03 | Honeywell International Inc. | Systems and methods for commissioning access control devices |
US20110038278A1 (en) * | 2007-05-28 | 2011-02-17 | Honeywell International Inc. | Systems and methods for configuring access control devices |
US20110071929A1 (en) * | 2008-01-30 | 2011-03-24 | Honeywell International Inc. | Systems and methods for managing building services |
US9704313B2 (en) | 2008-09-30 | 2017-07-11 | Honeywell International Inc. | Systems and methods for interacting with access control devices |
US8878931B2 (en) | 2009-03-04 | 2014-11-04 | Honeywell International Inc. | Systems and methods for managing video data |
US9019070B2 (en) | 2009-03-19 | 2015-04-28 | Honeywell International Inc. | Systems and methods for managing access control devices |
US20110153791A1 (en) * | 2009-12-17 | 2011-06-23 | Honeywell International Inc. | Systems and methods for managing configuration data at disconnected remote devices |
US9280365B2 (en) | 2009-12-17 | 2016-03-08 | Honeywell International Inc. | Systems and methods for managing configuration data at disconnected remote devices |
US20110167488A1 (en) * | 2010-01-07 | 2011-07-07 | Honeywell International Inc. | Systems and methods for location aware access control management |
US8707414B2 (en) | 2010-01-07 | 2014-04-22 | Honeywell International Inc. | Systems and methods for location aware access control management |
US8787725B2 (en) | 2010-11-11 | 2014-07-22 | Honeywell International Inc. | Systems and methods for managing video data |
US9894261B2 (en) | 2011-06-24 | 2018-02-13 | Honeywell International Inc. | Systems and methods for presenting digital video management system information via a user-customizable hierarchical tree interface |
US9344684B2 (en) | 2011-08-05 | 2016-05-17 | Honeywell International Inc. | Systems and methods configured to enable content sharing between client terminals of a digital video management system |
US10038872B2 (en) | 2011-08-05 | 2018-07-31 | Honeywell International Inc. | Systems and methods for managing video data |
US10362273B2 (en) | 2011-08-05 | 2019-07-23 | Honeywell International Inc. | Systems and methods for managing video data |
US10863143B2 (en) | 2011-08-05 | 2020-12-08 | Honeywell International Inc. | Systems and methods for managing video data |
US10523903B2 (en) | 2013-10-30 | 2019-12-31 | Honeywell International Inc. | Computer implemented systems frameworks and methods configured for enabling review of incident data |
US11523088B2 (en) | 2013-10-30 | 2022-12-06 | Honeywell Interntional Inc. | Computer implemented systems frameworks and methods configured for enabling review of incident data |
US9614681B2 (en) * | 2015-01-09 | 2017-04-04 | Adobe Systems Incorporated | Private electronic signature service for electronic documents |
US10333696B2 (en) | 2015-01-12 | 2019-06-25 | X-Prime, Inc. | Systems and methods for implementing an efficient, scalable homomorphic transformation of encrypted data with minimal data expansion and improved processing efficiency |
US11017065B2 (en) * | 2016-07-05 | 2021-05-25 | Advanced New Technologies Co., Ltd. | Authority revoking method and device |
US11397797B2 (en) | 2016-07-05 | 2022-07-26 | Advanced New Technologies Co., Ltd. | Authority revoking method and device |
Also Published As
Publication number | Publication date |
---|---|
US6301659B1 (en) | 2001-10-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6301659B1 (en) | Tree-based certificate revocation system | |
EP0858702B1 (en) | Tree-based certificate revocation system | |
US5717757A (en) | Certificate issue lists | |
US5793868A (en) | Certificate revocation system | |
US5717758A (en) | Witness-based certificate revocation system | |
US6532540B1 (en) | Apparatus and method for demonstrating and confirming the status of a digital certificates and other data | |
US6487658B1 (en) | Efficient certificate revocation | |
US7337315B2 (en) | Efficient certificate revocation | |
US6901509B1 (en) | Apparatus and method for demonstrating and confirming the status of a digital certificates and other data | |
US6226743B1 (en) | Method for authentication item | |
US7827401B2 (en) | Efficient certificate revocation | |
Aiello et al. | Fast digital identity revocation | |
US6397329B1 (en) | Method for efficiently revoking digital identities | |
Micali | Enhanced certificate revocation system | |
US7529928B2 (en) | Certificate revocation system | |
US5666416A (en) | Certificate revocation system | |
US6292893B1 (en) | Certificate revocation system | |
US8321664B2 (en) | Method and apparatus for efficient certificate revocation | |
US20050154879A1 (en) | Batch OCSP and batch distributed OCSP | |
US20050154878A1 (en) | Signature-efficient real time credentials for OCSP and distributed OCSP | |
Elwailly et al. | Quasimodo: Efficient certificate validation and revocation | |
US20030126085A1 (en) | Dynamic authentication of electronic messages using a reference to a certificate | |
Kikuchi et al. | Performance evaluation of public-key certificate revocation system with balanced hash tree | |
EP1164746B1 (en) | Tree-based certificate revocation system | |
AU2006202855A1 (en) | Signature-efficient real time credentials for OCSP and distributed OCSP |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOVOMODO, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICALI, SILVIO;REEL/FRAME:012865/0618 Effective date: 20020417 |
|
AS | Assignment |
Owner name: CORESTREET SECURITY, LTD., MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:NOVOMODO, INC.;REEL/FRAME:013315/0230 Effective date: 20020828 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |