OpenWink alters a number of files which are at the core of the Wink Hub. Each file is backed up to allow the user to restore the Wink Hub to out-of-the-box (pre- OpenWink) condition if they choose to.
/database/wpa_supplicant.conf
This file does not exist on a Wink Hub out of the box. It gives the Wink Hub the necessary configuration information to connect to a home WiFi network. If the Wink Hub hasn't received a proper token from the Wink cloud, this file is perpetually deleted in an attempt to prevent local control of the Hub. OpenWink resolves this to create a constant network connection.
/etc/default/dropbear
A configuration file for dropbear, which is the SSH server running on the Wink Hub. This file controls whether the SSH server requires RSA key authentication or not. Since RSA keys are not a common tool for most users, this adds an unnecessary level of complexity during the initial configuration. The preconfiguration script for OpenWink removes the RSA key requirement, but the full OpenWink package makes it easier (yet still safe) to transfer RSA keys and reinstate the RSA key requirement if desired.
/etc/hosts
This file is used to define essential static IP addresses. It is often used to block a system's access to certain websites. OpenWink uses this file to block the Wink update servers, so that the Wink Hub can't be forced to update it's firmware and lock you out.
/etc/init.d/S31platform
This file controls network startup for the Wink Hub. It also prevents the Wink Hub from connecting to any home network without a valid authorization token from Wink. Lines 93 through 95 ("if [ ! -e /database/oauth ]; then...fi") are removed so that the Wink Hub ignores the token requirement.
/openwink
This directory is created by OpenWink and is the main repository for the OpenWink software, being called upon during SSH/UART connections and the OpenWink web interface.
/root/.ssh/authorized_keys
This file contains the RSA public keys used for SSH connections. Wink leaves their development key in this file, which provides Wink back-door access to your Wink Hub. We strongly recommend removing this key...OpenWink asks the user and obliges their choice. Any RSA keys created by the user and transferred via OpenWink are stored here.
/root/wifi/run_ap.sh
This file controls the SSID that is broadcast by the Wink Hub when it is operating in access point mode, which happens when it can't connect to a home network. The SSID is pseudo-random, which can be a disaster in a classroom environment and just ain't cool in a customized appliance. OpenWink prompts the user for a personalized SSID.
/var/www/set_dev_value.php
Many others recommend changing this file to add capability over the Wink Hub's web server. We essentially ignore this file, since the OpenWink web component replaces the entire web interface.