Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A acme-dns-tiny
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Adrien Dorsaz
  • acme-dns-tiny
  • Issues
  • #5
Closed
Open
Created Nov 05, 2016 by Adrien Dorsaz@adrienOwner0 of 3 tasks completed0/3 tasks

Enable use of ECDSA private account key

As boulder allow to use either RSA or ECDSA account key, we should be able to use both of them.

I think we can do this by two means:

  • use openssl to read the key and find parameters inside it
  • ask to add configuration inside the config file if user uses non-rsa key

To acheive this issue will have to:

  1. Update the account key rollover to take into account every RSA-PSK and ECDSA possible algorithm
  2. Update the acme-dns-tiny script wot take into account one of RSA-PSK algorithm and one of ECDSA algorithm
  3. Update our documentation to warn users using ECDSA keys that they have to use our choice to create their key (or adapt themselves the script with example inside the account key rollover tool) and that they'll have more work when the choice will be updated to latest securty recommendations.
Assignee
Assign to
Time tracking