Abstract: A dead drop at a node in a dead drop (DD) domain performs actions responsive to detecting events in the DD domain. The node receives a notification request specifying an event to be monitored, the notification request including a dead drop identifier (DDID) referencing a storage location in the DD domain associated with the specified event and a token associated with the DDID. The node further specifies the action to perform in response to detecting the occurrence of the specified event. The node monitors for an occurrence of a specified event within the DD domain. The node detects the occurrence of the specified event within the DD domain. The node further performs a specified action in response to detecting the occurrence of the specified event within the DD domain.

Abstract: In particular embodiments, a method comprising, by one or more computing devices, installing an application on a portion of a physical disk system of a first platform, virtualizing the portion of the physical disk system into a virtual disk system, comprising, storing data in the portion of the physical disk system in a database of the virtual disk system, providing an interface to access the data stored in the database, and providing a plurality sets of drivers for a plurality of platforms, wherein each set of drivers supports native operations with respect to the portion of the physical disk system on a different one of the plurality of platforms, mounting the virtual disk system on a second platform, and executing the application on the second platform, wherein all operations in connection with executing the application are contained within the virtual disk system mounted on the second platform.

Abstract: A client device stores domain identification information for authenticating and validating a user on a dead drop domain. The identification information is stored locally on the client device in the form of a domain ID, which includes a cipher comprising an outer core and an inner core. An outer key for decrypting the outer core is stored locally on the client device, or can be generated based on a passphrase that is provided to the client device by the user. The encrypted outer core stores access information for locating and retrieving an inner key from a dead drop on a node of a dead drop domain. The inner key is used by the client device to decrypt the inner core of the cipher. User validation information is stored in the encrypted inner core.

Abstract: A dead drop at a node in a dead drop (DD) domain performs actions responsive to detecting events in the DD domain. The node receives a notification request specifying an event to be monitored, the notification request including a dead drop identifier (DDID) referencing a storage location in the DD domain associated with the specified event and a token associated with the DDID. The node further specifies the action to perform in response to detecting the occurrence of the specified event. The node monitors for an occurrence of a specified event within the DD domain. The node detects the occurrence of the specified event within the DD domain. The node further performs a specified action in response to detecting the occurrence of the specified event within the DD domain.

Abstract: A sender uses a double-write protocol to pass data to a recipient using a dead drop network architecture. The sender sends, to a dead drop domain, a data payload to store at the dead drop domain, and receives payload access information corresponding to a payload dead drop where the payload data is stored. The sender sends, to the dead drop domain, one or more instances of metadata including the payload access information to store at the dead drop domain, and receives metadata access information corresponding to one or more metadata dead drops where the metadata is stored. The sender provides the metadata access information to one or more recipients. A recipient uses the metadata access information to read the corresponding metadata dead drop. The recipient then uses the payload access information from the metadata to read the payload dead drop and receive the payload data.

Abstract: A sender uses a double-write protocol to pass data to a recipient using a dead drop network architecture. The sender sends, to a dead drop domain, a data payload to store at the dead drop domain, and receives payload access information corresponding to a payload dead drop where the payload data is stored. The sender sends, to the dead drop domain, one or more instances of metadata including the payload access information to store at the dead drop domain, and receives metadata access information corresponding to one or more metadata dead drops where the metadata is stored. The sender provides the metadata access information to one or more recipients. A recipient uses the metadata access information to read the corresponding metadata dead drop. The recipient then uses the payload access information from the metadata to read the payload dead drop and receive the payload data.

Abstract: A dead drop at a node in a dead drop (DD) domain performs actions responsive to detecting events in the DD domain. The node receives a notification request specifying an event to be monitored, the notification request including a dead drop identifier (DDID) referencing a storage location in the DD domain associated with the specified event and a token associated with the DDID. The node further specifies the action to perform in response to detecting the occurrence of the specified event. The node monitors for an occurrence of a specified event within the DD domain. The node detects the occurrence of the specified event within the DD domain. The node further performs a specified action in response to detecting the occurrence of the specified event within the DD domain.

Abstract: A sender uses a double-write protocol to pass data to a recipient using a dead drop network architecture. The sender sends, to a dead drop domain, a data payload to store at the dead drop domain, and receives payload access information corresponding to a payload dead drop where the payload data is stored. The sender sends, to the dead drop domain, one or more instances of metadata including the payload access information to store at the dead drop domain, and receives metadata access information corresponding to one or more metadata dead drops where the metadata is stored. The sender provides the metadata access information to one or more recipients. A recipient uses the metadata access information to read the corresponding metadata dead drop. The recipient then uses the payload access information from the metadata to read the payload dead drop and receive the payload data.

Abstract: A dead drop at a node in a dead drop (DD) domain performs actions responsive to detecting events in the DD domain. The node receives a notification request specifying an event to be monitored, the notification request including a dead drop identifier (DDID) referencing a storage location in the DD domain associated with the specified event and a token associated with the DDID. The node further specifies the action to perform in response to detecting the occurrence of the specified event. The node monitors for an occurrence of a specified event within the DD domain. The node detects the occurrence of the specified event within the DD domain. The node further performs a specified action in response to detecting the occurrence of the specified event within the DD domain.

Abstract: A sender uses a double-write protocol to pass data to a recipient using a dead drop network architecture. The sender sends, to a dead drop domain, a data payload to store at the dead drop domain, and receives payload access information corresponding to a payload dead drop where the payload data is stored. The sender sends, to the dead drop domain, one or more instances of metadata including the payload access information to store at the dead drop domain, and receives metadata access information corresponding to one or more metadata dead drops where the metadata is stored. The sender provides the metadata access information to one or more recipients. A recipient uses the metadata access information to read the corresponding metadata dead drop. The recipient then uses the payload access information from the metadata to read the payload dead drop and receive the payload data.

Abstract: A system virtualizes applications on a managed endpoint using containers. A managed endpoint receives a virtualized container from an IT automation appliance. The virtualized container includes an application and a virtualization module. The virtualization module includes computer program instructions for virtualizing the application. An operating system API call made by the application during execution is intercepted, and a portion of the computer program instructions are executed based on the operating system API call. The computer program instructions modify the behavior of the application to effect the file and data virtualization of the application. A virtualized container can be deployed and updated from an IT automation appliance along with an agent to support the deployment and updating of the virtualized container.

Abstract: A dead drop at a node in a dead drop domain exchanges data between a sender and a recipient. The recipient provides the sender with a dead drop identifier (DDID) referencing the dead drop. The sender sends the dead drop domain a write request including the DDID. Nodes within the domain forward the request to other nodes until the write request reaches the node containing the dead drop identified by the DDID. The node receives data from the sender and stores the data in the identified dead drop. The recipient sends the dead drop domain a read request including the DDID and nodes within the domain forward the request to other nodes until the read request reaches the node containing the dead drop identified by the DDID. The node retrieves the data from the dead drop and provides the data to the recipient.

Abstract: In one embodiment, transmitting, from a first computing device, a private-home-network-discovery message that comprises a first identifier corresponding to a private-home-networking system, receiving, at the first computing device, one or more content-response messages from a second computing device that collectively comprise a second identifier corresponding to the second computing device, a third identifier corresponding to the private-home-networking system, and information corresponding to content stored on the second computing device, and storing, at the first computing device, the second and third identifiers and the information received in the one or more content response messages for access by one or more applications hosted on the first computing device, one of the applications being associated with administering the private-home-networking system.