This disclosure relates generally to data processing and, more specifically, to biometric verification of a human Internet user.
The approaches described in this section could be pursued but are not necessarily approaches that have previously been conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.
With the development of the Internet, more and more resources and services are available online. A user can use a web browser to access these resources and services. However, the convenience that the Internet brings comes with some security challenges. There are a great number of malicious software programs that imitate valid client requests. Such malicious software can even perform distributed denial of service attacks (DDoS) to make machine or network resources unavailable to their intended users.
In order to address these problems, mitigation techniques have been used to determine whether the client requests are valid. For example, higher level challenge-response type implementations are aimed toward determining the authenticity of a requester. A SYN cookie is a Transmission Control Protocol (TCP) level challenge response aimed towards detecting spoofed attacks. A Hypertext Transfer Protocol (HTTP) 302 redirect is a higher level challenge response aimed at guaranteeing that the generator of a request is indeed capable of parsing basic HTTP responses. Another technique involves JavaScript redirect which is more powerful than HTTP redirect with multiple implementations. Unless the requester is indeed a browser, with a full java interpreter, it will not be able to follow the Java redirect.
The problem with the above techniques is that they do not involve human detection; rather they are browser detection techniques. Today's Internet bots are not implementing attacks over raw sockets; instead they just link with the browser Application Programming Interface (API) library, and so any request coming from the Internet bots is actually passing through a genuine browser library, thus also having inherent support for 302 redirect as well as JavaScript capabilities.
Other known techniques to differentiate legitimate, user-initiated, web requests from spoofed malicious request include a Completely Automated Public Turing test to tell Computers and Humans Apart (CAPTCHA). But the problem with CAPTCHA is that it is very intrusive, complicated to implement for multi-language support, and does not provide the key benefit of DDoS mitigation, which is keeping the site up and running without the legitimate users ever knowing that there is an ongoing attack being mitigated.
Thus, the existing solutions are associated with various disadvantages and more efficient, non-intrusive, transparent methods are desirable.
This summary is provided to introduce a selection of concepts in a simplified form that are further described in the Detailed Description below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
The present disclosure is related to biometric verification of a human Internet user. Specifically, a method for biometric verification of a human Internet user includes receiving, from a client machine, a web request for a service. The method further includes receiving environmental parameters associated with the client machine. Upon receiving the environmental parameters, the method proceeds with determining whether the environmental parameters are indicative of the human Internet user. Based on the determination, the service is selectively provided in response to the web request.
According to another approach of the present disclosure, a system for biometric verification of a human Internet user is provided. The system includes a processor. The processor is configured to receive, from a client machine, a web request for a service. The processor is further configured to receive environmental parameters associated with the client machine and determine whether the environmental parameters are indicative of the human Internet user. The system further includes a traffic classification engine. Based on the determination that the environmental parameters are indicative of the human Internet user, the processor selectively provides the service in response to the web request.
In further example embodiments of the present disclosure, the method steps are stored on a machine-readable medium including instructions, which when implemented by one or more processors perform the recited steps. In yet further example embodiments, hardware systems, or devices can be adapted to perform the recited steps. Other features, examples, and embodiments are described below.
Embodiments are illustrated by way of example, and not by limitation, in the figures of the accompanying drawings, in which like references indicate similar elements.
The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show illustrations in accordance with example embodiments. These example embodiments, which are also referred to herein as “examples,” are described in enough detail to enable those skilled in the art to practice the present subject matter. The embodiments can be combined, other embodiments can be utilized, or structural, logical, and electrical changes can be made without departing from the scope of what is claimed. The following detailed description is therefore not to be taken in a limiting sense, and the scope is defined by the appended claims and their equivalents. In this document, the terms “a” and “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a nonexclusive “or,” such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated.
The present technology enables differentiating between legitimate, user-initiated web requests and malicious requests masquerading as legitimate requests. To enable such differentiation, non-intrusive, transparent methods are used to determine whether a human client is initiating the request. The present technology is implemented by obtaining environmental data from the endpoint client machine (this data can be machine-dependent). The environmental data is analyzed for cues indicating whether the request comes from an Internet bot or a human client.
Some embodiments of the present technology allow recording data associated with an input device, such as, for example, a computer mouse. The web browser can send the recorded data to a web server to validate that the data is indicative of a human client. Using the present technology, when a web request for a service is received from a client machine, environmental parameters associated with the client machine are analyzed and a determination is made as to whether a human client is involved. For example, it can be determined whether the web browser is actually running in the foreground, and not merely as a background task. Furthermore, it can be determined whether the web browser has the mouse focus.
Examples of the environmental parameters that can be collected from the client machine include a list of running processes, identity of the process that has an active window handle, mouse movement (human clients tend to move the mouse while waiting for a page to load), keystrokes, and various types of gestures/touches on touchscreen-based devices, as well as information collected from other types of available sensors (for example face detection can be used if a camera is available).
In one example embodiment, the environmental parameters are extracted using an API associated with the client machine. The API is used to determine that a mouse associated with the client machine has a mouse pointer on top of an active window. In certain embodiments, the API is used to access processes associated with the client machine and identify a process that has an active handle, thus determining whether the web page has a focus of the mouse.
In one example embodiment, a script or other executable code is embedded in a webpage being served to the client machine and executed when a browser application gets the focus of the mouse. In one example embodiment, a Macromedia Flash component, such as an ActionScript, can be executed when a browser application gets the focus.
In an alternative embodiment, a Hypertext Markup Language (HTML) frame is inserted into a webpage being served to the client machine, and the mouse movements over the HTML frame are analyzed.
The embodiments disclosed herein can be implemented using a variety of technologies. For example, the methods described herein can be implemented in software executing on a computer system or in hardware utilizing either a combination of microprocessors or other specially designed application-specific integrated circuits (ASICs), programmable logic devices, or various combinations thereof. In particular, the methods described herein can be implemented by a series of computer-executable instructions residing on a storage medium such as a disk drive, or computer-readable medium. It should be noted that methods disclosed herein can be implemented by a computer (e.g., a desktop computer, a tablet computer, a laptop computer, and a server), game console, handheld gaming device, cellular phone, smart phone, smart television system, and so forth.
Referring now to the drawings,
The network 140 can include the Internet or any other network capable of communicating data between devices. Suitable networks can include or interface with any one or more of, for instance, a local intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a MAN (Metropolitan Area Network), a virtual private network (VPN), a storage area network (SAN), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3, E1 or E3 line, Digital Data Service (DDS) connection, DSL (Digital Subscriber Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34 or V.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or an FDDI (Fiber Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connection. Furthermore, communications can also include links to any of a variety of wireless networks, including WAP (Wireless Application Protocol), GPRS (General Packet Radio Service), GSM (Global System for Mobile Communication), CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access), cellular phone networks, GPS (Global Positioning System), CDPD (cellular digital packet data), RIM (Research in Motion, Limited) duplex paging network, Bluetooth radio, or an IEEE 802.11-based radio frequency network. The network 140 can further include or interface with any one or more of an RS-232 serial connection, an IEEE-1394 (Firewire) connection, a Fiber Channel connection, an IrDA (infrared) port, a SCSI (Small Computer Systems Interface) connection, a USB (Universal Serial Bus) connection or other wired or wireless, digital or analog interface or connection, mesh or Digi® networking. The network 140 can include a network of data processing nodes that are interconnected for the purpose of data communication. The network 140 can include a Software-defined Network (SDN). The SDN can include one or more of the above network types. Generally, the network 140 can include a number of similar or dissimilar devices connected together by a transport medium enabling communication between the devices by using a predefined protocol. Those skilled in the art will recognize that the present disclosure can be practiced within a variety of network configuration environments and on a variety of computing devices.
The client machine 120 can include a desktop personal computer (PC), workstation, laptop, personal digital assistant (PDA), cell phone, or any other computing device capable of interfacing directly or indirectly to the Internet. The client machine can run a browsing program, such as Microsoft's Internet Explorer™ browser, Netscape Navigator™ browser, Mozilla Firefox™ browser, Opera™ browser, or a Wireless Application Protocol (WAP)-enabled browser in the case of a cellphone, PDA, or other wireless device, allowing the user 110 of the client machine to view web pages available from the web servers 150 over the Internet.
The client machine 120 can include one or more user interface devices that are usually manipulated or controlled by a human, such as a keyboard, mouse, touch screen, pen, or the like, for interacting with a graphical user interface (GUI) provided by the web browser on a display (e.g., monitor screen, Liquid-crystal Display LCD display, and so forth), in conjunction with pages, forms, and other information provided by the web server 150. It should be understood that other networks can be used instead of or in addition to the Internet.
The method 200 can commence with receiving, from a client machine, a web request for a service at operation 205. At operation 210, environmental parameters associated with the client machine are received. For example, when a user makes a web request, the web browser collects the environmental parameters associated with the user's client machine. The environmental parameters can include mouse movements, keystrokes, and processes running on the client machine. The environmental parameters can be extracted using an API associated with the client machine. For example the API can be used to determine that a mouse associated with the client machine has a mouse pointer on top of an active window. The API can be also used to access processes running on the client machine to identify a process that has an active window handle and determine whether a webpage has the focus of the mouse.
The method 200 can continue with determining whether the environmental parameters are indicative of the human Internet user at operation 215. For example, an active browser window of the client machine, a specific pattern of mouse movement and keystrokes, and/or gestures/touches applied to touchscreen devices can be indicative of the human Internet user.
At operation 220, in response to the web request, the service is selectively provided based on the determination performed in step 215. In an example embodiment, the method 200 can include inserting a HTML frame into a webpage being served to the client machine, capturing mouse movement of a mouse associated with the client machine, and determining that the mouse is moving over the HTML frame
In an example embodiment, the method 200 includes providing a biometric challenge to the human Internet user, receiving a response to the biometric challenge and, based on the response, selectively providing the service in response to the web request. The biometric challenge includes a gesture, a touch, a facial expression, and the like. In an example embodiment, the method 200 includes inserting a script into a webpage being served to the client machine, capturing mouse movement of a mouse associated with the client machine, and determining that the mouse is moving over the webpage.
In an example embodiment, the method 200 includes inserting a binary into a webpage being served to the client machine, capturing mouse movement of a mouse associated with the client machine, and determining that the mouse is moving over the webpage. In an example embodiment, the method 200 includes activating a camera associated with the client machine, detecting a face associated with the human Internet user and, based on the detection, selectively providing the service in response to the web request.
In one example embodiment, the processor 305 is configured to receive, from a client machine, a web request for a service. The web request can come from an Internet bot or a human Internet user. In one example embodiment, the processor 305 can be further configured to receive environmental parameters associated with the client machine. The environmental parameters can refer to an active browser on the client machine or a mouse pointer on top of an active browser window. The environmental parameters include user operation behavior with respect to a webpage, such as mouse movements, using keyboard for data entry, a process running on the client machine, and so forth. For instance, mouse operation data can include information on coordinates of a cursor, temporal information associated with mouse clicks, and a number of mouse clicks. Keyboard operation data can include key information, key temporal information, and a number of clicks. The environmental parameters can be extracted using an API associated with the client machine.
In one example embodiment, the active browser window is detected by accessing processes associated with the client machine using the API, identifying a process that has an active window handle, and determining whether the webpage has a focus of the mouse. In one example embodiment, the mouse operation is determined by inserting an HTML frame into a webpage being served to the client machine and capturing the movement of the mouse associated with the client machine.
In one example embodiment, the mouse operation is determined by inserting a script into the webpage served to the client machine and capturing the movement of the mouse associated with the client machine. In one example embodiment, the mouse operation is determined by inserting a binary into the webpage served to the client machine and capturing the movement of the mouse associated with the client machine.
In one example embodiment, the processor 305 is further configured to determine whether the environmental parameters are indicative of the human client. The recorded environmental parameters are analyzed to determine whether they are indicative of a behavior associated with a human client. The processor 305 can determine whether the request is indeed generated by a human interacting with an application running on the client machine. Alternatively, the processor 305 can determine that one or more bots are running on the client machine and can ignore requests received from the client machine or discontinue serving the client machine.
In one example embodiment, the user 405 can be provided with a biometric challenge, such as a gesture, a touch, a facial expression, and the like. For example, the user 405 can be prompted to touch a screen or make a sound. The user 405 can be prompted to perform other actions (for example, smile or frown) to confirm that the user is a human. In one example embodiment, the system for biometric verification of a human Internet user 420 can determine that the user 405 has successfully completed the biometric challenge within a predetermined amount of time.
In one example embodiment, the system for biometric verification of a human Internet user 420 can receive, via a network 425, a response to the biometric challenge, and based on the response, selectively provide the service. In some embodiments, the response can include a notification that a human presence has been verified. In one example embodiment, a determination can be made that no human presence exists.
The example computer system 500 includes a processor or multiple processors 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory 506 and a static memory 508, which communicate with each other via a bus 510. The computer system 500 can further include a video display unit 510 (e.g., a LCD or a cathode ray tube (CRT)). The computer system 500 can also include an alphanumeric input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), a disk drive unit 504, a signal generation device 528 (e.g., a speaker), and a network interface device 512.
The disk drive unit 504 includes a non-transitory computer-readable medium 520, on which is stored one or more sets of instructions and data structures (e.g., instructions 522) embodying or utilized by any one or more of the methodologies or functions described herein. The instructions 522 can also reside, completely or at least partially, within the main memory 506 and/or within the processors 502 during execution thereof by the computer system 500. The main memory 506 and the processors 502 can also constitute machine-readable media.
The instructions 522 can further be transmitted or received over a network 526 via the network interface device 512 utilizing any one of a number of well-known transfer protocols (e.g., HTTP).
In some embodiments, the computer system 500 can be implemented as a cloud-based computing environment, such as a virtual machine operating within a computing cloud. In other embodiments, the computer system 500 can itself include a cloud-based computing environment, where the functionalities of the computer system 500 are executed in a distributed fashion. Thus, the computer system 500, when configured as a computing cloud, can include pluralities of computing devices in various forms, as will be described in greater detail below.
In general, a cloud-based computing environment is a resource that typically combines the computational power of a large grouping of processors (such as within web servers) and/or that combines the storage capacity of a large grouping of computer memories or storage devices. Systems that provide cloud-based resources can be utilized exclusively by their owners, or such systems can be accessible to outside users who deploy applications within the computing infrastructure to obtain the benefit of large computational or storage resources.
The cloud can be formed, for example, by a network of web servers that include a plurality of computing devices, such as the computing device 120, with each server (or at least a plurality thereof) providing processor and/or storage resources. These servers can manage workloads provided by multiple users (e.g., cloud resource customers or other users). Typically, each user places workload demands upon the cloud that vary in real-time, sometimes dramatically. The nature and extent of these variations typically depends on the type of business associated with the user.
It is noteworthy that any hardware platform suitable for performing the processing described herein is suitable for use with the technology. The terms “computer-readable storage medium” and “computer-readable storage media” as used herein refer to any medium or media that participate in providing instructions to a CPU for execution. Such media can take many forms, including, but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as a fixed disk. Volatile media include dynamic memory, such as system Random Access Memory (RAM). Transmission media include coaxial cables, copper wire, and fiber optics, among others, including the wires that include one embodiment of a bus. Transmission media can also take the form of acoustic or light waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, any other physical medium with patterns of marks or holes, a RAM, a PROM, an EPROM, an EEPROM, a FLASHEPROM, any other memory chip or data exchange adapter, a carrier wave, or any other medium from which a computer can read.
Various forms of computer-readable media can be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU.
Computer program code for carrying out operations for aspects of the present technology can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a LAN or a WAN, or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).
The corresponding structures, materials, acts, and equivalents of all means or steps plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present technology has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. Exemplary embodiments were chosen and described in order to best explain the principles of the present technology and its practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Aspects of the present technology are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions can also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
Thus, methods and systems for biometric verification of a human Internet user are disclosed. Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes can be made to these example embodiments without departing from the broader spirit and scope of the present application. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Number | Name | Date | Kind |
---|---|---|---|
5541994 | Tomko et al. | Jul 1996 | A |
5712912 | Tomko et al. | Jan 1998 | A |
5737420 | Tomko et al. | Apr 1998 | A |
5757916 | MacDoran et al. | May 1998 | A |
5832091 | Tomko et al. | Nov 1998 | A |
5991408 | Pearson et al. | Nov 1999 | A |
6035398 | Bjorn | Mar 2000 | A |
6167517 | Gilchrist et al. | Dec 2000 | A |
6182146 | Graham-Cumming, Jr. | Jan 2001 | B1 |
6182221 | Hsu et al. | Jan 2001 | B1 |
6219793 | Li et al. | Apr 2001 | B1 |
6219794 | Soutar et al. | Apr 2001 | B1 |
6310966 | Dulude et al. | Oct 2001 | B1 |
6317834 | Gennaro et al. | Nov 2001 | B1 |
6490624 | Sampson et al. | Dec 2002 | B1 |
6507912 | Matyas, Jr. et al. | Jan 2003 | B1 |
6714931 | Papierniak et al. | Mar 2004 | B1 |
6748084 | Gau et al. | Jun 2004 | B1 |
6901145 | Bohannon et al. | May 2005 | B1 |
6950651 | Seligmann | Sep 2005 | B2 |
7095852 | Wack et al. | Aug 2006 | B2 |
7133916 | Schunemann | Nov 2006 | B2 |
7155514 | Milford | Dec 2006 | B1 |
7237267 | Rayes et al. | Jun 2007 | B2 |
7360237 | Engle et al. | Apr 2008 | B2 |
7376969 | Njemanze et al. | May 2008 | B1 |
7480934 | Chan et al. | Jan 2009 | B2 |
7484089 | Kogen et al. | Jan 2009 | B1 |
7551574 | Peden, II et al. | Jun 2009 | B1 |
7552126 | Chen et al. | Jun 2009 | B2 |
7613829 | Alve | Nov 2009 | B2 |
7647635 | Chen et al. | Jan 2010 | B2 |
7653633 | Villella et al. | Jan 2010 | B2 |
7716378 | Chen et al. | May 2010 | B2 |
7804956 | Chang et al. | Sep 2010 | B2 |
7970934 | Patel | Jun 2011 | B1 |
7979585 | Chen et al. | Jul 2011 | B2 |
8104091 | Qin et al. | Jan 2012 | B2 |
8122152 | Chittenden et al. | Feb 2012 | B2 |
8151322 | Chen et al. | Apr 2012 | B2 |
8191106 | Choyi et al. | May 2012 | B2 |
8312507 | Chen et al. | Nov 2012 | B2 |
8423676 | Chen et al. | Apr 2013 | B2 |
8584199 | Chen et al. | Nov 2013 | B1 |
8595383 | Chen et al. | Nov 2013 | B2 |
8595791 | Chen et al. | Nov 2013 | B1 |
8782751 | Chen et al. | Jul 2014 | B2 |
8813180 | Chen et al. | Aug 2014 | B1 |
8826372 | Chen et al. | Sep 2014 | B1 |
8868765 | Chen et al. | Oct 2014 | B1 |
9060003 | Wang et al. | Jun 2015 | B2 |
9076027 | Miura et al. | Jul 2015 | B2 |
9122853 | Thompson | Sep 2015 | B2 |
9184921 | Novak | Nov 2015 | B2 |
9202105 | Wang | Dec 2015 | B1 |
9219751 | Chen et al. | Dec 2015 | B1 |
9253152 | Chen et al. | Feb 2016 | B1 |
9270705 | Chen et al. | Feb 2016 | B1 |
9294467 | Wang et al. | Mar 2016 | B2 |
9344421 | Chen et al. | May 2016 | B1 |
9398011 | Thompson | Jul 2016 | B2 |
9830599 | Khen | Nov 2017 | B1 |
9979747 | Bailey | May 2018 | B2 |
20010022558 | Karr, Jr. et al. | Sep 2001 | A1 |
20020036660 | Adan | Mar 2002 | A1 |
20020095587 | Doyle et al. | Jul 2002 | A1 |
20030023874 | Prokupets et al. | Jan 2003 | A1 |
20030101349 | Wang | May 2003 | A1 |
20030105859 | Garnett et al. | Jun 2003 | A1 |
20030140232 | De Lanauze | Jul 2003 | A1 |
20030140235 | Immega et al. | Jul 2003 | A1 |
20030142122 | Straut et al. | Jul 2003 | A1 |
20030191989 | O'Sullivan | Oct 2003 | A1 |
20030219121 | van Someren | Nov 2003 | A1 |
20040015243 | Mercredi et al. | Jan 2004 | A1 |
20040034784 | Fedronic et al. | Feb 2004 | A1 |
20040049687 | Orsini et al. | Mar 2004 | A1 |
20040059924 | Soto et al. | Mar 2004 | A1 |
20040081173 | Feather | Apr 2004 | A1 |
20040153553 | Chotkowski et al. | Aug 2004 | A1 |
20040167912 | Tsui et al. | Aug 2004 | A1 |
20040194114 | Spiegel | Sep 2004 | A1 |
20040224664 | Guo | Nov 2004 | A1 |
20040242200 | Maeoka et al. | Dec 2004 | A1 |
20040254919 | Giuseppini | Dec 2004 | A1 |
20040260651 | Chan et al. | Dec 2004 | A1 |
20050009520 | Herrero et al. | Jan 2005 | A1 |
20050010930 | Vaught | Jan 2005 | A1 |
20050018618 | Mualem et al. | Jan 2005 | A1 |
20050086502 | Rayes et al. | Apr 2005 | A1 |
20050089048 | Chittenden et al. | Apr 2005 | A1 |
20050108518 | Pandya | May 2005 | A1 |
20050114186 | Heinrich | May 2005 | A1 |
20050114321 | DeStefano et al. | May 2005 | A1 |
20050125276 | Rusu | Jun 2005 | A1 |
20050137981 | Maes | Jun 2005 | A1 |
20050144480 | Kim et al. | Jun 2005 | A1 |
20050182969 | Ginter et al. | Aug 2005 | A1 |
20050204162 | Rayes et al. | Sep 2005 | A1 |
20050283609 | Langford | Dec 2005 | A1 |
20060069687 | Cui et al. | Mar 2006 | A1 |
20060077926 | Rune | Apr 2006 | A1 |
20060083372 | Chang et al. | Apr 2006 | A1 |
20060165226 | Ernst et al. | Jul 2006 | A1 |
20060173977 | Ho et al. | Aug 2006 | A1 |
20060190997 | Mahajani et al. | Aug 2006 | A1 |
20060200441 | Nagatsuka | Sep 2006 | A1 |
20070011300 | Hollebeek et al. | Jan 2007 | A1 |
20070032247 | Shaffer et al. | Feb 2007 | A1 |
20070067441 | Pomerantz | Mar 2007 | A1 |
20070067838 | Bajko | Mar 2007 | A1 |
20070121560 | Edge | May 2007 | A1 |
20070156919 | Potti et al. | Jul 2007 | A1 |
20070179986 | Adam | Aug 2007 | A1 |
20070180101 | Chen et al. | Aug 2007 | A1 |
20070192849 | Golle | Aug 2007 | A1 |
20070195791 | Bosch et al. | Aug 2007 | A1 |
20070206746 | Andreasson et al. | Sep 2007 | A1 |
20070234061 | Teo | Oct 2007 | A1 |
20070239604 | O'Connell | Oct 2007 | A1 |
20070259673 | Willars et al. | Nov 2007 | A1 |
20070271598 | Chen et al. | Nov 2007 | A1 |
20070282855 | Chen et al. | Dec 2007 | A1 |
20070283141 | Pollutro et al. | Dec 2007 | A1 |
20070288247 | Mackay | Dec 2007 | A1 |
20070294209 | Strub et al. | Dec 2007 | A1 |
20080002684 | Kumazawa et al. | Jan 2008 | A1 |
20080080398 | Yasuie et al. | Apr 2008 | A1 |
20080104276 | Lahoti et al. | May 2008 | A1 |
20080109870 | Sherlock et al. | May 2008 | A1 |
20080109887 | Chen et al. | May 2008 | A1 |
20080130898 | Holtmanns et al. | Jun 2008 | A1 |
20080148167 | Russak | Jun 2008 | A1 |
20080148357 | Chen et al. | Jun 2008 | A1 |
20080189790 | Park | Aug 2008 | A1 |
20080229418 | Chen et al. | Sep 2008 | A1 |
20080263626 | Bainter et al. | Oct 2008 | A1 |
20090047952 | Giaretta et al. | Feb 2009 | A1 |
20090113294 | Sanghavi | Apr 2009 | A1 |
20090213763 | Dunsmore et al. | Aug 2009 | A1 |
20090292924 | Johnson | Nov 2009 | A1 |
20090299862 | Fan | Dec 2009 | A1 |
20100100725 | Ozzie | Apr 2010 | A1 |
20100153544 | Krassner | Jun 2010 | A1 |
20100159955 | Aerrabotu | Jun 2010 | A1 |
20100217819 | Chen et al. | Aug 2010 | A1 |
20100235880 | Chen et al. | Sep 2010 | A1 |
20110173280 | Ishikawa | Jul 2011 | A1 |
20110239289 | Wang et al. | Sep 2011 | A1 |
20120023558 | Rafiq | Jan 2012 | A1 |
20120084133 | Ross | Apr 2012 | A1 |
20120183270 | Greenblatt | Jul 2012 | A1 |
20120204236 | Chen et al. | Aug 2012 | A1 |
20120216266 | Wang et al. | Aug 2012 | A1 |
20120246737 | Paxton | Sep 2012 | A1 |
20120297190 | Shen | Nov 2012 | A1 |
20130036342 | Deo | Feb 2013 | A1 |
20130191908 | Klein | Jul 2013 | A1 |
20140059702 | Wang et al. | Feb 2014 | A1 |
20140082694 | Sanghavi | Mar 2014 | A1 |
20140096272 | Makofsky | Apr 2014 | A1 |
20140143149 | Aissi | May 2014 | A1 |
20140196143 | Fliderman | Jul 2014 | A1 |
20140229268 | Clapp | Aug 2014 | A1 |
20140250538 | Rapaport | Sep 2014 | A1 |
20140333415 | Kursun | Nov 2014 | A1 |
20140347479 | Givon | Nov 2014 | A1 |
20140380424 | Thompson | Dec 2014 | A1 |
20150128236 | Moscicki | May 2015 | A1 |
20150141076 | Libin et al. | May 2015 | A1 |
20150312237 | Wang et al. | Oct 2015 | A1 |
20150365410 | Thompson | Dec 2015 | A1 |
20160036778 | Chen et al. | Feb 2016 | A1 |
20160048662 | Arnoud | Feb 2016 | A1 |
20160050233 | Chen et al. | Feb 2016 | A1 |
20160105395 | Chen et al. | Apr 2016 | A1 |
20160105446 | Chen et al. | Apr 2016 | A1 |
20160182456 | Wang et al. | Jun 2016 | A1 |
20160323261 | Thompson | Nov 2016 | A1 |
20170034148 | Rapaport | Feb 2017 | A1 |
Number | Date | Country |
---|---|---|
1449618 | Oct 2003 | CN |
1725702 | Jan 2006 | CN |
101094225 | Dec 2007 | CN |
101361037 | Feb 2009 | CN |
101375253 | Feb 2009 | CN |
102098316 | Jun 2011 | CN |
102123156 | Jul 2011 | CN |
ZL 200780001795.6 | Jul 2011 | CN |
ZL 200780001775.9 | Sep 2011 | CN |
102918801 | Feb 2013 | CN |
ZL2011100683067 | Nov 2014 | CN |
102098316 | Sep 2015 | CN |
1770915 | Apr 2007 | EP |
1885096 | Feb 2008 | EP |
2577910 | Apr 2013 | EP |
1183569 | Dec 2013 | HK |
2013528330 | Jul 2013 | JP |
NI175810 | Apr 2003 | TW |
I249314 | Feb 2006 | TW |
0221788 | Mar 2002 | WO |
2008067013 | Jun 2008 | WO |
2008070248 | Jun 2008 | WO |
WO2011149796 | Dec 2011 | WO |
WO2014209660 | Dec 2014 | WO |
Entry |
---|
Alex Marandon, “How to build a web widget (using jQuery)—Alex Marandon”, Jun. 2010, https://web.archive.org/web/20100623004301/http://alexmarandon.com/articles/web_widget_jquery/. |
“How to Create a Rule in Outlook 2003” CreateaRule-Outlook2003.doc 031405 mad. |
WFLOGS, Dec. 15, 2002, http://web.archive.org/web/20021205151706/http://www.wallfire.org/wflogs/wflogs.8.html. |
Microsoft Windows XP—Filter events in an event log, Jul. 2, 2004, http://web.archive.org/web/20040702070538/http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/nt_filteringevents_how_ev.mspx. |
The Cable Guy: Windows 2000 Routing and Remote Access Service—Jun. 2001, Jul. 22, 2004, http://web.archive.org/web/20040722111534/http://www.microsoft.com/technet/community/columns/cableguy/cg0601.mspx. |
Monrose et al., “Cryptographic Key Generation from Voice,” Proceedings of the 2001 IEEE Symposium on Security and Privacy, pp. 202-213, May 2001. |
Shamir, “How to share a secret,” Communications of the ACM, vol. 22, No. 11, pp. 612-613, Nov. 1979. |
Jermyn et al., “The Design and Analysis of Graphical Passwords,” Aug. 1999; Usenix; 15 pp. |
Soutar et al.; “Biometric Encryption™”; 1999; pp. 1-28. |
Duda et al., “Pattern Classification,” Second Edition; 2001; pp. 117-121. |
Zhang et al.; “Personal Authentication Based on Generalized Symmetric Max Minimal Distance in Subspace;” 2003; IEEE; pp. 245-248. |
Okada et al.; “An Optimal Orthonormal System for Discriminant Analysis”; 1985; Pattern Recognition, vol. 18, No. 2; pp. 139-144. |
Chang et al.; “Biometrics-Based Cryptographic Key Generation;” 2004; IEEE; 5 pp. |
Zhang et al.; “Optimal Thresholding for Key Generation Based on Biometrics;” 2004; IEEE; 5 pp. |