Client install: auto-login for a password-less screen account, so a screen shows the player after a reboot #232

Closed
opened 2026-11-15 16:57:31 +00:00 by vivy · 2 comments
Owner

Problem

After a power cut or reboot, a screen stays at the GDM login page. The player starts only after a desktop login, and on campus nobody is there to log in. Seen on the test client (10.0.0.188:23) on 2026-11-15: no desktop session since boot, so the new build did not start.

Decision (product owner, GRI-2051, 2026-11-15)

The signage devices have no password on the screen account: a screen is never locked, so a password protects nothing.

What install.sh (client mode) does

  1. Creates a dedicated screen account if it does not exist. Name from config / --kiosk-user, default scryglass. Not in sudo, no admin rights.
  2. Removes its password (passwd -d), so it logs in with no prompt.
  3. GDM auto-login for that account: /etc/gdm3/custom.conf, [daemon] AutomaticLoginEnable=true, AutomaticLogin=<user>. Edit only those two keys; keep the rest of the file.
  4. No screen lock, no blanking, no idle suspend for that account (dconf lock file, so a desktop update cannot turn it back on).
  5. The player autostarts in that session (already the case).
  6. install.sh upgrade keeps an existing setting and does not re-create the account.

Safety

  • sshd refuses empty passwords by default (PermitEmptyPasswords no). The installer checks that and stops with a clear message if it is set to yes.
  • The account has no sudo, so a person at the screen cannot change the system.
  • An operator who does want a password can pass --kiosk-password-keep (or the config key): then only auto-login is set.

Done when

  • A fresh client install, then a reboot, shows the player with no keyboard input.
  • Test in scripts/tests/ for the custom.conf edit (keys set, other content kept, second run changes nothing).
  • docs/ deployment guide names the account and the opt-out.
## Problem After a power cut or reboot, a screen stays at the GDM login page. The player starts only after a desktop login, and on campus nobody is there to log in. Seen on the test client (10.0.0.188:23) on 2026-11-15: no desktop session since boot, so the new build did not start. ## Decision (product owner, GRI-2051, 2026-11-15) The signage devices have **no password** on the screen account: a screen is never locked, so a password protects nothing. ## What `install.sh` (client mode) does 1. Creates a dedicated screen account if it does not exist. Name from config / `--kiosk-user`, default `scryglass`. **Not** in `sudo`, no admin rights. 2. Removes its password (`passwd -d`), so it logs in with no prompt. 3. GDM auto-login for that account: `/etc/gdm3/custom.conf`, `[daemon] AutomaticLoginEnable=true`, `AutomaticLogin=<user>`. Edit only those two keys; keep the rest of the file. 4. No screen lock, no blanking, no idle suspend for that account (dconf lock file, so a desktop update cannot turn it back on). 5. The player autostarts in that session (already the case). 6. `install.sh upgrade` keeps an existing setting and does not re-create the account. ## Safety - `sshd` refuses empty passwords by default (`PermitEmptyPasswords no`). The installer checks that and stops with a clear message if it is set to `yes`. - The account has no sudo, so a person at the screen cannot change the system. - An operator who does want a password can pass `--kiosk-password-keep` (or the config key): then only auto-login is set. ## Done when - A fresh client install, then a reboot, shows the player with no keyboard input. - Test in `scripts/tests/` for the `custom.conf` edit (keys set, other content kept, second run changes nothing). - `docs/` deployment guide names the account and the opt-out.
Member

State: implemented, PR #234 open against dev, CI running.

What install.sh client now does: everything in the description (account, passwd -d, the two GDM keys only, locked no-lock/no-blank/no-suspend dconf for that account only, upgrade keeps an existing setting) plus the sshd check and --kiosk-password-keep. Details are in the PR body and in plan/operations/deployment.md → "The screen account".

Choices I made that the description did not settle:

  • --no-kiosk (SCRYGLASS_KIOSK=no): no account and no auto-login, for somebody installing the client on a desktop they use themselves. The settings are recorded in /etc/grimoirix-signage/install.toml so an upgrade keeps them. Without that file, an upgrade would quietly add the account to a device installed with --no-kiosk.
  • The account you name is refused if it has sudo or is a system account. An empty password on a sudo account would let anybody at the screen become root.
  • An upgrade of a device from before this, with no auto-login set, gets the screen account. That is the 10.0.0.188 case. The player's device identity is stored per user, so that device appears once as a new pending registration, and someone has to approve it in the panel.
  • No GDM (Raspberry Pi OS uses LightDM): nothing is set up, and the installer says so.

Measured: scripts/tests/install-client-kiosk-test.sh, 62 assertions, all pass. They cover the custom.conf edit (keys set, all other lines kept, second run byte-identical) and the whole step run twice on a private root (second run writes nothing). local-gates.sh --frontend-only passed.

Not measured yet, and I cannot measure it from here: the first Done-when item, a real install followed by a reboot. This build host has no root and no container, and I have no access to the test client 10.0.0.188. Once #234 is merged, somebody with that access needs to run ... | sudo bash -s -- upgrade client on it, reboot, and check that the player shows with no keyboard input. If it does not, run journalctl -b -u gdm and cat /etc/gdm3/custom.conf and post both outputs here.

**State: implemented, PR #234 open against `dev`, CI running.** What `install.sh client` now does: everything in the description (account, `passwd -d`, the two GDM keys only, locked no-lock/no-blank/no-suspend dconf for that account only, `upgrade` keeps an existing setting) plus the sshd check and `--kiosk-password-keep`. Details are in the PR body and in `plan/operations/deployment.md` → "The screen account". Choices I made that the description did not settle: - **`--no-kiosk`** (`SCRYGLASS_KIOSK=no`): no account and no auto-login, for somebody installing the client on a desktop they use themselves. The settings are recorded in `/etc/grimoirix-signage/install.toml` so an upgrade keeps them. Without that file, an upgrade would quietly add the account to a device installed with `--no-kiosk`. - **The account you name is refused if it has sudo or is a system account.** An empty password on a sudo account would let anybody at the screen become root. - **An upgrade of a device from before this, with no auto-login set, gets the screen account.** That is the 10.0.0.188 case. The player's device identity is stored per user, so that device appears once as a new pending registration, and someone has to approve it in the panel. - **No GDM** (Raspberry Pi OS uses LightDM): nothing is set up, and the installer says so. Measured: `scripts/tests/install-client-kiosk-test.sh`, 62 assertions, all pass. They cover the custom.conf edit (keys set, all other lines kept, second run byte-identical) and the whole step run twice on a private root (second run writes nothing). `local-gates.sh --frontend-only` passed. **Not measured yet, and I cannot measure it from here:** the first Done-when item, a real install followed by a reboot. This build host has no root and no container, and I have no access to the test client 10.0.0.188. Once #234 is merged, somebody with that access needs to run `... | sudo bash -s -- upgrade client` on it, reboot, and check that the player shows with no keyboard input. If it does not, run `journalctl -b -u gdm` and `cat /etc/gdm3/custom.conf` and post both outputs here.
Member

State: PR #234 is green and ready to merge into dev.

  • fj ci 234 → exit 0 on 616ae9b5. All 11 contexts pass, including install.sh client upgrade (step scripts/tests/install-client-kiosk-test.sh, the new 62-assertion test: keys set, other content kept, second run changes nothing).
  • Chief of staff: please merge #234 into dev.

Still open before this issue can close: the reboot proof on a real device. "A fresh client install, then a reboot, shows the player with no keyboard input" has not been done. I have no login on 10.0.0.188 and no root on the build host. After the merge, someone with access needs to run:

sudo ./install.sh upgrade client     # on 10.0.0.188, from dev
sudo reboot

Then check:

  1. GDM logs scryglass in with no keyboard input.
  2. The player is on screen.
  3. The device appears once as a new pending registration in the panel, which needs approving. The device identity is stored per user, so the new account counts as a new device.

Chief of staff: please name who holds 10.0.0.188. I'll leave this issue open until that result is posted here.

**State: PR #234 is green and ready to merge into `dev`.** - `fj ci 234` → exit 0 on `616ae9b5`. All 11 contexts pass, including `install.sh client upgrade` (step `scripts/tests/install-client-kiosk-test.sh`, the new 62-assertion test: keys set, other content kept, second run changes nothing). - Chief of staff: please merge #234 into `dev`. **Still open before this issue can close: the reboot proof on a real device.** "A fresh client install, then a reboot, shows the player with no keyboard input" has not been done. I have no login on 10.0.0.188 and no root on the build host. After the merge, someone with access needs to run: ``` sudo ./install.sh upgrade client # on 10.0.0.188, from dev sudo reboot ``` Then check: 1. GDM logs `scryglass` in with no keyboard input. 2. The player is on screen. 3. The device appears once as a new pending registration in the panel, which needs approving. The device identity is stored per user, so the new account counts as a new device. Chief of staff: please name who holds 10.0.0.188. I'll leave this issue open until that result is posted here.
vivy closed this issue 2026-11-15 18:49:23 +00:00
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#232
No description provided.