Skip to content
This repository was archived by the owner on Mar 10, 2026. It is now read-only.
This repository was archived by the owner on Mar 10, 2026. It is now read-only.

RFE: Add option to choose allowed TLS versions #5119

Closed

Description

@zdohnal

Hi,
I'm currently working on this RFE for our customer. Desired outcome will be similar like in mod_ssl module for httpd - cupsd could choose how strong ciphers will be used for encryption - options will be something like these: LOW-MEDIUM-HIGH.
Do you want to add this feature to CUPS, when I send the patch?

Activity

  1. michaelrsweet commented on Sep 24, 2017

    @michaelrsweet
    Contributor

    First, only one of the TLS libraries supported by CUPS (GNU TLS) offers this sort of support. The macOS security framework has very low level control (which we use in some cases) and the Windows security provider interface doesn’t allow applications any direct control. Both macOS and Windows limit supported ciphers by default to those that are either considered secure or are required for interoperability.

    Second, the SSLOptions directive in client.conf and cupsd.conf already provides specific options to allow low security ciphers for interop (AllowRC4 and AllowDH) and deny cipher suites and versions that are being phased out (DenyCBC and DenyTLS1.0). Conceptually you could add generic “BestSecurity” and “BestCompatiblity” options, however I have my concerns about options that can change behaviour across releases.

    But finally I have never liked these mod_ssl (really OpenSSL) options since the definitions of LOW, MEDIUM, and HIGH are not clear and vary not based on the application version but on the library version in use. All of the security focused guides therefore provide an explicit list of cipher suites and TLS versions and not the low, medium, or high pseudo settings.

    The default for CUPS is a balance between compatibility and security.

  2. michaelrsweet commented on Sep 24, 2017

    @michaelrsweet
    Contributor

    So to answer your question, it will depend. Just supporting what mod_ssl does will be rejected. Doing something better will be considered.

  3. zdohnal commented on Sep 25, 2017

    @zdohnal
    ContributorAuthor

    Ciphers, which customer consider as medium strong, are part of TLS 1.0 and use CBC, so DenyCBC and DenyTLS1.0 should work. But what about TLS 1.1? It uses same ciphers as TLS 1.0 (that's how I understood it), so what about adding option DenyTLS1.1, which will make CUPS to use TLS 1.2?

  4. added
    enhancementNew feature or request
    and removed
    questionGeneral usage question
    on Sep 25, 2017
  5. added this to the milestone on Sep 25, 2017
  6. michaelrsweet commented on Sep 25, 2017

    @michaelrsweet
    Contributor

    TLS 1.1 has other differences from TLS 1.0, and the set of ciphers is not generally limited by the TLS version (each TLS version has one or more required cipher suites, but any version can generally implement any cipher suite).

    I can see maybe adding a DenyTLS1.1 directive, but perhaps for future proofing we should start using "MinTLS" options instead since TLS 1.3 is all but done and that syntax would be forward-looking.

  7. changed the title [-]RFE: Add option to choose how strong ciphers will be used for encryption [/-] [+]RFE: Add option to choose allowed TLS versions[/+] on Sep 25, 2017
  8. zdohnal commented on Sep 25, 2017

    @zdohnal
    ContributorAuthor

    MinTLS directive sounds reasonable. Let's go with that.

  9. hardfalcon commented on Oct 16, 2017

    @hardfalcon
    Contributor

    @michaelrsweet:

    First, only one of the TLS libraries supported by CUPS (GNU TLS) offers this sort of support. The macOS security framework has very low level control (which we use in some cases) and the Windows security provider interface doesn’t allow applications any direct control.

    It seems this only applies to the old CryptoAPI on Windows. If you use "Cryptography API: Next Generation" (CNG), it seems to be possible to add and remove single ciphersuites for a connection without having to fiddle with the registry:
    https://msdn.microsoft.com/en-us/library/windows/desktop/bb870930(v=vs.85).aspx
    CNG is supported on Windows Vista / Server 2008 and newer.
    I've never used neither CryptoAPI nor CNG myself, though.

  10. zdohnal commented on Oct 23, 2017

    @zdohnal
    ContributorAuthor

    Should MinTLS be complementary to SSLOption directive? Or can be there conflicts between these to directives? To sum it up - what relationship will MinTLS and SSLOptions have?
    I created patch for cups in RHEL 7 for now, where cups is built with openssl. Patch introduces new option for SSLOption directive - DenyTLSv1.1, because I didn't know possible relations between SSLOption and MinTLS directives. When I will have time (at beginning of November), I can rewrite it for GNUTLS (I am not familiar of Mac or Windows encrypting libraries), if you are interested.

  11. michaelrsweet commented on Oct 23, 2017

    @michaelrsweet
    Contributor

    MinTLS will be an SSLOptions value, as an alternative to adding a bunch more DenyTLS#.# or AllowTLS#.# options.

  12. zdohnal commented on Oct 23, 2017

    @zdohnal
    ContributorAuthor

    So there will be SSLOptions values like MinTLS1.0, MinTLS1.1, MinTLS1.2, if I understood correctly?

  13. michaelrsweet commented on Oct 23, 2017

    @michaelrsweet
    Contributor

    Yes

  14. zdohnal commented on Oct 23, 2017

    @zdohnal
    ContributorAuthor

    Ok, thank you, Mike.

  15. michaelrsweet commented on Nov 3, 2017

    @michaelrsweet
    Contributor

    [master 8f1fbde] Add support for MinTLS and MaxTLS options (Issue #5119)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions