Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid usage of legacy algorithms on libssl-3.0+ #53

Merged
merged 3 commits into from
Jun 6, 2024

Commits on Jun 24, 2022

  1. Avoid usage of legacy algorithms on libssl-3.0+

    Single DES and MD4 are considered legacy algorithms in OpenSSL/libssl-3.0.
    They can be enabled by adjusting the openssl configuration file or by using the new provider concept of OpenSSL-3.
    Editing the configuration must be done by each use of rubyntlm, which is very inconvenient.
    The provider API is not yet supported by the ruby binding to OpenSSL.
    
    So it's better to avoid the legacy algorithms at all.
    The single DES algorithm can easily implemented by a two key 3-DES run.
    The md4 implementation is taken from here:
      https://gist.github.com/tprynn/5419da1a2ad8935c1fff
    And the rc4 implementation is taken from here and modified:
      https://github.com/caiges/Ruby-RC4/blob/082fce56ab707dc77442709357cf176f7b3b6f22/lib/rc4.rb
    
    Fixes WinRb#49
    larskanis committed Jun 24, 2022
    Configuration menu
    Copy the full SHA
    f666786 View commit details
    Browse the repository at this point in the history

Commits on Jun 27, 2022

  1. Add CI run on OpenSSL-3.0

    ... which is the default on ubuntu-22.04.
    OpenSSL-3.0 has some limitations regarding outdated algorithms.
    larskanis committed Jun 27, 2022
    Configuration menu
    Copy the full SHA
    c56f474 View commit details
    Browse the repository at this point in the history

Commits on Jun 6, 2024

  1. Configuration menu
    Copy the full SHA
    f5cb761 View commit details
    Browse the repository at this point in the history