Remote Access

Last minute hack, started Sun, 11:55...

Team 5 Log

Just looking around:

  1. Come to venue, see Wi-Fi password

  2. $ ifconfig => my IP, e.g. 192.168.0.23

  3. $ nmap 192.168.0.0-255 -p 80 => e.g. 192.168.0.42 looks like an oven

  4. Access 192.168.0.42/Network.html => Sicherheitseinstellungen => set user "admin", password "hacked"

Let's add SSL/TLS and remote access:

  1. https://yaler.net/ => RELAY_DOMAIN

  2. https://yaler.net/macos => ./yalertunnel installed (would run right on the oven MCU in a real deployment)

  3. $ ./yalertunnel server 192.168.0.42:80 ssl:try.yaler.io:443 RELAY_DOMAIN -min-listeners 8

  4. Access (from everywhere) https://RELAY_DOMAIN.try.yaler.io/

  5. E.g. on your phone https://chart.googleapis.com/chart?cht=qr&chs=150x150&choe=UTF-8&chld=H&chl=https://RELAY_DOMAIN.try.yaler.io/

(Full disclosure: I'm a founder of Yaler)

👋 Contact
⎌

Edited

6 years ago ~ tamberg

Event finish

Joined the team

6 years ago ~ tamberg

Challenge shared
Tap here to review.

6 years ago ~ tamberg

Start

Contributed 6 years ago by tamberg for Open Food Data x Smart Kitchen Hackdays

Connect to our community on Team Chat | Twitter | Facebook

All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the Hack Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody. For more details on how the event is run, see the Guidelines on our wiki.

Creative Commons LicenceThe contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License.


Previous
Open Food Data x Smart Kitchen Hackdays
Next project