Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 970
    • Issues 970
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #17135
Closed
Open
Issue created Oct 08, 2019 by segfault@segfaultDeveloper

Don't store the admin password in cleartext

Originally created by @segfault on #17135 (Redmine)

The Greeter currently stores the user-chosen admin password unhashed in /var/lib/gdm3/tails.password. In /etc/gdm3/PostLogin/Default, the password is then set via chpasswd and /var/lib/gdm3/tails.password is removed.

IMO, passwords should never be stored in cleartext. Instead, we should store them hashed and use chpasswd -e to set them.

This will also make it easier to persist the password, as part of persisting the Greeter options, which I plan to work on.

Feature Branch: bugfix/17135-store-admin-pw-hashed

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking