Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1,014
    • Issues 1,014
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 28
    • Merge requests 28
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #9402
Closed
Open
Issue created May 14, 2015 by intrigeri@intrigeriMaintainer

Generalize automated tests for OpenPGP keys expiration

Originally created by @intrigeri on #9402 (Redmine)

In config/chroot_local-includes/lib/live/config/2000-import-gnupg-key we import /usr/share/doc/tails/website/*.key into the desktop user’s keyring. Since #9112 (closed) was resolved, that now means more keys than it used to. We already have automated tests to ensure that some of these keys are up-to-date and won’t expire any time soon. This should be generalized to all keys we import at boot time.

Feature Branch: kytv:test/9402-check-all-tails-openpgp-keys

Parent Task: #8543 (closed)

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