secure and test pi user about raspiblitz HOT 3 CLOSED

physical access will always be a problem. but trying to limit …

• first thing: drop him from sudoers ;) or even better: dont use user pi but leave him be and go with another/new user, e.g. "status", "monitor" or sth. you like
• one uncomplicated thing to limit the user is a restricted shell, e.g. sudo chsh -s /bin/rbash pi
• another thing is to prevent him from exiting the script, this can be done with exec, trap is an alternative fallback … for /home/pi/.bashrc

# automatic start the LCD info loop
SCRIPT=/home/admin/00infoLCD.sh
# trap may not be necessary when exec is used
trap $SCRIPT EXIT
# replace shell with script => logout when exiting script
exec $SCRIPT

further limits are possible

from raspiblitz.

Remove the sudo from pi needs more work to keep info-scripts running - thinking about not investing the time in this for now, because maybe we will make jump to rewrite for ePaper Hat (replacing LCD) anyway soon. Will gather feedback on that from the community on the hackday this week.

But the exec sounds like a quick win. Will test it out. Much thanks.

from raspiblitz.

exec works great :D

from raspiblitz.