Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: The techniques and systems disclosed herein pertain to preventing unauthorized access to computing resources by unauthorized persons by deploying biometric security. To implement biometric security, the computing device, possibly by the OS, may obtain samples of one or more biometric factors unique to the owner. The computing device may construct pattern-matching templates corresponding to the biometric samples, which may be stored for later use when a protected resource is requested. Computing resources may be selected for protection by a biometric security mechanism by an authorized user or by other techniques or default settings. Before allowing certain restricted actions, the OS may request that the user provide one of the previously registered biometric samples. If the biometric sample matches the user's stored pattern-matching template, the OS may grant access to the computing resource, otherwise, the OS may deny access to the computing resource.

Abstract: Techniques described herein leverage a trusted entity within a domain to enable devices to establish trust with one another so they can securely discover each other and connect to one another. In various examples discussed herein, a device is configured to provide trust information to, and/or receive trust information from, the trusted entity. The trust information may include, for example, a public key of an encryption key pair, a certificate signed by the trusted entity proving authenticity, and/or a hash function and a hash seed used to compute a series of results that form a hash chain. The device may use the trust information to discover another device and to connect to the other device securely and automatically (e.g., with no user involvement or limited user involvement). Moreover, the device may use the trust information to dynamically change a MAC address being used to communicate with the other device.

Abstract: A remote access system connects a server computer with one or more client computers, where devices are connected locally at the client computers. The devices are recognized by the client computers and a device driver is provided for each connected and recognized device. A virtual driver is created at the server computer from information specific to the device, such that the virtual driver acts as an actual driver to an application on the server computer. The application through the virtual driver is able to recognize and provide commands to the connected device.

Abstract: The techniques and systems disclosed herein pertain to preventing unauthorized access to computing resources by unauthorized persons by deploying biometric security. To implement biometric security, the computing device, possibly by the OS, may obtain samples of one or more biometric factors unique to the owner. The computing device may construct pattern-matching templates corresponding to the biometric samples, which may be stored for later use when a protected resource is requested. Computing resources may be selected for protection by a biometric security mechanism by an authorized user or by other techniques or default settings. Before allowing certain restricted actions, the OS may request that the user provide one of the previously registered biometric samples. If the biometric sample matches the user's stored pattern-matching template, the OS may grant access to the computing resource, otherwise, the OS may deny access to the computing resource.

Abstract: A remote access system connects a server computer with one or more client computers, where devices are connected locally at the client computers. The devices are recognized by the client computers and a device driver is provided for each connected and recognized device. A virtual driver is created at the server computer from information specific to the device, such that the virtual driver acts as an actual driver to an application on the server computer. The application through the virtual driver is able to recognize and provide commands to the connected device.

Abstract: Techniques for discovering, connecting to, disconnecting from, reconnecting to, updating, and removing workspaces are described. In one embodiment, a list of discovered workspaces is maintained on a user device. Shortcuts for resources corresponding to each respective one of the discovered workspaces are integrated into a user interface of the user device. A request to access one of the resources contained in one of the discovered workspaces is received. Responsive to receiving the request, a connection from the user device to one or more resource hosts containing the resources corresponding to the indicated one of the discovered workspaces is opened. Access from the user device to the resources stored on the resource host(s) corresponding to the indicated one of the discovered workspaces is enabled by presenting shortcuts for resources corresponding to the discovered workspaces as though they were local resources.

Abstract: A MIME or XML formatted message is stored and a map is processed in place of a message. The map is a compact representation of the message. The map is indicative of the content and structure of the message. The map comprises tags that map to and are indicative of portions of the message. When a portion of the message is to be accessed, the associated tag in the map is processed to determine the location of the associated portion of the message, and the associated portion of the message is accessed at the location. To allow accurate decryption of signed messages, the format of the message is preserved.

Abstract: A remote access system connects a server computer with one or more client computers, where devices are connected locally at the client computers. The devices are recognized by the client computers and a device driver is provided for each connected and recognized device. A virtual driver is created at the server computer from information specific to the device, such that the virtual driver acts as an actual driver to an application on the server computer. The application through the virtual driver is able to recognize and provide commands to the connected device.

Abstract: Techniques for discovering, connecting to, disconnecting from, reconnecting to, updating, and removing workspaces are described. In one embodiment, a list of discovered workspaces is maintained on a user device. Shortcuts for resources corresponding to each respective one of the discovered workspaces are integrated into a user interface of the user device. A request to access one of the resources contained in one of the discovered workspaces is received. Responsive to receiving the request, a connection from the user device to one or more resource hosts containing the resources corresponding to the indicated one of the discovered workspaces is opened. Access from the user device to the resources stored on the resource host(s) corresponding to the indicated one of the discovered workspaces is enabled by presenting shortcuts for resources corresponding to the discovered workspaces as though they were local resources.

Abstract: A MIME or XML formatted message is stored and a map is processed in place of a message. The map is a compact representation of the message. The map is indicative of the content and structure of the message. The map comprises tags that map to and are indicative of portions of the message. When a portion of the message is to be accessed, the associated tag in the map is processed to determine the location of the associated portion of the message, and the associated portion of the message is accessed at the location. To allow accurate decryption of signed messages, the format of the message is preserved.