Easiest way to use Mycroft completely offline

[auwsom]

• Or, the firewall is set up incorrectly (which I asked for specifics on in the post below).

The link is to my summary of the correct firewall settings… perhaps you could check them.

Mycroft security

Maybe someone can double check these, but to clarify I believe the correct firewall rules to block port 8181 except from localhost 127.0.0.1 are either: using iptables: sudo /sbin/iptables -A INPUT -p tcp -s localhost --dport 8181 -j ACCEPT sudo /sbin/iptables -A INPUT -p tcp --dport 8181 -j DROP using ufw: sudo ufw allow in from 127.0.0.1 to any port 8181 sudo ufw deny in from any to any port 8181 using gufw (tested): add a 'simple' rule with Rule Name, allow, in, both, 8181 add an…

Regarding the OP going completely offline, in the second reply from KathyReid, she explains the STT (speech rec, right?) is the biggest obstacle at the moment. In the last few posts there seems to be progress on that front, though Google’s DeepSpeech is very accurate, but my understanding is currently not downloadable. Firefox’s may be, and there are other options directly above from jarbasAI.

The Mimic TTS can be downloaded. And the Mycroft.ai site ‘backend’ can be disabled by the config settings I pasted from the README. Or people have linked several personal backend projects, if you dont trust the initial setup from Mycroft.ai (dont know if it can be setup with the config settings in place from the getgo, havent tested), or you want to manage your own skills and config repository (which at that point, isnt it easier to apply skills changes and settings directly?)

For me, I have no problem using bandwidth for Googles DeepSpeech, and that seems to be less of a security concern if your voice data is anonymized, but I could see where wanting offline everything could be useful for all internal networked IOT and home devices could be controlled without any internet (appliances, gardening, robots, etc…).

Again, for me, I just wanted to secure unknown internet traffic after the port 8181 warning, but in the post I linked see all outbound traffic is on regular ports 80 and 443, the latter for secure account data I would presume. After securing port 8181 on internal networks with the above firewall settings, and disconnecting Mycroft.ai (at least until I want to exchange skills), I feel more confident any internet traffic from mycroft is at the same level of risk as a browser using ports 80 and 443. Correct me if Im wrong. (oh, and as was pointed out on the other post, where more discussion about security probably belongs, the threat from exposing port 8181 more than to localhost would be limited to data shared with mycroft… which could range from trivial to significant).