H04L9/321

Peer-to-peer confidential document exchange

Systems and methods for peer-to-peer secure document exchange are disclosed. The system may allow a document provider to securely transmit a certified document to a document verifier using decentralized storage. The verifier system may generate a session key pair and transmit the session public key to a trusted API provider. The trusted API provider may generate a session nonce. The verifier system may transmit the session nonce to the provider system. The provider system may use the session nonce to retrieve the session public key. The provider system may encrypt a certified document using the session public key and store the encrypted certified document in the decentralized storage. The verifier system may retrieve the encrypted certified document by polling the trusted API provider based on the session nonce. The verifier system may decrypt the encrypted certified document using the session private key.

System enabling digital signature of a document in an online meeting
11695571 · 2023-07-04 ·

The system comprises a first data processing system, a second data processing system, and a server. The system further includes four screens. The first and third screen comprises a video stream and an audio stream. The second and fourth screen comprises a video stream displaying visual contents of a first document that is to be digitally signed by the first and second user. The first and second data processing systems are configured to receive a first and second unique signature from the first and second user, respectively, and add it to the first document. The server is configured to coordinate communication between the first and second data processing systems, record the visual contents of the first screen, the second screen, the third screen and the fourth screen, and store the recording.

Blockchain controlled cross-domain data transfer

An example operation may include one or more of receiving a data file with off-chain content that originated in a first security domain of a multi-domain blockchain network, verifying that the on-chain and off-chain content satisfies a cross-domain security policy between the first security domain and a second security domain within the multi-domain blockchain network with a different security policy than the first security domain, in response to verifying the on-chain and off-chain content, signing the on-chain portion of the data file with a signature of a cross-domain endorsement peer, transmitting the signed on-chain portion of the data file to an ordering service of the multi-domain blockchain network, and transmitting the off-chain portion of the data file to a cross-domain content controller in the first security domain.

CROSS-BLOCKCHAIN IDENTITY AND KEY MANAGEMENT
20230006835 · 2023-01-05 · ·

A method of implementing a revocable threshold hierarchical identity-based signature scheme may include receiving an identifier associated with a user. A first secret key based on the identifier may be generated. A string and the identifier may be directed to be posted on a block of a blockchain. A second secret key may be generated using the string, the first secret key, and the identifier. The block that includes the string and the identifier may be signed using the second secret key. A message may be signed using the second secret key to generate a signature. The signature may be provided to a device. The signature may be verifiable by the device using the string and the identifier obtained from the block by the device.

SYSTEMS AND METHODS TO PERFORM CONTACTLESS CARD ACTIVATION

Example embodiments relate to performing activation techniques for contactless cards. For example, embodiments may include performing a near-field communication (NFC) exchange with a contactless card, processing a message comprising data to activate the contactless card, communicating the data to a server to activate the contactless card; and receiving a response from the server, the response to indicate whether the contactless card is successfully activated or not successfully activated.

Scalable byzantine fault-tolerant protocol with partial tee support
11546145 · 2023-01-03 · ·

A method is provided for preparing a plurality of distributed nodes to perform a protocol to establish a consensus on an order of received requests. The plurality of distributed nodes includes a plurality of active nodes, the plurality of active nodes including a primary node, each of the plurality of distributed nodes including a processor and computer readable media. The method includes preparing a set of random numbers, each being a share of an initial secret. Each share of the initial secret corresponds to one of the plurality of active nodes. The method further includes encrypting each respective share of the initial secret, binding the initial secret to a last counter value to provide a commitment and a signature for the last counter value, and generating shares of a second and of a plurality of subsequent additional secrets by iteratively applying a hash function to shares of each preceding secret.

User ID codes for online verification

Methods and systems for establishing a chain of relationships are disclosed. An identity verification platform receives a first request for registration comprising an identification of a first user, identification of an entity, and a relationship between the first user and the entity; verifies the identity of the first user and the relationship between the first user and the entity; and verifies that the entity is legitimate. Once a relationship between a first individual, invited by the first user, and the entity is confirmed, the platform creates a custom badge representing the relationship between the first individual and the entity for display on the entity's website. The platform receives an identification of a selection by an end user of the custom badge and, responsive to receiving the identification of the selection, renders, on a domain controlled by the identity verification platform, a verification that the relationship between the first individual and the entity is valid.

Wireless terminal authentication
11546174 · 2023-01-03 · ·

A device for wireless terminal authentication may include at least one processor configured to receive, from a wireless terminal device, a request for user information, the request comprising a certificate corresponding to the wireless terminal device. The at least one processor may be further configured to verify the certificate based at least in part on a public key stored on the electronic device. The at least one processor may be further configured to, when the certificate is verified, determine whether the certificate indicates that the wireless terminal device is authorized to receive the requested user information. The at least one processor may be further configured to transmit, to the wireless terminal device, the requested user information when the certificate indicates that the wireless terminal device is authorized to receive the requested user information.

Adaptive identification systems and methods

A computer system is provided. The computer system includes a memory and a processor coupled to the memory. The processor is configured to receive a first message from an identity provider, the first message including an arbitrary identifier generated by the identity provider, the arbitrary identifier being incompatible with a dependent process that is reliant upon the identity provider; encode, in response to reception of the first message, the arbitrary identifier into an encoded identifier that is compatible with the dependent process; and transmit a second message including the encoded identifier to the dependent process.

Apparatus and method for terminating an authorization to access a record in a blockchain ledger

A record of authorization including user information is received and appended to a blockchain. The record of authorization authorizes access by a third-party application to the user information for an access duration. The user information is encrypted by a group key and access duration is based on a change to the group key. The group key comprises a public/private key pair, and the access duration is implemented by an authorization group of nodes having the group key. The group key corresponds to either a valid group key at or near the start of the access duration, that enables decryption of a message in the record of authorization that includes the user information, or an incompatible group key at or after the end of the access duration, that does not enable decryption of the message in the record of authorization that includes the user information.