10 Commits

Author SHA1 Message Date
3bdac850b6 Merge pull request #58 from KasperskyLab/dev
Adding few features.
2021-02-26 14:28:16 +01:00
885d67afd0 Adding few seconds before internet check 2021-02-26 14:26:50 +01:00
6de9f4aabe Change icon button to home button 2021-02-26 14:10:09 +01:00
c3b48f278d Add back button 2021-02-26 13:47:57 +01:00
e4d63a7ef5 Preventing the analyzed device to reach TinyCheck 2021-02-26 13:25:10 +01:00
672b8cf0c1 Merge pull request #57 from KasperskyLab/dev
Update install.sh with new node version.
2021-02-26 12:20:26 +01:00
4488a52631 Update install.sh 2021-02-26 12:15:45 +01:00
92b89b78cf Merge pull request #56 from KasperskyLab/main
Update dev branch
2021-02-26 12:13:27 +01:00
22c7cf1119 Merge pull request #54 from KasperskyLab/update-feature
Update from GUI feature
2021-02-19 16:45:41 +01:00
67ac58ef46 Deleting Q&A. 2021-02-18 09:17:54 +01:00
6 changed files with 27 additions and 13 deletions

View File

@ -40,15 +40,6 @@ Once installed, you can connect yourself to the TinyCheck backend by browsing th
The backend allows you to edit the configuration of TinyCheck, add extended IOCs and whitelisted elements in order to prevent false positives. Several IOCs are already provided such as few suricata rules, FreeDNS, Name servers, CIDRs known to host malicious servers and so on.
### Questions & Answers
**Your project seem very cool, does it send data to Kaspersky or any telemetry server?**<br /><br />
No, at all. You can look to the sources, the only data sent by TinyCheck is an HTTP GET request to a website that you can specify in the config, as well as the watchers URLs. Kaspersky don't - and will not - receive any telemetry from your TinyCheck device.<br /><br />
**Can you list some hardware which can be used with this project (touch screen, wifi dongle etc.)?**<br /><br />
Unfortunately, we prefer to not promote any hardware/constructor/website on this page. Do not hesitate to contact us if you want specific references. <br /><br />
**I'm not very confortable with the concept of "watchers" as the IOCs downloaded are public. Do you plan to develop a server to centralize AMBER/RED IOCs?**<br /><br />
Yes, if the demand is felt by NGOs (contact us!). Is it possible to develop this kind of thing, allowing you to centralize your IOCs and managing your fleet of TinyCheck instances on a server that you host. The server can also embed better detection rules thanks to the telemetry that it will receive from devices.<br />
### Special thanks
**Guys who provided some IOCs**

File diff suppressed because one or more lines are too long

View File

@ -2,9 +2,11 @@
<div class="controls" v-if="display">
<i class="off-icon" v-on:click="action('shutdown')" v-if="off_available"></i>
<i class="quit-icon" v-on:click="action('quit')" v-if="quit_available"></i>
<i class="home-icon" @click="$router.push({ name: 'home' })"></i>
<i class="update-icon" v-if="update_available&&update_possible" @click="$router.push({ name: 'update' })"></i>
</div>
</template>
<script>
import axios from 'axios'

View File

@ -46,7 +46,7 @@
}
},
created: function() {
setTimeout(function () { this.internet_check(); }.bind(this), 1000);
setTimeout(function () { this.internet_check(); }.bind(this), 5000);
}
}
</script>

View File

@ -283,7 +283,7 @@ install_package() {
rm Release.key && sudo apt-get update
apt-get install zeek -y
elif [[ $1 == "nodejs" ]]; then
curl -sL https://deb.nodesource.com/setup_12.x | bash
curl -sL https://deb.nodesource.com/setup_14.x | bash
apt-get install -y nodejs
elif [[ $1 == "dig" ]]; then
apt-get install -y dnsutils
@ -436,7 +436,7 @@ change_configs() {
}
feeding_iocs() {
echo -e "\e[39m[+] Feeding your TinyCheck instance with fresh IOCs and whitelist."
echo -e "\e[39m[+] Feeding your TinyCheck instance with fresh IOCs and whitelist, please wait."
python3 /usr/share/tinycheck/server/backend/watchers.py
}
@ -480,4 +480,4 @@ else
feeding_iocs
cleaning
reboot_box
fi
fi

View File

@ -290,8 +290,14 @@ class Network(object):
try:
sp.Popen("echo 1 > /proc/sys/net/ipv4/ip_forward",
shell=True).wait()
# Enable forwarding.
sp.Popen(["iptables", "-A", "POSTROUTING", "-t", "nat", "-o",
self.iface_out, "-j", "MASQUERADE"]).wait()
# Prevent the device to reach the 80 of TinyCheck.
sp.Popen(["iptables", "-A", "INPUT", "-i", self.iface_in, "-d",
"192.168.100.1", "-p", "tcp", "--dport", "80", "-j" "DROP"]).wait()
return True
except:
return False