Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
bolt
bolt
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bolt
  • boltbolt
  • Merge Requests
  • !107

Merged
Created Sep 11, 2018 by Christian Kellner@gicmoOwner

Allow key upgrades for devices when security level gets upgraded

  • Overview 0
  • Commits 6
  • Pipelines 2
  • Changes 6

If a device gets authorized in USER mode, but then the security level changes to SECURE, the device will NOT be automatically get authorized, because we can not verify the its identity via a key. When the user then manually authorizes the devices via the dbus Authorize method, and the device allows for it (stored and supports key verification), a new key will be generated and stored. See also issue #30 (closed)

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: key_upgrade