Patent classifications
G06F11/1438
Systems and methods for reliably injecting control flow integrity into binaries by tokenizing return addresses
Systems and methods of modifying a program binary by injecting code into a function of a program binary that tokenizes the return address of the function. The tokenization of the return address improves the robustness of the program binary against cyberattacks. For example, an attacker's attempt to hijack program flow before a function return will fail since any return address modified by the adversary will be tokenized (e.g., using a binary operation such as an XOR) resulting in an unusable address that will cause the system to crash. One advantage of the improved CFI consumes less average overhead and does not require all of the complications of the conventional CFI systems. In some embodiments, the tokenization includes applying a binary operation on a randomly-generated token and the return address. The token can be generated at transform time, load time, or run time.
Interactive Graphical User Interface for Monitoring Computer Models
A computing system establishes a hierarchy for monitoring model(s). The hierarchy comprises an association between each of multiple measures of a measure level of the hierarchy and intermediate level(s) of the hierarchy. An intermediate level comprises one or more of a measurement category or analysis type. The hierarchy comprises an association between the intermediate level(s) and at least one model. The system monitors the model(s) by generating health measurements. Each of the health measurements corresponds to one of the multiple measures. Each of the health measurements indicates a performance of a monitored model according to a measurement category or analysis type associated in the hierarchy with the respective measure of the multiple measures. The system generates a visualization in a graphical user interface. The visualization comprises a graphical representation of an indication of a health measurement for each of measure(s), and associations in the hierarchy.
Application recovery using a memory image
A memory image can be captured by generating metadata indicative of a state of volatile memory and/or byte-addressable PMEM at a particular time during execution of a process by an application. This memory image can be persisted without copying the in-memory data into a separate persistent storage by storing the metadata and safekeeping the in-memory data in the volatile memory and/or PMEM. Metadata associated with multiple time-evolved memory images captured can be stored and managed using a linked index scheme. A linked index scheme can be configured in various ways including a full index and a difference-only index. The memory images can be used for various purposes including suspending and later resuming execution of the application process, restoring a failed application to a previous point in time, cloning an application, and recovering an application process to a most recent state in an application log.
Managing lifecycle of virtualization software running in a standalone host
Virtualization software installed in a standalone host is remediated according to a desired state model using a desired image of a virtualization software that is used to remediate virtualization software running in hosts which are logically grouped as a cluster of hosts not including the standalone host. The method of remediating the virtualization software installed in the standalone host includes the steps of generating a desired image of the virtualization software of the standalone host from a desired image of the virtualization software of the hosts in the cluster, and upon detecting a difference between an image of the virtualization software currently running in the standalone host and the desired image of the virtualization software of the standalone host, instructing the standalone host to remediate the image of the virtualization software currently running therein to match the desired image of the virtualization software of the standalone host.
SYSTEM TUNING ACROSS LIVE PARTITION MIGRATION
A processor may receive a software fix package. The processor may apply an interim software code fix of the software fix package to software of a device, where the interim software code fix includes adjusting one or more tunable computing parameters to one or more first values. The processor may identify that a reboot of the device is recommended for application of a permanent code fix of the software fix package. The processor may identify that the device was not rebooted after receipt of the software fix package. The processor may determine that a dynamic reconfiguration event has taken place. The processor may apply, automatically, one or more second values for the one or more tunable computing parameters associated with the interim software code fix of the software fix package.
Distributed package management using meta-scheduling
A system for package management includes an interface and a processor. The interface is to receive an indication to install a package. The processor is to determine a configured package using a set local configuration properties and using the package and to launch, using a metascheduler, a set of subschedulers to install a plurality of applications of the configured package.
Information processing system
A remote management system includes a device management service having multiple instances that performs parallel distributed processing through the instances and a worker service having multiple instances that performs parallel distributed processing through the instances. Each instance of the device management service acquires the status of processing related to the recovery of the relevant instance from counter information, and stores the status of the processing related to the recovery of the relevant instance in the counter information when having performed the processing. Each instance of the worker service acquires the status of processing related to the recovery of an instance of the device management service from the counter information, and stores the status of the processing related to the recovery of the instance of the device management service in the counter information when having performed the processing.
Methods, apparatuses and systems for configuring a network environment for a server
Methods, apparatuses and systems for cloud-based disaster recovery are provided. The method, for example, includes receiving, at a cloud-based computing platform, first internet protocol (IP) information relating to a first network environment associated with a server used by a client machine; translating the first IP information, without having to interpose a camouflage layer into the first IP information, and generating second IP information based on the translated first IP information, the second IP information used for creating a second network environment for the server; creating the second network environment for the server; and deploying the server in the created second environment.
LOCKSTEP PROCESSOR RECOVERY FOR VEHICLE APPLICATIONS
A fault tolerant processing environment wherein multiple processors are configured as worker nodes and redundant nodes, with a failed worker node replaced programmatically by a manager node. Each of the processing nodes may include a processor and memory associated with the processor and communicate with other processing nodes using a network. A manager node creates a message passing interface (MPI) communication group having worker nodes and redundant nodes, instructs the worker nodes to perform lockstep processing of tasks for an application, and monitors execution of the tasks. If a node fails, the manager node creates a replacement worker node from one of the redundant processing nodes and creates a new communications group. It then instructs those nodes in the new communications group to resume processing based on the application state and checkpoint backup data.
Data refresh in a replication environment
Data refresh in a replication environment is provided by: reading, by a data services component of a replication environment as part of a data refresh operation, a data store and identifying refresh data, from a source object of source objects of the data store, that is to be provided to a target system, where the data services component is further configured to read a replication log into which changes to source object(s) of the source objects are recorded, and send the changes as change data records to a capture service; and retrieving, by the data services component, the refresh data from the source object and sending the refresh data as refresh data records to the capture service, where the capture service is configured with data record handling routines for applying to received change data records and to the received refresh data records.