The invention relates to portable desktops, and more particularly to the recognition of hardware of a host of a portable desktop.
A portable desktop allows a user to utilize the hardware of a host computer system and thus provides a portable computing environment. A portable desktop may be physically embodied in portable storage media and more often is embodied in a portable device which includes processing hardware, storage, and input/output (I/O) hardware for communication with the host system and/or authentication by a user. The portable computing environment, hereinafter referred to as the portable desktop, is portable in the sense that any changes made to data files, software, settings, user preferences, or any other configuration or aspect of that computing environment made during a session on the host computer system, which are intended to be permanent, are stored in the portable device such that the portable desktop has continuity across multiple sessions. The appearance, functionality, content and/or configuration of the portable desktop should also be independent of any changes made to any particular host computer system, as well as be independent of the particular host computer system used for any session. Portability, therefore, depends upon the ability of the portable desktop device to function with different host computer systems.
One type of portable desktop device is a USB memory device used to transport and store the portable desktop data. In a typical situation, the device is inserted into a host computer USB port from which it derives power. The host computer provides power to the device until the host computer is powered down or until the device is removed from the USB port thereof. From powering of the USB memory device, security features thereon are enabled. Once accessed, the device acts to support portable desktop functionality. Typically, this involves rebooting the host computer or powering it up from an unpowered state. Further typically, the portable desktop environment is discontinued when the host computer is powered down or when the USB memory device is removed from the USB port thereof.
A known security problem exists when a secure device is kept in a powered state once use of the device is completed. For example, if a USB hub were introduced between the host computer and USB devices coupled therewith, and the USB hub were powered, then a USB device would retain a power on state even when the hub was removed from the host computer. When this happens, it is often the case that some of the security of the USB memory device remains disabled as the device is already enabled for use; as such, the device is still accessible differently from what was intended.
It would be advantageous for there to be a method or system for supporting secure portable desktops that overcomes security and/or other limitations of known portable desktop approaches.
According to one aspect, the invention provides for a method comprising: coupling a portable desktop device comprising portable desktop data stored therein to a host computer; enabling access to the portable desktop data; executing a portable desktop application received from the portable desktop device on the host computer system; at intervals transmitting from the host computer system to the portable desktop device a beat signal indicating a presence and operability of the host computer; and, when the portable desktop device other than receives a beat signal at the interval, disabling access to the portable desktop data.
In accordance with another embodiment of the invention there is provided a portable desktop device comprising: I/O hardware for coupling the portable desktop device to a host computer system; memory storage comprising: a portable desktop storage block comprising a portable desktop O/S; and a processor for during use receiving a beat signal from the host computer at intervals and for, in the absence of receiving a beat signal at the interval preventing access to the memory storage.
In accordance with another embodiment of the invention there is provided a portable desktop device comprising: an input output port for coupling the portable desktop device to a host computer system; memory storage comprising: a portable desktop storage block comprising a portable desktop O/S; and a processor for during use providing to the host computer system at second intervals a challenge signal and for, in response thereto receiving a beat signal from the host computer at first intervals and for, in the absence of receiving the beat signal at the first interval preventing access to the memory storage.
The features and advantages of the invention will become more apparent from the following detailed description of the preferred embodiment(s) with reference to the attached figures, wherein:
It is noted that in the attached figures, like features bear similar labels.
Referring to
The portable desktop device 1000 is shown connected to its host computer system 1900. The host computer system 1900 is coupled to a number of hardware devices 1950. Some of the hardware devices 1950 are external to the host computer system 1900 while others are internal hardware devices. For the purposes of the invention, no distinction is made between an external or an internal hardware device, and as such hardware devices 1950 includes any and all hardware connected to and controlled by the host computer system 1900.
The host computer system 1900 is any computer system capable of interfacing with the portable desktop device 1000. The portable desktop device 1000 is in the form of a powered peripheral device capable of interfacing with the host computer system 1900 and in some embodiments is a universal serial bus (USB) storage and processing device.
The portable desktop device 1000 is connected to the host computer system 1900 by input/output (I/O) hardware 1300. In addition to I/O hardware 1300, the portable desktop device 1000 comprises a processor 1100, authentication hardware 1400, and memory storage 1200. The processor 1100 is coupled to the I/O hardware 1300, the authentication hardware 1400, and the memory storage 1200. The authentication hardware 1400 may comprise biometric authentication hardware such as a fingerprint, retinal, or other scanner or may comprise some other input hardware for receiving a bar code, encryption key, combination, password or other authentication information. Alternatively, the authentication hardware forms part of the host computer system 1900.
The memory storage 1200 comprises a boot process 1220 application data storage block including application storage for a security process 1222 and a portable desktop storage block 1224. The portable desktop storage block 1224 comprises a portable desktop O/S 1242. The portable desktop storage block 1224 also includes a storage block for the portable desktop user data 1244. The portable desktop O/S 1242 may include user data in the form of O/S preferences or configuration settings for a user. The portable desktop user data 1244 may include user installed applications which do not form part of the O/S along with preferences or configuration settings thereof, as well as any other data files associated with the portable desktop the user may have. In embodiments for which multiple users are supported, per user files, preferences or configuration settings are stored in the portable desktop O/S 1242 and multiple instances of portable desktop user data 1244, one for each user, are present in the portable desktop storage block 1224 (not shown). Optionally, in other embodiments, further portable desktop storage blocks are present in the memory storage 1200, each having its own portable desktop O/S and portable desktop user data block. This allows for further separation among users and/or groups of users, insuring not only that data and functions of each portable desktop environment are separated but that each user or group of users that can access one portable desktop environment have no knowledge of there being other users who use other desktop environments. A second portable desktop storage block 1250 is shown in dashed lines in
Referring also to
In some embodiments, hot-plugging the portable desktop device 1000 will trigger the host computer system 1900 to detect the portable desktop device 1000 and prompt the user to confirm whether or not the system should be restarted in order to commence the portable desktop session.
During a boot of the host computer system 1900 from the portable desktop device 1000, the host computer system 1900 requests, through the I/O hardware 1300, a bootable process, for example the portable desktop O/S within data storage of the memory storage 1200 and executes the portable desktop O/S. Typically, the portable desktop device 1000 is initially secured. Prior to supporting a portable desktop application, the portable desktop device 1000 typically requires user authentication. For example, when the portable desktop device 1000 comprises a fingerprint platen, a fingerprint of a user is authenticated at 203 to “unlock” the portable desktop data at 204. Alternatively, another form of user authentication is performed. Further alternatively, authentication is performed using input/output devices of the host computer system 1900.
After user authentication and once the portable desktop device 1000 is “unlocked,” for example during execution of the portable desktop O/S at 205, a signal is transmitted at 206 from the host computer to the portable desktop device at intervals to indicate that the host computer is still active. The signal transmitted is optionally a beat signal sent every so often to indicate activity. For example the beat signal is a periodic signal. Alternatively, the beat signal is transmitted at time intervals that vary in a fashion known to the portable desktop device 1000. Further alternatively, a content of the beat signal varies in a fashion known to the portable desktop device 1000. Alternatively, the beat signal is a response to a challenge provided from the portable desktop device to the host computer. Further optionally, the beat signal comprises a response to a challenge issued between beats or to another previously issued challenge. When the beat signal is received at the portable desktop device, the device continues normal operation at 207.
In such an embodiment, removal of the portable desktop device connection to the host computer system while maintaining power to the device is detectable as a potential security threat since the beat signal is not provided to the portable desktop device 1000 during the disruption.
When a beat signal is other than detected by the portable desktop device 1000, the portable desktop device is locked at 209 and access thereto is prevented absent a further user authentication operation.
Timing of the beat signal is preferably significantly less than the amount of time required to disconnect and reconnect the portable desktop device. For example, the timing is on the order of a few milliseconds. Further preferably, the content of the beat signal is not easily copied or determined in order to prevent another device from mimicking the beat signal once the host computer system is disconnected.
Referring to
Referring to
Referring to
Referring to
The embodiments presented are exemplary only and persons skilled in the art would appreciate that variations to the embodiments described above may be made without departing from the spirit of the invention. The scope of the invention is solely defined by the appended claims.
This application is a U.S. national stage application under 35 U.S.C. 371 of PCT Patent Application No. PCT/CA2010/001810, filed Nov. 15, 2010, entitled “Device and Method for Verifying Connectivity,” which claims priority to U.S. Provisional Application No. 61/260,875, filed Nov. 13, 2009, the contents of both of which are hereby incorporated in their entirety by reference.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/CA2010/001810 | 11/15/2010 | WO | 00 | 5/31/2012 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2011/057409 | 5/19/2011 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6249868 | Sherman et al. | Jun 2001 | B1 |
6321335 | Chu | Nov 2001 | B1 |
6370649 | Angelo et al. | Apr 2002 | B1 |
6718463 | Malik | Apr 2004 | B1 |
6754817 | Khatri et al. | Jun 2004 | B2 |
7069433 | Henry et al. | Jun 2006 | B1 |
7293166 | Nguyen et al. | Nov 2007 | B2 |
7363363 | Dal Canto et al. | Apr 2008 | B2 |
7484089 | Kogen et al. | Jan 2009 | B1 |
7512512 | Foote et al. | Mar 2009 | B2 |
7555568 | Huang | Jun 2009 | B2 |
7865573 | Tyhurst et al. | Jan 2011 | B2 |
7975287 | Hung | Jul 2011 | B2 |
8024790 | Zhao et al. | Sep 2011 | B2 |
8065676 | Sahai et al. | Nov 2011 | B1 |
8104088 | Khilnani et al. | Jan 2012 | B2 |
8140869 | Song et al. | Mar 2012 | B2 |
8176153 | Bose | May 2012 | B2 |
20020087877 | Grawrock | Jul 2002 | A1 |
20020188565 | Nakamura et al. | Dec 2002 | A1 |
20030023839 | Burkhardt et al. | Jan 2003 | A1 |
20030101246 | Lahti | May 2003 | A1 |
20030195950 | Huang et al. | Oct 2003 | A1 |
20030216136 | McBrearty et al. | Nov 2003 | A1 |
20040019778 | Gere | Jan 2004 | A1 |
20040095382 | Fisher et al. | May 2004 | A1 |
20040103288 | Ziv et al. | May 2004 | A1 |
20050193188 | Huang | Sep 2005 | A1 |
20050235045 | Narayanaswami et al. | Oct 2005 | A1 |
20060080540 | Arnon et al. | Apr 2006 | A1 |
20060085845 | Davis et al. | Apr 2006 | A1 |
20060130004 | Hughes et al. | Jun 2006 | A1 |
20060200679 | Hawk et al. | Sep 2006 | A1 |
20070016743 | Jevans | Jan 2007 | A1 |
20070101118 | Raghunath et al. | May 2007 | A1 |
20070143837 | Azeez et al. | Jun 2007 | A1 |
20070300220 | Seliger et al. | Dec 2007 | A1 |
20080016005 | Owen et al. | Jan 2008 | A1 |
20080022393 | Waltermann et al. | Jan 2008 | A1 |
20080052528 | Poo et al. | Feb 2008 | A1 |
20080052770 | Ali et al. | Feb 2008 | A1 |
20080052776 | Prabhat et al. | Feb 2008 | A1 |
20080072289 | Aoki et al. | Mar 2008 | A1 |
20080172555 | Keenan | Jul 2008 | A1 |
20080215796 | Lam et al. | Sep 2008 | A1 |
20080293450 | Ryan et al. | Nov 2008 | A1 |
20090049307 | Lin | Feb 2009 | A1 |
20090132816 | Lee | May 2009 | A1 |
20090210794 | Pendse et al. | Aug 2009 | A1 |
20090260071 | Sadovsky et al. | Oct 2009 | A1 |
20090300710 | Chai et al. | Dec 2009 | A1 |
20090319782 | Lee | Dec 2009 | A1 |
20100036973 | Mardiks et al. | Feb 2010 | A1 |
20100098243 | Chopart | Apr 2010 | A1 |
20100251328 | Syed et al. | Sep 2010 | A1 |
20110078347 | Hamid | Mar 2011 | A1 |
20110078428 | Hamid | Mar 2011 | A1 |
20110078785 | Hamid | Mar 2011 | A1 |
20110078787 | Hamid | Mar 2011 | A1 |
Number | Date | Country |
---|---|---|
1 168 235 | Jan 2002 | EP |
2 420 198 | May 2006 | GB |
WO 9804967 | Feb 1998 | WO |
WO2007149671 | Dec 2007 | WO |
WO 2008122755 | Oct 2008 | WO |
WO 2011038502 | Apr 2011 | WO |
WO 2011038503 | Apr 2011 | WO |
WO 2011038504 | Apr 2011 | WO |
WO 2011038505 | Apr 2011 | WO |
WO 2011057409 | May 2011 | WO |
Entry |
---|
Kevin. “Review: IronKey Secure USB Flash Drive,” Oct. 3, 2007, p. 1-5. Retrieved from the Internet: <URL: http://www.geek.com/articles/gadgets/review-ironkey-secure-usb-flash-drive-2007103/> , retrieved on Nov. 15, 2012. |
Roudebush, Bob. “VThere—A Second Look”, retrieved Jul. 31, 2006 from <http://www.roudybob.net/?p=307> 4 pages. |
Number | Date | Country | |
---|---|---|---|
20120233358 A1 | Sep 2012 | US |
Number | Date | Country | |
---|---|---|---|
61260875 | Nov 2009 | US |