Skip to content
Snippets Groups Projects
  1. Mar 02, 2025
  2. Jan 04, 2025
  3. Oct 31, 2024
  4. Oct 23, 2024
  5. Sep 19, 2024
  6. Sep 02, 2024
  7. Aug 07, 2024
  8. Aug 05, 2024
  9. Jul 20, 2024
  10. Jul 04, 2024
  11. May 28, 2024
  12. May 26, 2024
  13. May 25, 2024
  14. May 02, 2024
  15. Mar 12, 2024
  16. Feb 05, 2024
    • Christine Caulfield's avatar
      Report crypto errors back to cfg reload · ce03c683
      Christine Caulfield authored
      
      Because crypto changing happens in the 'commit' phase
      of the reload and we can't get sure that knet will
      allow the new parameters, the result gets ignored.
      This can happen in FIPS mode if a non-FIPS cipher
      is requested.
      
      This patch reports the errors back in a cmap key
      so that the command-line can spot those errors
      and report them back to the user.
      
      It also restores the internal values for crypto
      so that subsequent attempts to change things have
      predictable results. Otherwise further attempts can
      do nothing but not report any errors back.
      
      I've also added some error reporting back for the
      knet ping counters using this mechanism.
      
      The alternative to all of this would be to check for FIPS
      in totemconfig.c and then exclude certain options, but this
      would be duplicating code that could easily get out of sync.
      
      This system could also be a useful mechanism for reporting
      back other 'impossible' errors.
      
      Signed-off-by: default avatarChristine Caulfield <ccaulfie@redhat.com>
      Reviewed-by: default avatarJan Friesse <jfriesse@redhat.com>
      ce03c683
  17. Jan 02, 2024
Loading