Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Passwords and Secrets Passwords and Secrets
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • Passwords and SecretsPasswords and Secrets
  • Issues
  • #170

Closed
Open
Created Jan 07, 2018 by Bugzilla@bugzilla-migration💬Reporter

Cannot set 'ultimate' level of trust on public GnuPG key

Submitted by Przemysław Kowalczyk

Link to original bug (#792311)

Description

The level 'ultimate' should be available not only for private keys, but also for public ones. This was already mentioned in #350206 and is supposedly a feature, not a bug, but I strongly oppose and here's why:

  1. 'gpg --edit-key' allows such setting (and then seahorse is unable to show it properly, but that's another bug)
  2. such level is needed when encrypting a file with gpg, otherwise it will fail stating the key is not trusted.

Version: 3.20.x

Assignee
Assign to
Time tracking