Abstract: 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.

Abstract: Techniques are presented for discovering a previously configured network device. In one embodiment, a basic service set identification (BSSID) that uniquely identifies a network device (i.e., a router) is saved when the network device or a client device is configured. The stored BSSID indicates that the network device has previously been configured. After the network device is reset—i.e., one or more user-configurable settings return to their default settings—a client device may execute a setup application to reconfigure the network device. The setup application may compare the BSSID being broadcasted by the network device with the BSSID stored in the memory. If the BSSIDs match, the setup application may automatically select the network device without user input. Because the network device was previously configured, the setup application assumes that the user is attempting to reconfigure the network device after it has been reset.

Abstract: Techniques are presented for managing firmware updates for a plurality of devices within a wireless network. Embodiments monitor network usage of the plurality of devices to collect historical usage data. An optimal window of time for updating the firmware of the plurality of devices is then determined, based on the collected historical device usage data. Embodiments flag at least one of the plurality of devices for a firmware update, based on a current firmware version of the device and a corresponding available firmware version for the device. In one embodiment, dependencies for each of the plurality of devices are considered in flagging the devices for the firmware update. The firmware of the flagged devices is updated during the determined optimal window of time.

Abstract: A method in one example implementation includes discovering a networking device within a wireless connectivity range from a first computing device. The networking device may be configured for wireless connectivity by sending new network configuration settings to the networking device to be stored in a memory element. The method also includes configuring the first computing device to initiate a wireless connection to the networking device, such that the wireless connection is created without requiring the user to provide any configuration settings associated with the wireless connection. In more specific embodiments, if it is determined that the networking device is unconfigured, then the new network configuration settings are automatically generated. In other more specific embodiments, the new network configuration settings include a new network identifier and a new network password.

Abstract: Techniques are presented for managing firmware updates for a plurality of devices within a wireless network. Embodiments monitor network usage of the plurality of devices to collect historical usage data. An optimal window of time for updating the firmware of the plurality of devices is then determined, based on the collected historical device usage data. Embodiments flag at least one of the plurality of devices for a firmware update, based on a current firmware version of the device and a corresponding available firmware version for the device. In one embodiment, dependencies for each of the plurality of devices are considered in flagging the devices for the firmware update. The firmware of the flagged devices is updated during the determined optimal window of time.

Abstract: Techniques are presented for discovering a previously configured network device. In one embodiment, a basic service set identification (BSSID) that uniquely identifies a network device (i.e., a router) is saved when the network device or a client device is configured. The stored BSSID indicates that the network device has previously been configured. After the network device is reset—i.e., one or more user-configurable settings return to their default settings—a client device may execute a setup application to reconfigure the network device. The setup application may compare the BSSID being broadcasted by the network device with the BSSID stored in the memory. If the BSSIDs match, the setup application may automatically select the network device without user input. Because the network device was previously configured, the setup application assumes that the user is attempting to reconfigure the network device after it has been reset.

Abstract: Phishing detection, prevention, and notification is described. In an embodiment, a messaging application facilitates communication via a messaging user interface, and receives a communication, such as an email message, from a domain. A phishing detection module detects a phishing attack in the communication by determining that the domain is similar to a known phishing domain, or by detecting suspicious network properties of the domain. In another embodiment, a Web browsing application receives content, such as data for a Web page, from a network-based resource, such as a Web site or domain. The Web browsing application initiates a display of the content, and a phishing detection module detects a phishing attack in the content by determining that a domain of the network-based resource is similar to a known phishing domain, or that an address of the network-based resource from which the content is received has suspicious network properties.

Abstract: 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.

Abstract: A method in one example implementation includes discovering a networking device within a wireless connectivity range from a first computing device. The networking device may be configured for wireless connectivity by sending new network configuration settings to the networking device to be stored in a memory element. The method also includes configuring the first computing device to initiate a wireless connection to the networking device, such that the wireless connection is created without requiring the user to provide any configuration settings associated with the wireless connection. In more specific embodiments, if it is determined that the networking device is unconfigured, then the new network configuration settings are automatically generated. In other more specific embodiments, the new network configuration settings include a new network identifier and a new network password.

Abstract: Various embodiments provide protection against web resources associated with one or more undesirable activities. In at least some embodiments, a method detects and responds to a user-initiated activity on a computing device. Responding can include, by way of example and not limitation, checking locally, on the computing device, whether a web resource that is associated with the user-initiated activity has been identified as being associated with a safe site. Furthermore, in at least some embodiments, the method checks remotely, away from the computing device, whether the web resource is identified as being at least possibly associated with one or more undesirable activities.

Abstract: Various embodiments provide protection against web resources associated with one or more undesirable activities. In at least some embodiments, a method detects and responds to a user-initiated activity on a computing device. Responding can include, by way of example and not limitation, checking locally, on the computing device, whether a web resource that is associated with the user-initiated activity has been identified as being associated with a safe site. Furthermore, in at least some embodiments, the method checks remotely, away from the computing device, whether the web resource is identified as being at least possibly associated with one or more undesirable activities.

Abstract: Phishing detection, prevention, and notification is described. In an embodiment, a messaging application facilitates communication via a messaging user interface, and receives a communication, such as an email message, from a domain. A phishing detection module detects a phishing attack in the communication by determining that the domain is similar to a known phishing domain, or by detecting suspicious network properties of the domain. In another embodiment, a Web browsing application receives content, such as data for a Web page, from a network-based resource, such as a Web site or domain. The Web browsing application initiates a display of the content, and a phishing detection module detects a phishing attack in the content by determining that a domain of the network-based resource is similar to a known phishing domain, or that an address of the network-based resource from which the content is received has suspicious network properties.

Abstract: A tag-based structure for communicating software update metadata information to client computers and to update service nodes is presented. An update metadata file includes: an identifier tag including a software update identifier that uniquely identifies the software update; zero or more general properties tags that carry general property information relating the software update; zero or more localized properties tags that carry localized property information organized according to language; zero or more relationship tags that identify dependency relationships the current software update, as described in the update metadata, has with other software updates; zero or more applicability rules tags that carry information for determining the applicability of the software update to a client computer; zero or more files tags that carry information relating to the software update's payload files; and handler specific data tags that carry information directed to the software handler for installing the software update.