Systems and methods are disclosed with respect to using a blockchain for managing the subrogation claim process related to a vehicle collision, in particular, utilizing evidence oracles as part of the subrogation process. An exemplary embodiment includes receiving recorded data from one or more connected devices at a geographic location; analyzing the recorded data, wherein analyzing the recorded data includes determining that an collision has occurred involving one or more vehicles; generating a transaction including the data indicative of the collision based upon the analysis; and transmitting the transaction to at least one other participant in the distributed ledger network.

An apparatus and method for mapping user-associated data to an identifier. The apparatus includes a processor configured to store a plurality of user identifiers. User identifiers may be determined by way of user or by machine-learning modules or the like. Apparatus receives user-associated data from a user to be stored in a resource data storage system. User-associated data may include a plurality of data sets to be mapped to an identifier. Mapping a data set to an identifier may be user determined or use a machine-learning module. Apparatus is configured to update the immutable sequential listing associated with the data set with the mapped identifier.

A secure programming system and method for provisioning and programming a target payload into a programmable device mounted in a programmer. The programmable device can be authenticated before programming to verify the device is a valid device produced by a silicon vendor. The authentication process can include a challenge-response validation. The target payload can be programmed into the programmable device and linked with an authorized manufacturer. The programmable device can be verified after programming the target payload by verifying the silicon vendor and the authorized manufacturer. The secure programming system can provision different content into different programmable devices simultaneously to create multiple final device types in a single pass.

Techniques are described for managing a network through use of a security device that includes, or has access to, a blockchain node. The security device may manage a network of Internet-of-Things (IoT) devices in a home or other environment. The security device may act as an intermediary to manage secure, trusted communications between the IoT device(s) and external service(s). The security device may also provide network security features such as a network firewall. In some implementations, the security device may run a blockchain node, and the blockchain could be used to establish a verifiable home identity. The security device may interact with external resources and/or services, such as utility services, e-commerce services, and so forth, through this secure mechanism.

A proxy server receives from a client device a request for a network resource that is hosted at an origin server for a domain. The request is received at the proxy server as a result of a DNS request for the domain resolving to the proxy server. The origin server is one of multiple origin servers that belong to different domains that resolve to the proxy server and are owned by different entities. The proxy server retrieves the requested network resource. The proxy server determines that the requested resource is an HTML page. The proxy server scans the HTML page to locate one or more modification tokens that each indicates content that is subject to being modified. For at least one of the located modification tokens, the proxy server automatically modifies at least a portion of the content of the HTML page that corresponds to that modification token. The proxy server then transmits the modified HTML page to the client device.

Methods and systems pertaining secure transaction systems are disclosed. In one implementation, a computer with a verification token associated with a computer can send user authentication data as well as a secure datum to a control server. The verification token may obtain the secure datum from a validation entity. The control server can validate the secure datum and authentication data and can generate a payer authentication response.

A network node may include one or more processors. The one or more processors may receive a message that is associated with one or more signatures and one or more second signatures. The one or more signatures may have been validated by a particular node. The one or more processors may determine that the particular node is a trusted node. The network node may be configured not to validate signatures that have been validated by a trusted node. The one or more processors may determine that the one or more signatures have been validated by the particular node. The one or more processors may sign or provide the message, without validating the one or more signatures, based on determining that the one or more signatures have been validated by the particular node.

The present disclosure relates to the field of computer technologies and it discloses a method for encrypting a picture performed at a sending device, the method including: obtaining, by a sending device raw data of a to-be-encrypted picture, a first key, a second key, and location information that is used for adding disturbance data to the raw data; generating the disturbance data, and adding the disturbance data to the raw data according to the location information, to obtain first data; encrypting the first data by using the first key, to obtain the second data, and encrypting the first key and the length of the disturbance data by using the second key, to obtain first encrypted data; and sending the second data, the first encrypted data, and the second key to a receiving device.

At a transmitter node, a commitment value C is obtained as a function of a message m. The commitment value C and transmitter terms of use T.sup.A for the message m are then sent to a receiver node without disclosing the message m. A cryptographic receiver signature S.sub.B over the commitment value C and the transmitter terms of use T.sup.A is received from the receiver node, where the cryptographic receiver signature S.sub.B is signed with a private key kprv-B associated with the receiver node. The receiver signature S.sub.B may be authenticated using a public key kpuh-B for the receiver node. If the receiver signature S.sub.B is successfully authenticated, the message m and the receiver signature S.sub.B are signed using a private key kprv-A for the transmitter node to obtain a transmitter signature S.sub.A. The message m and the transmitter signature S.sub.A may then be sent to the receiver node.

Methods, systems, storage media for authentication are described. On the methods includes receiving, at a smart contract on a distributed ledger, a signed authentication challenge. The method includes verifying the identity of the user who signed authentication challenge. The method includes raising an event that indicates that the user has been authenticated; wherein a server listens for events from the smart contract, and associates a session between the browser and the server with the user based on the event.