SAFECHANNEL ENCRYPTED MESSAGING SYSTEM

Patent Information

  • Patent No.: US 10,230,693 B2
  • Date of Patent: Mar. 12, 2019
  • Applicant: WebCloak, LLC, Irvine, CA (US)
  • Inventor: Martin Dawson, Laguna Beach, CA (US)
  • Assignee: WEBCLOAK, LLC, Irvine, CA (US)
  • Notice: Subject to any disclaimer, the term of this patent is extended or adjusted under 35 U.S.C.154(b) by 211 days. This patent is subject to a terminal disclaimer.
  • Application No.: 15/011,080
  • Filed: Jan. 29, 2016
  • Prior Publication Data: US 2016/0226

Abstract

Portable, hand-held electronic devices for and methods to enabling a user to interact with a native operating system (OS) running on a host device and a virtual machine running on top of the native OS are presented. The host device includes a processor to communicate with an application having a target network address. The devices includes an onboard database that stores user credential information and a portable encryption and authentication service module (PPEASM) that allows to make a secure communication channel with the host device. The PPEASM configures the processor to negotiate authentication of the user with an application running on top of the native OS utilizing the user credential information, render an application running on top of the virtual machine, and pass data between the application running on top of the virtual machine and a second application running on top of the native OS.

Claims

  1. A portable, hand-held electronic device, operable in conjunction with a host device running a native operating system (OS), comprising:

    • an onboard database storing user credential information; and
    • an onboard memory storing software instructions that, when executed by a processor of the host device, configure the processor to perform the following steps:
      • negotiating, by a virtual machine on the portable device, authentication of the user utilizing the user credential information between a VM application running on the virtual machine and a host application running on top of the native OS;
      • trapping, by the virtual machine, input/output (i/o) events from the native OS;
      • encrypting a first data from the VM application with the generated security token; and
      • passing the encrypted first data between the VM application and the host application as a function of the trapped i/o events.

  2. The device of claim 1, wherein the software instructions further configure the processor to automatically encrypt a portion of the trapped i/o events and transmit the encrypted portion to the host application.

  3. The device of claim 1, wherein the software instructions further configure the processor to:

    • identify a data transfer action between the VM application and the host application based on a portion of the trapped i/o events;
    • trigger the data transfer action via the interface of the native OS.

  4. The device of claim 1, wherein the software instructions issue a transaction ID for each transaction associated with the time-sensitive token.

  5. The device of claim 1, wherein the software instructions configure the processor to provide a user interface (UI) that enables the user to simultaneously interact with the VM and host applications.

Method of Interaction

  1. A method of enabling a user to interact with a native operating system (OS) running on a host device and a virtual machine running on top of the native OS, comprising:
    • rendering, by a virtual machine, a VM application running on top of the virtual machine;
    • negotiating authentication of the user with a host application utilizing the user credential information;
    • generating a security token when the virtual machine accepts user credential information;
    • passing data between the VM application and the host application using the generated security token as a function of the trapped i/o events.

Figures

  • Figure 1: Private, portable encryption and authentication service module (PPEASM) in a device communicating with applications in a host computer.
  • Figure 2: PPEASM in a host computer communicating with applications.
  • Figure 3: PPEASM in a host computer communicating with applications in a third-party system.
  • Figure 4: Application with a client interface to interact with PPEASM.