Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
stork
stork
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 139
    • Issues 139
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #356

Closed
Open
Opened Jul 22, 2020 by Tomek Mrugalski@tomek🛰Owner

Make sure Stork runs on RHEL7 with FIPS enabled

There's a report that Stork migration fails on RHEL7 with FIPS enabled.

For details, see support#16817.

On a related note, we should migrate away from poor security algorithms like MD5 and use something modern.

Assignee
Assign to
0.10
Milestone
0.10 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/stork#356