A secure method for exchanging entities via a blockchain is presented. The method comprises receiving, from a user over a communications network, an invitation to perform an exchange of entities; generating a redeem script comprising metadata; hashing the redeem script to generate a redeem script hash; sending the first script and the first script hash on a distributed hash table (DHT); and generating an invitation transaction comprising an output associated with an encrypted digital asset, and a hash of a script comprising an indication of entities to be exchanged, conditions for the exchange, and a public cryptographic key associated with the user.

A vehicle system includes: a reprogramming slave device that is an electronic control unit (hereinafter, referred to as ECU) to be a target of updating an update file of a program stored among a plurality of the ECUs; a reprogramming master device that transmits the update file to the reprogramming slave device in response to a request from a terminal operable by a vehicle user to control updating of the program stored in the reprogramming slave device; and a determination unit that determines traveling propriety of a vehicle when the update file is rewritten in the reprogramming slave device. The vehicle device functions as the reprogramming master device, and includes: an obtaining unit that obtains the traveling propriety determined by the determination unit; and a notification command unit that commands a notification medium to notify information of the traveling propriety obtained by the obtaining unit.

Examples of systems described herein include a virtualized file server including a first file server virtual machine and a second file server virtual machine configured to manage a distributed file share of storage items. The second file server virtual machine is configured to manage a particular storage item of the distributed file share of storage items. The first file server virtual machine is configured to, in response to receipt of a referral request for a file share path for the particular storage item from a client, look up a file share path for the particular storage item in a map of at least a portion of the distributed file share of storage items, and provide a referral with the file share path that identifies the second file server virtual machine.

Examples of systems described herein include a virtualized file server including a first file server virtual machine and a second file server virtual machine configured to manage a distributed file share of storage items. The second file server virtual machine is configured to manage a particular storage item of the distributed file share of storage items. The first file server virtual machine is configured to, in response to receipt of a referral request for a file share path for the particular storage item from a client, look up a file share path for the particular storage item in a map of at least a portion of the distributed file share of storage items, and provide a referral with the file share path that identifies the second file server virtual machine.

A server system, based on content of a first file stored on a first client device being modified, automatically receives a copy of the modified first file from a first transfer client, implemented on the first client device, the copy of the modified first file being an updated version of the first file generated from content of the first file being modified. The server system receives, from the first transfer client, first metadata associated with the updated version of the first file, the first metadata being assigned a first priority greater than a second priority assigned to the copy of the modified first file. The server system automatically transfers the first metadata to a second transfer client, implemented on a second client device, before the copy of the modified first file is transferred to the second transfer client to be stored on the second client device.

A server system, based on content of a first file stored on a first client device being modified, automatically receives a copy of the modified first file from a first transfer client, implemented on the first client device, the copy of the modified first file being an updated version of the first file generated from content of the first file being modified. The server system receives, from the first transfer client, first metadata associated with the updated version of the first file, the first metadata being assigned a first priority greater than a second priority assigned to the copy of the modified first file. The server system automatically transfers the first metadata to a second transfer client, implemented on a second client device, before the copy of the modified first file is transferred to the second transfer client to be stored on the second client device.

A packet processing technique can include receiving a packet, and parsing the packet based on a protocol field to generate a parse result vector. The parse result vector is used to select between forwarding the packet to a virtual machine executing on a host processing integrated circuit, forwarding the packet to a physical media access controller, multicasting the packet to multiple virtual machines executing on the host processing integrated circuit, and sending the packet to a hypervisor.

A packet processing technique can include receiving a packet, and parsing the packet based on a protocol field to generate a parse result vector. The parse result vector is used to select between forwarding the packet to a virtual machine executing on a host processing integrated circuit, forwarding the packet to a physical media access controller, multicasting the packet to multiple virtual machines executing on the host processing integrated circuit, and sending the packet to a hypervisor.

A configuration for a component of a primary node is synchronized with a configuration for a component of a partner node in a different cluster by replicating the primary node configuration with the partner node. A baseline configuration replication comprises a snapshot of a component configuration on the primary. The baseline configuration can be generated by traversing through the configuration objects, capturing their attributes and encapsulating them in a package. The baseline package can then be transferred to the partner node. The configuration objects can be applied on the partner node in the order in which they were captured on the primary node. Attributes of the configuration objects are identified that are to be transformed. Values for the identified attributes are transformed from a name space in the primary node to a name space in the partner node.

A cloud-based write-once object store is configured to store inode-based data exported to the store from an enterprise file system. For each version of data (e.g., a file) exported to the store, there is a version of the inode corresponding to that data. As versions of the data are exported to the cloud, the system creates multiple versions of the inode. The set of inode versions corresponding to the versions of the file have a pointer associated therewith that specifies the latest version of the data associated with the inode. The inode versions in the set share the same pointer. The inode versions represent a revision history for the inode. For each inode version corresponding to a version of the data, information is received and stored in a new portion of the object store. The inode version for a file version comprises a list of data chunks for the file.