This is a tricky issue.

I recognize there is a need in some places for this as a workaround. However this is a highly insecure workaround. It should not be enabled by default, and it should require more than just a flag from the user to turn it on.

If we're going to take this, it should probably include a builder setting that governs whether the user is allowed to specify this.

Good point @mikem. I've added a builder setting for it.
Though, should the build fail if the user uses the option and it's not allowed, or should it simply ignore the input?

In the case where the user specifies noverifyssl, but the builder is configured not to allow it, it seems like we should error rather than silently dropping the option. The naming of the option implies this behavior, plus it's confusing to the developer to have their option silently dropped.

Otherwise the patch looks fine

@mikem @tkopecek thanks, updated the PR.

:thumbsup:

Commit d5d7c1ac fixes this pull-request