Abstract: A user-provided keystore may be utilized in a boot process to verify a boot image as disclosed herein. A device may be determined to be in a locked or verified state. A selected keystore may be determined to not verify against a first key such as a root key. A user may provide a keystore to a device. The system may display a prompt to the user which asks whether the user would like to continue to boot or not, if the system determines that the keystore does not verify against the first key. The user may respond to the prompt by indicating a desire to continue booting. The system may determine that the boot image verifies against the keystore and finish booting the device. Thus, the prompt may alert the user to a threat to the integrity of the boot process or device.

Abstract: Systems and techniques are provided for dynamic authorization. A signal may be received from a sensor. A concept may be determined from the signal. The concept may be a location of a computing device, an action being performed with the computing device, an identity of a user of the computing device, or a temporal context for the computing device. A current pattern may be determined from the concept. The current pattern may be matched to a stored pattern. The stored pattern may be associated with a security outcome. The security outcome may be sent to be implemented. A security message may displayed indicating the security outcome and part of the stored pattern that was matched to the current pattern. The security outcome may be causing presentation of an authentication prompt or not causing presentation of an authentication prompt.

Abstract: Systems and techniques are provided for dynamic authorization. A signal may be received from a sensor. A concept may be determined from the signal. The concept may be a location of a computing device, an action being performed with the computing device, an identity of a user of the computing device, or a temporal context for the computing device. A current pattern may be determined from the concept. The current pattern may be matched to a stored pattern. The stored pattern may be associated with a security outcome. The security outcome may be sent to be implemented. A security message may displayed indicating the security outcome and part of the stored pattern that was matched to the current pattern. The security outcome may be causing presentation of an authentication prompt or not causing presentation of an authentication prompt.

Abstract: A user-provided keystore may be utilized in a boot process to verify a boot image as disclosed herein. A device may be determined to be in a locked or verified state. A selected keystore may be determined to not verify against a first key such as a root key. A user may provide a keystore to a device. The system may display a prompt to the user which asks whether the user would like to continue to boot or not, if the system determines that the keystore does not verify against the first key. The user may respond to the prompt by indicating a desire to continue booting. The system may determine that the boot image verifies against the keystore and finish booting the device. Thus, the prompt may alert the user to a threat to the integrity of the boot process or device.

Abstract: A device includes at least one processor, a messaging service operable by the at least one processor to determine whether an outgoing message is a likely premium message, and a user interface module operable by the at least one processor to responsive to determining that outgoing message is the likely premium message, output, for display, a prompt for confirmation to send the outgoing message to a likely premium code, and receive an indication of input detected within the prompt for confirmation. The module is further operable by the at least one processor to selectively send, based at least in part on the received indication of the user input, the outgoing message to the likely premium code.

Abstract: A device includes at least one processor, a messaging service operable by the at least one processor to determine whether an outgoing message is a likely premium message, and a user interface module operable by the at least one processor to responsive to determining that outgoing message is the likely premium message, output, for display, a prompt for confirmation to send the outgoing message to a likely premium code, and receive an indication of input detected within the prompt for confirmation. The module is further operable by the at least one processor to selectively send, based at least in part on the received indication of the user input, the outgoing message to the likely premium code.

Abstract: Systems, methods, routines and/or techniques are described to protect users from undesirable content, for example, on an open platform. One or more embodiments may prevent the installation of an application package or warn a user if the application package may be undesirable (e.g., because it may contain malware). In one or more embodiments, a method may include receiving a first request to install an application package, and receiving and/or capturing metadata related to the application package. The method may include communicating a second request (e.g., including the metadata) to a remote server, such that the remote server can determine whether the application package may be undesirable. The method may include receiving a response from the remote server, where the response may indicate whether the application package may be undesirable, and initiating installation of the application package if the application package is determined to be safe and/or acceptable.

Abstract: An application distribution server may be operable to perform an application distribution process for an application, where the application distribution process may comprise a plurality of phases. The plurality of phases may comprise, in sequence, a developer account creation phase, a risk assessment phase, an application upload phase, an application publication phase, an application promotion phase and an application download phase. The application distribution server may detect, at each of the plurality of phases, whether a particular behavior corresponding to use of the application to distribute undesirable software may occur. In instances when an occurrence of the particular behavior is detected at a certain phase in the application distribution process, the application distribution server may continue, utilizing a trap system, one or more subsequent phases after the certain phase for the application, without communicating information on the detection of the occurrence of the particular behavior.

Abstract: The present disclosure provides a system and method for a mobile device to run an application that requires one or more permissions. The mobile device may comprise a screen and a processor. The one or more permissions may be displayed graphically on the screen prior to the application being installed by the processor.

Abstract: Systems, methods, routines and/or techniques for time delay on services (e.g., verification services) that detect undesirable content are described. In some embodiments, a flexible verification service prevents users (e.g., hackers) from using the verification service “as an oracle” to predict whether the user's application or software program will be detected by the verification service. The verification service, after receiving a verification request from a client device, may delay or prevent the communication of a verification response to the client device. The verification service may evaluate a verification request to determine a level of risk associated with the request. The verification service may communicate an initial response to the client device that submitted the verification request. The verification service may eventually communicate the verification response to the client device, for example, after a period of delay.

Abstract: A system and method attempts to access a portable electronic document using different methods depending on whether the user attempting access is in front of, or behind, a firewall.

Abstract: In a winding apparatus for endless threads, a revolving disc (6) has at least two clamping chucks (8, 10) rotatably supported on the periphery thereof. A friction roll (2), the shaft (4) of which as well as the shaft (12) of the revolving disc (6) are mounted in a frame (14) at fixed locations. The shaft (12) is connected to a first drive device (120) and the first shaft (4) is connected to a second drive device (40). Each clamping chuck (8, 10) is provided with its own third drive device (80), and fourth drive device (100) respectively.

Abstract: In a winding apparatus for endless threads with a revolving disc (6) in the periphery of which at least two clamping chucks (8, 10) are rotatably supported and with a friction roll (2) the shaft of which as well as the shaft (12) of the revolving disc (6) are mounted at fixed locations in a frame, a shaft each (4, 12) is connected to a first drive device (120), and with a second drive device (40) respectively. Each clamping chuck is provided with its own third drive device (80), and a fourth drive device (100) respectively. The contacting pressure between the friction roll (2) and a respective clamping chuck each can be adjusted as a function of the diameter of a thread package being built on a clamping chuck.

Abstract: A bobbin chuck for winding manmade threads can have a length of e.g. 1200 mm and can consist of a bearing portion and of a cantilevered portion supported by it. The cantilevered portion includes an extension (66) of a shaft (64) supported directly by the bearings and a tubular part (60) taking up the bobbin tubes which is connected at two locations (68, 70) to the shaft extension (66) and secured against rotation relative thereto. The shaft extension (66) as well as the tube (60) are free to perform oscillations according to their natural oscillation modes.