Abstract: A system of secure data packets for transmission over a packet switched network includes an expiring Hash-based Message Authentication Code (HMAC) appended to the data packet. The expiring HMAC is calculated based on a shared secret and a clock time. A receiving network application or firewall with the shared secret validates the secure data packets based on a comparison of the expiring HMAC to the receiving network or application's own calculation of a valid HMAC based on the shared secret and the clock time. Applications executing on the receiving and sending networks do not need modification to use the secure data packet protocol because HMAC appending, validation, and removal may all occur at network boundaries on firewalls. Protected host endpoints may serve client endpoints using expiring HMAC data packets and other validation information based on security data stored on a shared ledger such as nonce values encountered by the network.

Abstract: A blockchain file system provides access to a data storage volume on a blockchain. The blockchain volume is mounted by the host computing system in the same way as a conventional data storage volume from the perspective of the user space applications. The host computing system includes a local write-ahead blockchain journal that links bundles of mutations to the filesystem related to filesystem operations into a chain of digital signatures. One or more of the mutation bundles are included in a signed blockchain transaction that is broadcast to a network of the blockchain that, when confirmed into the blockchain, will carry out the filesystem operations on the blockchain data storage volume. Also provided is a novel blockchain addressing scheme, copy-on-write functionality, and de-duplication features write-ahead filesystem journal.

Abstract: Methods, systems, and apparatuses for implementing shared-license software management are provided. Shared-license software management may be performed by generating a request for a license for running a process of a shared-license software application. The request is communicated to a license server, and the process is made available for scheduling an operation when a grant for the requested license is received from the license server, wherein the grant comprises a license quantum, which is an amount of central processing unit time for which the license has been granted to the process.

Abstract: Methods, systems, and apparatuses for implementing shared-license software management are provided. Shared-license software management may be performed by generating a request for a license for running a process of a shared-license software application. The request is communicated to a license server, and the process is made available for scheduling an operation when a grant for the requested license is received from the license server, wherein the grant comprises a license quantum, which is an amount of central processing unit time for which the license has been granted to the process.

Abstract: Methods, systems, and apparatuses for implementing shared-license management are provided. Shared-license management may be performed by receiving from a remote client a license request to run a process of a shared-license application; adding the process to a queue maintained for processes waiting for license grants; and reserving at least one license instance for the received license request, the at least one license instance comprising a quantum of CPU time for running the process.