* Start from the upstream SPEC file.
* Use the %{name} macro instead of explicitly repeating openresty-voms
* Use system zlib, openssl and pcre dependencies and do not specify minimum
  versions
* Remove unused macros oroprefix, {zlib,pcre,openssl}_prefix
* The voms_module_prefix macro is assumed
* Mv-ing openresty binary in openresty-voms seems irrelevant
* Don't consider "tapset" files, they don't exist (any more)
* For debug builds use -Og
* Review the packaging script
  - Minimize the list of build-time packages to install
  - Set the voms_module_prefix macro in the .rpmmacros file. The prefix is
    on the command line, with a default
  - Build only the optimized RPM
* Start docker:dind with --tls=false to avoid timeouts during CI

Issue #17

CentOS provides gcc 4.8.5, which has a decent support for C++14
features, enabled with -std=c++1y.

In this way we don't need to bring in the devtoolset software
collection.

Conflict is set against any version of openresty.

In particulare the one in certs shows concrete examples on how to
generate VOMS proxies

The proxies had a wrong VO in the FQANs and couldn't be validated any
more by the VOMS lib. See commit
https://github.com/italiangrid/voms/commit/feeaed

encoding.t was also affected, but didn't require any change, just a
correctly generated proxy.

Apparently the bug mentioned in the (removed) comment has been fixed.
But this showed a bug in our test: http vs HTTP in the pattern to match
in the log.

Issue #17

Refactored openresty-voms docker image

See merge request storm2/ngx_http_voms_module!17

Issue 22

See merge request storm2/ngx_http_voms_module!16

Check it's an SSL request before dereferencing the ssl field of a connection

Closes #26

See merge request storm2/ngx_http_voms_module!15

fix issue #26

Note that This test is always successful because, for some reason
(a bug?) the error.log as seen in Test::Nginx doesn't contain the
entries for the master process, although they are evailable in
the actual file. As a consequence the no_error_log check is
always satisfied, even if the segmentation fault were present

Actual fix for issue-23

See merge request storm2/ngx_http_voms_module!14

And related test.

Do not return CA certificates as the EEC

See merge request storm2/ngx_http_voms_module!13

When the client certificate chain contains a CA certificate, the
ngx_http_voms_module returns that one as the EEC.

This fix should resolve that issue.

Issue: https://baltig.infn.it/storm2/ngx_http_voms_module/issues/23

[ngx-voms] configure openssl to accept proxy certs

Closes #19

See merge request storm2/ngx_http_voms_module!12

fix issue #19

avoid dangling pointer (to a destroyed temporary)

Closes #20

See merge request storm2/ngx_http_voms_module!11

fix issue #20

* issue-16:
  initialize result
  review
  reorder code
  format

* issue-16:
  Tentative support for ssl_client_ee_cert

cache and clean the VOMS AC only once per connection

Closes #15

See merge request storm2/ngx_http_voms_module!10

ngx-voms docker image

See merge request storm2/ngx_http_voms_module!9