Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 311
    • Issues 311
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #205
Closed
Open
Issue created Mar 17, 2020 by Michal Nowikowski@godfrydContributor

network connection to agent should be well secured by default

re: !87 (comment 116633)

design doc: https://gitlab.isc.org/isc-projects/stork/-/wikis/Designs/Agent-Server-Security

There are a couple of aspects to be addressed here:

  • confidentiality
  • mutual authentication
  • authorization

This work has been split to separate issues:

  • #479 (closed) (keys and certs generation)
  • #481 (closed) (agent registration in the server)
  • #483 (closed) (agent deployment and authorization UI)
  • #485 (closed) (demo update)
  • #486 (closed) (docs)
  • #507 (closed) (system tests)
Edited Mar 08, 2021 by Michal Nowikowski
Assignee
Assign to
Time tracking