Skip to content
This repository was archived by the owner on Dec 26, 2020. It is now read-only.

rework CRYPTO_POLICY handling for fedora #314

Merged
merged 4 commits into from
Jul 22, 2020
Merged

rework CRYPTO_POLICY handling for fedora #314

merged 4 commits into from
Jul 22, 2020

Conversation

schurzi
Copy link
Contributor

@schurzi schurzi commented Jul 22, 2020

the previous implementation did not handle fedora right. Now we check if
a CRYPTO_POLICY is present regardless of the OS version.

Signed-off-by: Martin Schurz [email protected]

the previous implementation did not handle fedora right. Now we check if
a CRYPTO_POLICY is present regardless of the OS version.

Signed-off-by: Martin Schurz <[email protected]>
@schurzi schurzi requested a review from rndmh3ro July 22, 2020 14:54
path: /etc/sysconfig
pattern: sshd
contains: '.*CRYPTO_POLICY=.*'
register: crypto_policy
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found no better way of detecting if we have to disable the CRYPTO_POLICY, that also works with all supported OSes

Considered alternatives were:

  • package_facts_module search for package crypto-policies
    Possible alternative, but maybe more ressource intensive. Also needs extra task but no register
  • OS version check
    Would need to construct a check which covers CentOS/RHEL/Oracle and Fedora with differend release versions, that would be very complicated
  • some varaible from default facts
    Nothing of value found there

schurzi added 3 commits July 22, 2020 20:26
Signed-off-by: Martin Schurz <[email protected]>
Signed-off-by: Martin Schurz <[email protected]>
Signed-off-by: Martin Schurz <[email protected]>
@rndmh3ro rndmh3ro merged commit 760f120 into master Jul 22, 2020
@rndmh3ro rndmh3ro deleted the fedora branch July 22, 2020 20:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants