Configuring a secure network

Techniques are presented for configuring a networking device to provide secure wireless connectivity to one or more client devices. In one embodiment, a networking device is discovered that is within a wireless connectivity range from a first client device. The networking device is configured to provide wireless connectivity to the first client device. The first client device is configured to initiate a first wireless connection, without requiring a user to specify any network settings. The networking device is configured to authenticate a user to access a user interface for configuring the networking device, where the user is not authenticated based on any password.

TECHNICAL FIELD

Embodiments presented in this disclosure generally relate to the field of computer networks and, more particularly, to techniques for configuring secure networks.

BACKGROUND

Computing devices and computer networking have become an integral part of daily life in modern day society. Personal and business use of computing devices, such as laptops, personal computers, smartphones (i.e., cell phones offering advanced computing capabilities), tablets, personal digital assistants (PDAs), and the like, have exploded in recent years. In addition, other electronic devices such as printers, gaming devices, smart appliances, etc. have also surged in popularity. For example, a home may include one or more personal computers, a printing device, a gaming device shared by family members and smartphones owned by individual family members. Small businesses may provide personal computers and smartphones or PDAs for employees, in addition to printers shared by the employees.

Private local area networks (LANs) may be used to enhance the usefulness of computing devices and other electronic devices in homes and small business. In a LAN, devices may be linked together through a networking device, such as a router. The router may be connected to other private and public networks, such as the Internet. In such a configuration, the router facilitates communication by routing packets of data between the devices within the LAN and also to and from other devices in private and public networks outside the LAN. Thus, home users and small businesses may use the LANs to enable computing devices and other electronic devices to communicate both within and outside the private network.

DESCRIPTION

Overview

Embodiments of the invention provide a method, logic encoded in one or more tangible media, and system for performing an operation that includes discovering a networking device within a wireless connectivity range from a first client device. The operation also includes configuring the networking device to provide wireless connectivity according to network settings generated for the networking device. The operation also includes initiating, by the first client device and based on the network settings, a first wireless connection to the networking device. The first wireless connection is initiated to request, on behalf of a user, access to a user interface for configuring the networking device. The operation also includes, by the networking device and prior to granting access, authenticating the user requesting access.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Embodiments presented in this disclosure provide techniques for configuring a networking device, such as a wireless router, to provide secure wireless connectivity to one or more client devices. One embodiment provides a small flash memory device (referred to as a setup key) storing a network application. When a user connects the setup key to a client device, the client device executes the network application. In one embodiment, the setup key may be connected to the client device via a Universal Serial Bus (USB) port on the client device. The network application discovers and configures the networking device, using network settings generated for the networking device. The network settings may include a network identifier, a network password, and a wireless security protocol, and the like. Using the networking settings, the network application configures the client device to initiate a wireless connection to the configured networking device. The wireless connection is created without requiring the user to specify the network settings. The network application may store the network settings onto the setup key. The user may then connect the setup key to other devices, to configure other devices to connect to the wireless network provided by the configured networking device. Again, the client devices are configured to access the networking device without requiring the user to directly specify the network settings.

In one embodiment, the network application may also establish communication between the networking device and another network, such as the Internet. The networking device is further configured to authenticate a user to access a user interface for configuring the networking device. Rather than requiring the user to provide (and remember) a password, a user may be authenticated using information stored on the setup key. In some embodiments, the user is authenticated based on a digital certificate received from the networking application. Advantageously, by using the setup key, the user may configure a secure network more conveniently and/or efficiently at least in some cases. Should the user subsequently desire to further configure the networking device, the user may also access the user interface for configuring the networking device.

FIG. 1Ais an exemplary illustration of an overarching network system100configured to implement one or more aspects presented in the disclosure. The network system100comprises a smart network102, an external network110and an applet store116. The external network110may comprise the well-known Internet or any other data network system. The smart network102includes a smart network host device120configured to transmit network data packets between the external network110and connected devices within the smart network102, such as computer170and client devices130. Any technically feasible wireless or wired physical transport technology may be implemented to transmit the network data packets. The smart network host device120maintains a network state model178that represents the different entities and related services operating within the smart network102. For example, if client device130(0) implements a printer with an integrated scanner and flash memory reader, then the network state model178would include an entry for client device130(0), and related attributes for a printer service, scanner service and file (or block device) service. New devices register with the smart network host device120, which then updates the network state model178to include the new device.

A portal application172, residing within the computer170, is configured to access the network state model178to determine which client devices130are available within the smart network102, which services the client devices130provide, and to access and use the services. The portal application172may include one or more applets174, configured to extend functionality of the portal application172. A given applet174may be associated with a specific client device130and may facilitate specific usage models for the client device130via the extended functionality. When a new client device130registers with the smart network102, a most recent version of a corresponding applet174may not be available within the portal application172. However, the portal application172may retrieve the corresponding applet174or version of the corresponding applet174from the applet store116.

The applet store116is configured to facilitate access to applets174by the portal application172. The applet store116provides storage for applets174corresponding to client devices130and makes the applets174available for download to the portal application172via the external network110. In one embodiment, the applet store116occupies a well-known location, such as a universal resource locator (URL) associated with the external network110. Any technically feasible technique may be used to identify a particular applet174as corresponding to a particular client device130. Furthermore, any technically feasible technique may be used to download the particular applet174an incorporate the functionality of the applet174to the portal172.

FIG. 1Billustrates the smart home network102ofFIG. 1A, according to one example embodiment of the present disclosure. As shown, the smart network102comprises a smart network host device120, one or more client devices130and a wide area network (WAN) interface device112, coupled to the external network110ofFIG. 1A. The WAN interface device112may implement a cable modem, digital subscriber line (DSL) modem, fiber to the home interface, or any other technically feasible device that provides digital network connectivity to the external network110. The WAN interface device112is coupled to the smart network host device120via a network interface118. In one embodiment, the network interface118implements the well-known Ethernet standard.

The smart network host device120implements a wireless network interface coupled to antenna122, which is configured to convert electrical signals to electromagnetic signals for transmitting data packets, and electromagnetic signals to electrical signals for receiving data packets. The antenna122may comprise plural independent radiator structures, each having a separate radiation pattern for implementing spatial multiplexing. In one embodiment, the wireless network interface implements one or more well-known standards, such as the Institute of Electrical and Electronics Engineers (IEEE) standard 802.11, which defines a system for wireless local area networking. The antenna122is configured establish wireless client links134to antennas132coupled to corresponding client devices130. The smart network host device120implements layer2forwarding (bridging) for wireless data packets forwarded among client devices130as well as internet protocol (IP) layer3routing between an IP domain associated with the smart network102and the external network110. In this configuration, the smart network host device120provides related services and protocols, such as dynamic host configuration protocol (DHCP), network address translation (NAT), and the like.

The smart network host device120acts as a central authentication authority for the smart network102and implements authentication services for devices registering with the smart network102. In one embodiment, authentication is implemented via Identification (ID) devices136that are uniquely paired with corresponding client devices130. For example, client device130(0) may be uniquely paired with ID device136(0) by a manufacturer of the client device130(0). An ID device136(0) is physically presented to the smart network host device120as an authentication credential to allow a client device130(0) paired to the ID device136(0) to join the smart network102. Furthermore, the client device130(0) is able to authenticate the smart network102as a trusted network by accessing credentials for the corresponding ID device136(0) specifically via the smart network102. In one embodiment, the ID devices136are implemented as near field radio frequency identification (RFID) tags. Each one of the RFID tags is configured to retain authentication credentials necessary to uniquely associate the one RFID tag with one instance of the client device130. In this way, an RFID tag may be paired with a given client device130. Persons skilled in the art will recognize that any technique may be implemented to generate and represent authentication credentials without departing the scope and spirit of the present invention. For example, in another embodiment, the ID devices136could be implemented as a physical token that includes a printed bar code on a face of the token. The bar code may encode authentication credentials for a corresponding client device130. In such an embodiment, the smart network host device120may include an optical scanner capable of reading the printed bar code from the physical token. In alternative embodiments, other forms of ID devices136may implement storage of the authentication credentials. For example, a universal serial bus (USB) storage device may be used to present authentication credentials to the smart network host device120for authenticating a related device, such as the computer170. In other alternative embodiments, a user may manually authenticate a client device130with the smart network host device120. For example, the user may log onto a management web page generated by the smart network host device120and manually enter authentication credentials, such as a printed code associated with the client device130.

In one usage scenario involving ID device136, the user wishes to add a new device, such as a smart network-enabled printer to the smart network102. The printer includes an ID device136implemented as an RFID tag that is paired to the printer. The user places the ID device136in close physical proximity to the smart network host device120, which is the able to read the ID device136and authenticate the printer. The printer registers with the smart network host device120and is then available for use by devices connected within the smart network102. Upon successfully reading the ID device136, the smart network host device120may indicate success to the user by flashing a light-emitting diode (LED), or by generating any technically feasible indication.

FIG. 1Cillustrates the smart home network102ofFIG. 1A, according to another example embodiment of the present disclosure. Here, the smart network102comprises a smart network host device120, a smart network extender device140, one or more client devices130and a wide area network (WAN) interface device112, coupled to the external network110ofFIG. 1A. The WAN interface device112, smart network host device120and one or more client devices130are configured to operate as previously described inFIG. 1B.

In addition to previously described functionality, the smart network host device120is also configured to detect one or more smart network extender devices140and to establish a bridge link128to each of the one or more smart network extender devices140. Each smart network extender device140is configured to act as a network bridge between a client device130and the smart network host device120. For example, client devices130(1) through130(N) may be physically located such that they are able to connect to the smart network extender device140, but not to the smart network host device120. Furthermore, the smart network extender device140is able to connect to the smart network host device120via bridge link128. Data packets transmitted by client devices130(1) through130(N) and destined to the external network110are received by the smart network extender device140and retransmitted by the smart network extender device140via bridge link128to the smart network host device120, which then forwards the data packets to the external network110. Similarly, data packets from the external network110that are destined to any of the client devices130(1) through130(N) are transmitted via bridge link128to the smart network extender device140, which retransmits the data packets via wireless client links134(1)-134(N). Persons skilled in the art will understand that wireless client links134(1)-134(N) may each be configured to operate on a separate channel or band, or a common channel or band. Furthermore, bridge link128may operate on a separate channel or band with respect to the wireless client links134.

In one embodiment, each smart network extender device140is paired to an ID device136, which is presented as an authentication credential to the smart network host device120to enable the smart network extender device140to participate within the smart network102.

FIG. 1Dillustrates the smart home network102ofFIG. 1A, according to yet another example embodiment of the present disclosure. Here, the smart network102comprises a smart network host device120, a smart network extender device140, one or more client devices130, a smart network connector device150and a wide area network (WAN) interface device112, coupled to the external network110ofFIG. 1A. The WAN interface device112, smart network extender device140and one or more client devices130are configured to operate as previously described inFIGS. 1B and 1C.

In this embodiment, the smart network host device120is configured to operate similarly with respect toFIGS. 1B and 1C. However, upon detecting the smart network connector device150, the smart network host device120is configured to operate as a bridge rather than a router, and the smart network connector device150is configured to operate as a router. A backhaul link158is established between the smart network host device120and the smart network connector device150.

Network data traffic between client device130(N) and the external network110traverses wireless client link134(N), bridge link128and backhaul link158. This network data traffic is also forwarded by smart network extender device140, smart network host device120and smart network connector device150. A client device130may connect directly to any one of the network extender device140, smart network host device120or smart network connector device150. As shown, client device130(0) is connected to smart network connector device150via wireless client link134(0), client device130(1) is connected to smart network host device120via wireless client link134(1) and client device130(N) is connected to smart network extender device140via wireless client link134(N).

In one embodiment, the smart network connector device150is paired to an ID device136, which is presented as an authentication credential to the smart network host device120to enable the smart network connector device150to participate within the smart network102. In an alternative embodiment, the smart network connector device150and the smart network host device120are paired during a manufacturing step, eliminating the need for a separate ID device136.

FIG. 1Eis a more detailed illustration of the smart network host device120ofFIG. 1A, according to one example embodiment of the present disclosure. As shown, the smart network host device120comprises a processor complex,160, a wireless network interface162, an ID device reader164, and a wired network interface166. An interconnect165is configured to transmit data among the processor complex160, wireless network interface162, ID device reader164, and wired network interface166. The wired network interface166is configured transmit data packets via network interface118, based on data received via the interconnect165. The wired network interface166is also configured to receive data packets from the network interface118and transmit contents of the received data packets to the processor complex160via the interconnect165. The wireless network interface162is configured to transmit data packets, based on data received via the interconnect165, to one or more network devices within range. The wireless network interface162is also configured to receive data packets from the one or more network devices and then transmit contents of the received packets to the processor complex160. The wireless network interface162is coupled to an antenna122.

The processor complex160comprises a central processing unit (CPU), non-volatile memory for storing persistent programs, program state, and configuration information, random access memory (RAM) for storing temporary or volatile data, and an interface to the interconnect165. In one embodiment, the processor complex160is configured to execute an operating system and applications that provide routing services. The routing services may include, for example, data packet forwarding between the network interface118and the wireless network interface162. The packet forwarding services may include, without limitation, bridging among the one or more network devices via the wireless network interface162.

The ID device reader164is configured to read data from an associated ID device136. In one embodiment, the ID device reader164is configured to read data from RFID tags comprising the ID device136. The ID device reader164may also include a USB reader. In another embodiment, the ID device reader164may be implemented as an optical scanner for reading ID devices136that encode data via a printed bar code. In yet other embodiments, the ID device reader164may be configured to read data from other types of interfaces, such as other types of flash memories like an SD flash card.

In certain embodiments, the smart network host device120comprises one or more integrated circuits that implement respective functions of the smart network host device120. For example, the processor complex160, wired network interface166and wireless network interface162may be integrated into a single integrated circuit.

Persons skilled in the art will recognize that the smart network extender device140may be implemented using the basic architecture of the smart network host device120, with the exception that the ID device reader164and wired network interface166are not required for the smart network extender device140. Similarly, the smart network connector device150may be implemented using the basic architecture of the smart network host device120, with the exception that the ID device reader164is not required for the smart network connector device150.

FIG. 1Fillustrates a system software architecture for the smart network host device ofFIG. 1E, according to one example embodiment of the present disclosure. As shown, the software architecture104includes several software modules within the smart network host device120. Programming instructions stored within the processor complex160implement a portion of the system software architecture104that includes a runtime server180, a product solution space190and a network solution space196. The product solution space190comprises an object model192and one or more solution applications194. The object model192provides a standard, consistent abstraction of different network elements and related services within the smart network102. Exemplary network elements include devices coupled to the smart network102, such as printers, cameras and display devices. Exemplary services include device and service discovery, event tracking and generation, and state presentation for the different elements. In one embodiment, the object model192includes a network interface based on the well-known extensible markup language (XML). One or more solution applications194provide specific functionality, such as a specific view of a storage system, or a specific technique for presenting certain data. The network solution space196includes software modules configured to provide management of network elements and network services, including device services, local area network services within the smart network102, and wide area network services related to connectivity management of the external network110.

The runtime server180comprises a network provisioning module182, a service and discovery provisioning (SDP) module184, an event module186and a network configuration module188. The event module186tracks different network events, such as a network device advertising presence or updating status within the smart network102. The SDP module184maintains a persistent view of different network devices and related services, based on data from the event module186and on data from the network devices. The network provisioning module182provides authentication and authorization for network devices within the smart network102. Authentication credentials may be presented via a given ID device136. The network provisioning module182may also facilitate certain network services, such as DHCP leases. The network configuration module188includes hardware platform-specific implementation methods for network configuration and management. The persistent view comprises the network state model178ofFIG. 1A.

Persons skilled in the art will recognize that the smart network connector device150and smart network extender device140may be implemented using an appropriate subset of the system software architecture104described above in conjunction withFIG. 1F.

FIG. 1Gillustrates the smart network ofFIG. 1A, according to another example embodiment of the present disclosure. Here, the smart network102includes the smart network host device120, networking device142, one or more client devices130and a wide area network (WAN) interface device112, coupled to the external network110ofFIG. 1A. The WAN interface device112, smart network host device120and client devices130(0) through130(2) are configured to operate as previously described inFIG. 1A-1E.

In one embodiment, the networking device142allows authenticated clients (e.g., client devices130(1) and130(2)) to access the smart network102over a respective wireless client link135(1),135(2). The networking device142may be any device providing wireless connectivity to the external network110. For example, the networking device142may be a wireless router or wireless access point. As shown, the networking device142includes an antenna126used to transmit and receive radio transmissions of network frames from client devices130and smart network host device120. In this example, the networking device142has established a bridge link128with the smart network host device120. Network data transmitted by one of the client devices130destined for the external network110is received by the networking device142and retransmitted via bridge links128to the smart network host device120. The smart network host device120then forwards the network data to the external network110. Similarly, data packets from the external network110with a destination address of one of the client devices130are transmitted via bridge link128to the networking device142, which retransmits the data packets via one of the wireless client links to the appropriate client device130.

Depending on the embodiment, the smart network host device120may act as a registrar or wireless local area network (WLAN) manager for the client devices130. The networking device142may communicate with the smart network host device120to determine whether the client devices130are authorized to access the smart network102. If the device is authorized, then the access point allows that client device130to join the smart network102and may begin forwarding network frames to from the client device130.

Although embodiments are described herein with reference to the networking device142operating within the smart network102, other environments are broadly contemplated. For example, in an alternative embodiment, the networking device142operates outside of and/or in the absence of the smart network102. As an example, the networking device142may connect to an external network via a network link, providing access to the external network to one or more connected client devices130.

FIG. 1Hillustrates a network198that includes the networking device142ofFIG. 1G, according to an example embodiment of the present disclosure. The networking device142is connected to multiple client devices130, which include a wired computer197a, a wireless computer197b, a game console197c, a smart phone197dand a printing device197. Each client device130may be hardwired or wirelessly connected to the networking device142. The client devices130may also include other wireless devices197fand other wired devices197g. The networking device142may also facilitate communication with other private or public networks outside of the network198, such as the external network110. A network link199may be configured to connect the networking device142to the external network110. In one embodiment, the external network110is the Internet, and the network link199is an Internet link provided using a telephone modem, a Digital Subscriber Line (DSL) modem, a cable modem, an optical modem, etc.

In one embodiment, a vendor of the networking device142provides the setup key144in conjunction with the networking device142. The setup key144facilitates configuring the networking device142for use in the network198. More specifically, the setup key144facilitates interconnecting wireless and/or hardwired computers and other electronic devices through the networking device142, such that packets of data can be securely exchanged by the networked devices. To this end, the setup key140may provide a client device, such as the wireless computer197b, a network application containing executable instructions. When executed, the instructions cause the wireless computer197bto perform an operation for automatically configuring the networking device142to securely communicate wirelessly with the wireless computer197b. Automatically configuring the networking device142refers to configuring the networking device142without requiring a user to provide any configuration or network settings for the networking device142.

In one embodiment, the network application may store configuration settings of the configured networking device142on the setup key144. Doing so allows additional client devices to be securely connected to the networking device142by providing the setup key144to the additional client devices. The networking device142may also provide a user interface for modifying the configuration settings for the networking device142. Depending on the embodiment, the user interface may be accessed via a web browser application or via an administrative tool component installed on the computer197bfrom the setup key144. In one embodiment, the networking device is configured to authenticate a user to access the user interface, without requiring the user to specify a password.

In some embodiments, the user is authenticated based on a digital certificate stored on the setup key. That is, the user is authenticated on the basis of something they have (the setup key144) instead of something they know (a password). The administrative tool may provide the digital certificate to the networking device142during a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) handshake between the administrative tool component and the networking device142. In other embodiments, the network application or the administrative tool component imports the digital certificate into a browser application of the client device, and the browser application provides the digital certificate to the networking device142during an SSL/TLS handshake between the browser application and the networking device142. Generation of the digital certificate and/or authentication of the user may occur based on a predetermined security policy. Depending on the embodiment, the digital certificate may be pre-generated and stored on the setup key144. In other words, the digital certificate may exist on the setup key144prior to connecting the setup key144to any client device. In other embodiments, the digital certificate is generated by the network application and/or administrative tool component subsequent to connecting the setup key to a client device.

Advantageously, at least in some cases, the setup key simplifies the process for a user to configure a secure wireless network and configure client devices to connect to the secure wireless network. Additionally, the user may the user may access a user interface using the setup key144. Wireless networks are often desirable because computers and other electronic devices can be easily moved and positioned throughout a home or small business while retaining network connectivity. Incorporating wireless communication also helps to reduce the need for running cables. Secure wireless networks are often desirable due to a reduced susceptibility to security breaches, as compared to unsecured wireless networks. By using the techniques disclosed herein, the user may more conveniently and/or efficiently configure a wireless network with appropriate security settings, relative to alternative approaches.

One alternative approach may require the user to input one or more configuration parameters, such as: an Internet Protocol (IP) address of the networking device142(e.g., 192.168.0.1, etc.), a predetermined administrative username and password, a service set identifier (SSID), a network password, and a media access control (MAC) address. The SSID, also referred to as a network name or network identifier, refers to a character sequence that identifies a wireless LAN and that may be up to thirty-two characters in length. The network password may also be referred to as a security key or passphrase. The MAC address refers to a unique identifier assigned to a network adapter or network interface card, often referred to as a physical address.

Further, networking devices are often preconfigured as an open access point with no encryption and with a published SSID, allowing any device to access the wireless network provided by the access point, as well as attempt to access devices (whether authorized or not) connected to the access point. To properly secure the networking devices, the user may be required to select a wireless security protocol such as, for example, Wired Equivalent Privacy (WEP) encryption or Wi-Fi Protected Access (WPA and WPA2) encryption. The user may also be required to specify one or more options for a selected wireless security protocol, such as a desired WEP key length. Further, the user may also be required to specify some of the configuration parameters when adding additional devices to the network. By using the techniques disclosed herein, rather than the alternative approaches, the user is no longer required to specify any of the configuration parameters.

FIG. 2is a block diagram illustrating components of the client device130ofFIG. 1G, according to an example embodiment of the present disclosure. As shown, the client device130includes a processor210connected to a memory220, a USB port230, an Ethernet adapter240, a wireless network adapter250, and an optical disk drive260. The client device130may be connected connect to a display screen and input devices such as, for example, a keyboard, a touch screen, a mouse, a touchpad, a trackball, audio input devices, and the like. The Ethernet adapter240enables the client device130to physically connect to a network by a wire such as an Ethernet cable. The wireless network adapter250may include suitable transmitting and receiving components, such as transceivers, for wirelessly communicating with a local network. Both Ethernet adapter240and wireless network adapter250may be configured to communicate with a network, such as the network198ofFIG. 1H, using suitable communications protocols such as, for example, Internet Protocol Suite (TCP/IP). The client device130is shown with both the Ethernet adapter240and the wireless network adapter250for illustrative purposes only. While one or both hardwire and wireless adapter may be installed inside the client device130or externally connected to the client device130, merely one is sufficient to enable the client device130to connect to a network.

Other electronic devices added to the network198may have some of the components as described with reference to the client device130ofFIG. 2. The components of such devices may be configured to achieve the intended purposes of the particular electronic device, which may or may not differ from the client device130ofFIG. 2. In addition, other electronic devices may have a different combination of components such as, for example, a printing device without an optical disc drive.

FIG. 3is a block diagram illustrating components of the networking device142ofFIG. 1G, according to an example embodiment of the present disclosure. As shown, the networking device142includes a processor310operatively connected to a bus330that provides access to a memory320. The processor310may also be operatively connected to a wireless adapter350having suitable transmitting and receiving components, such as transceivers, for wirelessly communicating with local networked devices. Ethernet adapter340may also provide wired ports342for providing a hardwire connection between client devices130and the networking device142. An Internet port344allows the router300to connect to an Internet link, such as a modem, which communicates with private or public networks through, for example, Internet Service Providers (ISPs), Internet servers with dedicated bandwidth, switches, gateways, other routers or any other device used to achieve electronic communication between the networking device142and another network.

FIG. 4is a block diagram illustrating components of the setup key144ofFIG. 1G, according to an example embodiment of the present disclosure. As shown, the setup key144includes a storage medium400capable of storing data and executable code. For instance, the storage medium400may be a USB flash memory (USB key), a compact disc (CD). For example, in some embodiments, multiple setup keys may be used to configure a network. In one embodiment, e.g., a CD may be used initially to configure a network to include the networking device and a first client device, and a USB key is used to store configuration settings for adding additional client devices to the configured network. In another embodiment, an application stored on the USB key may be used to initially configure a network and to store configuration settings for the configured network. The USB key may then be used to add additional client devices to the configured network.

As shown, the storage medium400includes configuration settings410, a digital certificate460and a network application420. The network application420may include a setup component430, an administrative tool component440, and a connect computer component450. The network application420may be written in any number of programming languages capable of performing operations necessary to implement an embodiment of the present disclosure. The configuration settings410may be encoded using, for example, an Extensible Markup Language (XML) grammar.

In one embodiment, the configuration settings410include a mode element indicating a state of the storage medium400and an appropriate execution mode for the network application420. The execution mode may be a connect mode or a tool mode. The connect mode indicates that a user desires to add a client device to a network, and the tool mode indicates that a user desires to modify configuration settings of a configured network. For the connect mode, the configuration settings410may further include a count of client devices previously configured to connect to the network. The count may be incremented each time a client device is successfully configured.

As an example, if the count of configured client devices is zero, then the network application420may execute the setup component430to configure the networking device142. If the count of client devices is greater than zero, then the network application420bypasses execution of the setup component430and proceeds directly to executing the connect computer component450. In some embodiments, two separate counts are stored—one for wired client devices and one for wireless client devices.

In an alternative embodiment, the configuration settings410and/or network application420, or selected components thereof, may be provisioned in another component such as a wireless network adapter, which could be provided to a client device130to be configured to access the network198. In yet another embodiment, the configuration settings410and/or the network application420, or selected components thereof, could be received or downloaded from a web server and stored onto the setup key144or onto the client device130.

In one embodiment, the network application420and the configuration settings file410may guide a user to securely configure a local area network (LAN) having the networking device142and a first client device130with either a wireless or hardwired connection. In one embodiment, this configuration may be accomplished without requiring the user specify any configuration settings for the networking device142and/or the first client device130, such as an SSID, a network password, a wireless security protocol, an administrative username, an administrative password, etc. In one embodiment, the setup component430discovers a networking device142configured with factory default settings. The factory default settings may include an SSID conforming to a predetermined format, such as containing a predefined character sequence. For instance, the predetermined format may include a predefined character sequence of “CISCO” followed by a 5-digit number.

In one embodiment, once the networking device142is discovered, the setup component430then proceeds to configure the networking device142and the first client device130. Depending on the embodiment, the setup component430may also configure the networking device142with a wide area network (WAN) connection. Once the networking device142and the first client device130have been configured, the setup component430updates the configuration settings file410to reflect the configuration settings used in configuring the networking device142. The setup component430may also update the configuration settings file410to indicate that the networking device142and the first client device130have been configured. The connect computer component450may then be executed on additional client devices to configure the additional client devices to communicate with the router via either a wireless or hardwire connection and using the updated configuration settings file410.

In one embodiment, a user may subsequently desire to configure the networking device142via a user interface for modifying configuration settings of the networking device142. In some embodiments, the user may access the user interface via a web browser application (e.g., by visiting an IP address of the networking device, such as 192.168.0.1). In other embodiments, the user interface may be provided by the administrative tool component440, which is installed on a client device130.

In one embodiment, the networking device142may be configured to authenticate the user to access the user interface, based on the digital certificate460, without requiring the user to supply a password. To this end, the digital certificate460may be provided to the networking device142by the networking application420or administrative tool component440executing on the client device130. The digital certificate460may be provided to the networking device142during an SSL/TLS handshake with the networking device142. If the user interface is accessible by the web browser application, the network application150may copy the digital certificate460to the client device130and import the digital certificate460into the web browser application. Accordingly, the user may access the user interface via the web browser application without having to specify any username or password. In some embodiments, the digital certificate may be generated by the network application420based on a predetermined security policy. In other embodiments, a separate application generates the digital certificate and stores the digital certificate on the storage medium400, prior to the network application first being executed.

Alternatively, the storage medium400may be a read-only medium such as a CD or DVD. In such a case, the storage medium400may be manufactured such that the configuration settings410includes the digital certificate and configuration settings such as a network password, a network identifier, and an administrative password. The configuration settings stored on the medium are distinct from factory default configuration settings of a networking device142. Further configuration settings and/or digital certificate may be different for each copy of the storage medium400. Thus, the storage medium400need not be updated with the digital certificate or any of the configuration settings.

FIG. 5is a flowchart depicting a method500for configuring a secure wireless network, according to one embodiment of the present disclosure. As shown, the method500begins at step510, where the network application420discovers a networking device within a wireless connectivity range from a first client device. The step510may occur when a user connects the setup key144to the first client device, allowing the first client device to retrieve and execute the network application420stored on the setup key144. In certain embodiments, the network application420may be automatically launched, such as, for example, using autorun software technology provided by the Microsoft Windows XP operating system. In other embodiments, the user may be prompted to whether to launch the network application420.

At step520, the network application420uses network settings generated for the networking device142to configure that networking device142according to the network settings. For example, the network application420may use the configuration settings to specify a default SSID, wireless security protocols and/or a default network password used by a client to access the wireless network being configured. The wireless adapter of the client may be identified using a search for available network adapters on the client device. The search may be accomplished via one or more application programming interfaces (APIs) provided by the operating system executing on the client device.

In some embodiments, if a wireless adapter is detected that is not enabled, the network application420may automatically enable the wireless adapter. Enabling the wireless adapter may also be accomplished via one or more operating system APIs. If no wireless adapter is found, the network application420may attempt connect to the networking device142via a wired port. To this end, the network application420may first instruct the user to connect the networking device142and the client device130using an Ethernet cable. The network application420may then search for an available Ethernet adapter. If an Ethernet adapter is identified, the network application420determines whether the Ethernet adapter is enabled. If not, the network application420may automatically enable the Ethernet adapter. The network application420may also command the Ethernet adapter to perform a Dynamic Host Configuration Protocol (DHCP) release/renew. The network application420may then connect to the networking device142via the identified Ethernet adapter.

In one embodiment, after the network application420connects to the networking device142, the network application420gains administrative access to the networking device142via a default administrative username and a default administrative password. In an alternative embodiment, the network application420gains administrative access to the networking device142via the digital certificate460stored in the setup key144.

In one embodiment, after gaining administrative access, the network application420configures the network device142using the network settings, which may include an SSID, a network password, a wireless security protocol and the like. The configuration of the networking device142may be accomplished using one or more APIs provided by the networking device142. Some or all of the network settings may be automatically generated using a random generation algorithm. For example, the SSID could be a human readable string including an adjective and a noun such as, for example “ShortWillow” along with an appended numeric value (e.g., a portion of a serial number of the set up key). Further, the network settings may specify to enable a wireless security protocol, such as WPA. By configuring the networking device142with the generated network settings, the wireless security associated with the network198may be improved, without requiring the user to provide any of the network settings or understand the details of configuring a wireless network with wireless security protocols.

At step530, the network application420uses the network settings to configure the first client device to initiate a first wireless connection to the configured networking device. The first wireless connection is created without requiring the user to specify any of the network settings. For example, the first client device may be configured to initiate the first wireless connection using the SSID, generated password, and specified wireless security protocol generated as part of step520.

At step540, the network application420provides a digital certificate460to send to the networking device for authenticating the user to access a user interface for configuring the networking device. The networking device is configured to authenticate the user based on the digital certificate. Once authenticated, the user may modify any configuration settings of the networking device142, such as SSID, network password, wireless security protocol, parental controls, guest access, etc. After the step540, the method500terminates.

As described above, in one embodiment, a predetermined security policy may specify how users are authenticated to access the user interface for configuring the networking device. The predetermined security policy may also specify how digital certificates are generated. In one embodiment, the security policy specifies that each certificate conforms to the X.509 specification, which defines a standard format for public key infrastructure (PKI) certificates. The digital certificate for authenticating the user may also referred to as a client certificate. In some embodiments, the security policy also specifies to perform server validation. In other words, the networking device142sends a server certificate to the network application420, which authenticates the networking device142based on the server certificate. The security policy also specifies that a socket connection is immediately terminated on failure to validate a certificate. The security policy also specifies that the Hypertext Transfer Protocol Secure (HTTPS) protocol is used for control connections. The security policy also specifies that the HTTPS protocol may be used for data connections. For example, suppose that the security policy is applied in a context of a digital photo service. The request for the service to provide a digital photo may occur over an HTTPS connection, and the service may return a Uniform Resource Locator (URL) of the digital photo. The digital photo may then be retrieved via an HTTP connection and using the URL.

In some embodiments, the security policy further imposes one or more additional certificate generation and/or authentication constraints. The additional constraints may include a security protocol, cryptographic hash function type, a cryptographic mode of operation, an encryption standard, a certificate compatibility constraint, a certificate container type, a certificate format, a key container type, a key format, a cryptographic algorithm for digital signatures, a key size, a time duration during which certificates are valid, and a time duration during which certificate revocation lists (CRLs) are valid. Values assigned to each constraint may be tailored to suit the needs of a particular case. In one exemplary embodiment, the values for each constraint are assigned as follows:

TABLE IExample constraints specified by the security policySecurity protocol - Transport Layer Security (TLS) version 1.2Cryptographic hash function type - Secure Hash Algorithm 1 (SHA-1)Cryptographic mode of operation - Cipher-block chaining (CBC) modefor ciphersEncryption standard - Advanced Encryption Standard 128 (AES-128) ascipherCertificate compatibility constraint - Certificates are RSA-compatibleCertificate container type - Privacy Enhanced Mail (PEM) containersCertificate format - Use public-key cryptography standards (PKCS)formatsKey container type - Privacy Enhanced Mail (PEM) containersKey format - Use public-key cryptography standards (PKCS) formatsCryptographic algorithm for digital signatures - RSA algorithmKey size - 1024 bitsTime duration during which certificates are valid - 10 yearsTime duration during which certificate revocation lists are valid - 10years

The constraints in the above table may be used to configure a cryptography tool. The cryptography tool refers to an application for generating digital certificates and/or key pairs. Exemplary security tools include Open Secure Sockets Layer (OpenSSL) and GNU Transport Layer Security Library (GnuTLS), which implement the SSL/TLS protocols. The constraints may be stored in a preferences file associated with the cryptography tool.

In one embodiment, the vendor of a device generates a digital certificate for each device, where the device is the networking device142or the setup key144. In other words, the vendor may serve as a Certificate Authority (CA) for the digital certificates. A CA refers to an entity that issues digital certificates. At least in some embodiments, the vendor serves as a root CA for the digital certificates. A root CA refers to an entity at which a chain of trust of each digital certificate begins. The root CA is associated with a self-signed digital certificate; in other words, the root CA uses its own private key to sign its own digital certificate, also referred to as a root certificate. The signature of the root CA is verified using the public key associated with the root CA. To establish the chain of trust, the networking device142and the setup key144each store, in its firmware, a copy of the root certificate. In one embodiment, the root certificate may be generated using the following commands:

TABLE IIGenerating a root certificate01  mkdir -p demoCA02  od -N 8 -t x8 -A n /dev/random | sed -e ‘s/{circumflex over ( )} //’ > demoCA/serial03  touch demoCA/index.txt04  echo ‘01 ’ > demoCA/crlnumber05  openssl genrsa -aes128 -out he_root_keys.pem 102406  openssl rsa -in he_root_keys.pem -pubout >> he_root_keys.pem07  openssl req -new -key he_root_keys.pem -config openssl.cnf |openssl ca - extensions vs_ca -config openssl.cnf -keyfilehe_root_keys.pem -selfsign -outdir . - startdate 700101000000Z -outhe_root_cert.pem08  openssl x509 -in he_root_cert.pem -text -noout
In the above table, lines 01-04 configure a directory structure for use by the cryptography tool. Line 05 invokes the cryptography tool to generate a private key for the root CA, based on the constraints specified by the security policy. Line 06 invokes the cryptography tool to generate a public key for the root CA, based on the constraints specified by the security policy. Line 07 generates a self-signed root certificate for the root CA, based on the constraints specified by the security policy. The constraints may be specified as a command line argument and/or in a default configuration file associated with the cryptography tool, e.g., “openssl.cnf.” The root certificate is stored in a file “he_root_keys.pem.” Line 08 may optionally be executed to display the contents of the root certificate.

In one embodiment, each device may have an associated digital certificate that is signed by the root CA using the root certificate. The security policy may also specify constraints on one or more fields of each certificate. For example, the security policy may specify a constraint on a NotBefore field in a Validity section of each certificate. The constraint may specify that the NotBefore field is set to match the date of “Jan. 1 00:00:00 1970 GMT.” The security policy may also specify constraints on the Distinguished Name (DN) fields, which include fields such as Common Name, Organization, Organizational Unit, Locality, State or Province, and Country/Region. The security policy specifies that the Common Name field of test certificates is appended to include a predefined character sequence, “(test).” The security policy also specifies that the root certificate has a Common Name field storing “HE Root CA.” In the Common Name field of the root certificate, HE stands for Home Ecosystem, and Root CA specifies that the certificate is a root certificate.

In some embodiments, the digital certificate may have an associated type that is selected from a device certificate, a service certificate, and a firmware certificate. Although embodiments are herein described with reference to the digital certificates of each networking device142and/or setup key144being device certificates, it is contemplated that any digital certificate type may be used in other embodiments. In one embodiment, the security policy specifies that a device certificate has a Common Name field storing “HE Device <model name> <model ID> <model version>.” In the Common Name field of the device certificate, HE stands for Home Ecosystem, <model name>” is a device name assigned by the vendor of the device, <model ID> is a device identifier assigned by the vendor and <model version> is a device version number assigned by the vendor.

In one embodiment, the security policy also specifies that a service certificate has a Common Name field storing “HE Service <service name> <service ID> <service version>.” In the Common Name field of the service certificate, <service name> is a service name assigned by the vendor, <service ID> is a service identifier assigned by the vendor and <service version> is a service version number assigned by the vendor.

In one embodiment, the security policy also specifies that a firmware certificate has a Common Name field storing “HE Firmware <firmware name> <firmware ID> <firmware version>.” In the Common Name field of the firmware certificate, <firmware name> is a firmware name assigned by the vendor, <firmware ID> is a firmware identifier assigned by the vendor and <firmware version> is a firmware version number assigned by the vendor.

In one embodiment, each device may store the private key associated with the public key identified in the device certificate, which are generated using the cryptography tool based on the constraints defined by the security policy. The device may be any given networking device142or setup key144. Although such a device certificate includes a public key associated with the respective device, in some embodiments, a copy of the public key may also be separately stored outside of the device certificate. At least in some embodiments, the device certificates and/or private keys are generated by the vendor during or subsequent to manufacturing the respective device. In one embodiment, the device certificate may be generated using the following commands:

TABLE IIGenerating a device certificate01  openssl genrsa -aes128 -out he_device_keys.pem 102402  openssl rsa -in he_device_keys.pem -pubout >>he_device_keys.pem03  openssl req -new -key he_device_keys.pem -config openssl.cnf -outrequest.pem04  openssl ca -in request.pem -extensions v3_req -config openssl.cnf -keyfile he_root_keys.pem -cert he_root_cert.pem -outdir . -startdate700101000000Z -out he_device_cert.pem06  openssl x509 -in he_device_cert.pem -text -noout
In the above table, lines 01-02 invoke the cryptography tool to generate a public/private key pair for the device, based on the security policy. Lines 03-05 invoke the cryptography tool to generate a device certificate based on the security policy. Line 06 may optionally be executed to display the contents of the device certificate.

FIG. 6illustrates a device certificate600for a device, according to an example embodiment of the present disclosure. The device certificate600corresponds to the contents of the device certificate generated from the commands of Table II. As shown, the device certificate600includes a data portion602and a signature portion604. The data portion602includes a version605of the X.509 standard that the device certificate600conforms to, a serial number606for the device certificate600, a cryptographic hash function608used for signatures of the device, DN fields610identifying an issuer of the device certificate600, a validity period612for the device certificate600, DN fields614identifying the device, a public key encryption algorithm616used by the device, and a public key618of the device.

In one embodiment, the signature portion604of the device certificate600includes a cryptographic hash function620used for signatures of the CA and a signature622of the CA. The signature622of the CA is generated by encrypting, using a private key of the CA, a hash computed from the data portion602using the cryptographic hash function620. The DN fields610and the validity period612satisfy the constraints specified by the security policy. In order to authenticate a user for accessing a user interface for configuring the networking device142, device certificates are verified during an SSL/TLS handshake.

FIG. 7is a sequence diagram700depicting interactions between two actors during an SSL/TLS handshake, according to an example embodiment of the present disclosure. The interactions may be implemented using any library that supports certificate validation using SSL/TLS. For example, the LibCurl library may be used in conjunction with OpenSSL or GnuTLS. As shown, the actors include the network application420provided by the setup key144and the networking device142. In the context of the SSL/TLS handshake, the network application420acts as a client, and the networking device142acts as a server. At step710, the actors perform a setup operation by communicating via a predefined port, such as TCP port443. During the setup operation, the network application420sends a “client hello” message that includes cryptographic information such as the SSL/TLS version. The networking device142responds with a “server hello” message that contains a session identifier. At step720, the networking device sends its associated device certificate to the network application420. The device certificate may also be referred to as a server certificate.

At step725, the network application420authenticates the networking device142based on the received server certificate. Authentication is further described below in conjunction withFIG. 8. At step730, the actors perform a negotiation operation. During the negotiation operation, the network application420sends a random byte string that allows both the network application420and the networking device142to compute a session key to be used for encrypting subsequent message data, where the random byte string is encrypted using the public key of the networking device142. The random byte string may also be referred to as a pre-master secret. The session key is computed by the actors at steps7351,7352, based on the pre-master secret.

At step740, the networking device142sends a request for a client certificate. In response, at step750, the network application420sends the client certificate to the networking device142. At step755, the networking device142authenticates the client755using the received client certificate. Authenticating the client755is further described below in conjunction withFIG. 8. Once the client and the server are both authenticated, the user of the network application420may gain access to the user interface for configuring the networking device142. During user configuration of the networking device142via the user interface, the network application420and/or the networking device142may send and/or receive application data associated with configuring the networking device142. Depending on the embodiment, the application data may be encrypted or unencrypted. At step760, the actors communicate to request encryption using the generated session key. At step770, the actors send and/or receive encrypted application data. Additionally or alternatively, the actors may send and/or receive unencrypted application data.

FIG. 8is a flowchart depicting a method800for authenticating a user based on a client certificate, according to an example embodiment of the present disclosure. Assume a user requests to access a user interface for configuring the networking device142. In order to grant access to the user interface, the networking device142first authenticates the user by performing the method800during a TLS/SSL handshake. Doing so creates an encrypted communication channel between the client device and the networking device. The user may be authenticated by validating the client certificate. If the client certificate fails to validate, the user is denied access to the user interface. In some embodiments, the method800corresponds to the step755ofFIG. 7.

At step810, the networking device142receives a client certificate420from the network application420that is provided by the setup key144. The network application420may be executed by a client device130to which the setup key144is connected. The client certificate serves to associate the setup key144with a public key. The client certificate includes information such as a serial number606for the client certificate, a validity period612for the client certificate, DN fields614associated with the setup key144, a public key associated with the setup key144, DN fields610associated with the CA issuing the client certificate, and a signature of the CA. The signature of the CA may be generated by encrypting, using a private key of the CA, a hash computed over the information included in the client certificate.

At step820, the networking device142receives, from the network application420, random data and a signature associated with the setup key144. The signature is generated by encrypting the random data using a private key of the setup key144. The networking device142then performs steps830-860to validate the received client certificate. In one embodiment, validation of the client certificate succeeds only when all steps830-870validate successfully.

At step830, the networking device142validates the signature associated with the setup key144. The signature may be validated by decrypting the signature using the public key associated with the setup key144and comparing the decrypted signature with the random data. If the decrypted signature matches the random data, then the signature is considered validated. At step840, the networking device142validates the validity period in the client certificate. The validity period may be considered validated if the current time of the networking device142is within the validity period in the client certificate.

At step850, the networking device142validates that the CA is trusted by comparing the DN fields of the CA with DN fields included in a copy of the root certificate stored on the networking device142. If the DN fields match, then the CA is considered trusted. At step860, the networking device142validates the signature of the CA by decrypting the signature of the CA using a public key of the CA, where the public key of the CA is obtained from the copy of the root certificate. If the decrypted signature matches the information included in the data portion of the client certificate, then the signature of the CA is considered validated.

At step870, the networking device142validates the serial number for the client certificate based on a certificate revocation list (CRL) stored on the networking device142. The CRL is maintained by the vendor of the networking device142and/or the setup key144and includes a list of revoked certificate serial numbers. A certificate may be revoked when a private key associated with the certificate is compromised. The CRL may be stored in a portion of the filesystem in the firmware of the networking device142, where the portion is designated as a read-only portion that may only be updated during a firmware upgrade of the networking device142. In one embodiment, the read-only portion is given by a predefined location, “/etc/certs/.” If the serial number is not included in the CRL, then the serial number is considered validated. In some embodiments, the security policy may also specify predefined filenames for the CRL and/or certificates. For example, the security policy may specify that the CRL is named “he_crl.pem,” the root certificate is named “he_root_cert.pem,” the device certificate is named “he_device_cert.pem,” and any combination of the root certificate and the CRL is named “he_ca.pm.”

As described above, in one embodiment, if all steps830-870validate successfully, then the client is considered validated. Similarly, the client may also validate the server by performing variations of the steps810-870, using the server certificate instead of the client certificate. Once the client and the server are both validated, then the networking device142grants access to the user interface for configuring the networking device142. If the client or the server fails to be validated, the networking device142denies access to the user interface.

Advantageously, embodiments described above provide techniques for configuring a networking device to provide secure wireless connectivity to one or more client devices. One embodiment provides a setup key storing a network application. When a user connects the setup key to a client device, the client device executes the network application. The network application discovers and configures the networking device, using network settings generated for the networking device. Using the networking settings, the network application then configures the client device to initiate a first wireless connection to the configured networking device. The first wireless connection is created without requiring any user to specify any of the network settings. The network application may store the network settings onto the setup key. The user may then connect the setup key to other devices, to configure the other devices to initiate wireless connections to the configured networking device.

In one embodiment, the networking device is further configured to authenticate a user to access a user interface for configuring the networking device, where the user is not authenticated based on any password. In some embodiments, the user is authenticated based on a digital certificate received from the networking application, where the digital certificate is associated with the setup key. Advantageously, the user may configure a secure network more conveniently and/or efficiently at least in some cases. Should the user subsequently desire to further configure the networking device, the user may also more conveniently access the user interface for configuring the networking device.