Skip to content
This repository has been archived by the owner on Feb 18, 2022. It is now read-only.

Fix support for no verify #26

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

alex-harvey-z3q
Copy link
Contributor

On RHEL 7, which has Stunnel version 4.56, we found that a different
configuration was required.

Instead of specifying verify = default, it is in fact necessary to
simply not specify verify at all.

Without this patch applied, an error message is seen:

"verify = default": Bad verify level

On RHEL 6, Stunnel version 4.29 is available and it behaves differently,
but it also allows verify to simply be not specified.

Therefore, this patch modifies templates/stunnel.conf.erb to simply not
add the verify line if verify level default is specified.

On RHEL 7, which has Stunnel version 4.56, we found that a different
configuration was required.

Instead of specifying verify = default, it is in fact necessary to
simply not specify verify at all.

Without this patch applied, an error message is seen:

  "verify = default": Bad verify level

On RHEL 6, Stunnel version 4.29 is available and it behaves differently,
but it also allows verify to simply be not specified.

Therefore, this patch modifies templates/stunnel.conf.erb to simply not
add the verify line if verify level default is specified.
Before this, the Travis build was failing with:

    Using rake 12.0.0
    Gem::InstallError: public_suffix requires Ruby version >= 2.0.
    An error occurred while installing public_suffix (2.0.5), and Bundler
    cannot

Considering that Ruby 1.9.3 is very very old now, it seems to make sense
to simply remove it from .travis.yml, which is what this patch does.
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants