In this tutorial I will share some of my experiences with kiosk softwares running on Debian. I had some problems during my first try mostly because of my insufficient linux knowledge. I do not want you to have the same problems. I did everything from scratch and may have some unidentified problems/bugs even if there are ready made solutions.
Since I love debian with xfce, I have never thought using KDE on Debian or others which supports kiosk mode. I used xfce because xfce is a lightweight desktop environment suitable for kiosk systems which generally have low RAM and CPU. I listed my basic requirements of a kiosk so I tried to achieve them.
I realized that using MS Windows based systems did not fulfill my requirements in terms of cost, security, and cpu architecture flexibility.
Managing remote computers (in this case kiosks) can be easy if you use right tools.
VNC is a desktop sharing system like RDP in Windows. You may setup VNC Server for your kiosks to fix the daily problems. I wrote tutorial explaining how to setup VNC Server on Debian (jessie). It will help you to connect to your kiosks.
SSH is a secure protocol for getting access to remote computers highly used in Linux/Unix World. Settingup a ssh server is also very important to solve the problems easily. When you install OpenSSH server to your Debian kiosk do not forget to enable root access during development period, which is documented here.
Linux shell is very powerfull and you can do management of kiosks easily from command line (terminal) if you learn how to use Linux shell scripting. IMHO Bash Shell is more user friendly than other shells. There are lots of tutorials on the internet.
Do not forget to visit my cheat sheet for general Linux commands.
I think you do not want to be hacked for not paying enough attention to securing your clients. If you use your kiosk in public, you can ruin your business and become a disreputable company/person. Of course there are many tools out there but I will suggest you only one tool fail2ban.
Fail2ban scans log files (e.g. /var/log/apache/error_log) and bans IPs that show the malicious signs
Documentation of fail2ban is not very good but if you dig in you will learn how it works and how you modify it for your needs. Default settings may be enough but for optimizing resources in kiosks you can tweak it. It is easy to install fail2ban from terminal with
aptitude install fail2ban
TO BE CONTINUED…