[MGPG-106] Introduce second signer implementation based on Bouncy Castle (original) (raw)

Log inSkip to main contentSkip to sidebar

• Dashboards

• Projects

• Issues

• Help

  • Jira Core help
  • Keyboard Shortcuts
  • About Jira
  • Jira Credits

• Log In

1. Maven GPG Plugin (Moved to GitHub Issues)
2. MGPG-106

XMLWordPrintableJSON

Details

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: None

Description

The second signer would produce same GPG signatures (functionality wise would be equivalent to existing Gpg executable one) but with a big difference:

• no ~/.gnupg used (nor needed to contain private key)
• no external software needed
• in turn, it will need some alt way to have key to sign provided

Main goal is to make possible GPG signing on CI, thus automating releases (even from "managed" CI engines like GH Actions are)

Attachments

Issue Links

Activity

People

Votes:

0 Vote for this issue

Watchers:

3 Start watching this issue

Dates

Created:

03/Mar/24 16:03

Updated:

14/Jun/25 12:09

Resolved:

04/Mar/24 14:50