* Add OpenSSL 3 fixes
* Add Ubuntu Jammy to CI

* Debian package CI tools

* Prepare release 1.0.11

* Initial Github action end-to-end testing
* Github Action fixups

This PR addresses includes the changes provided in #46 and #47 but add the necessary logic to have the Caml Crush code compatible with TIRPC has some implementation details had changed.
In addition, this introduces a way to perform end-to-end testing using docker-compose and should allow for better future-proofing and better backward compatibility testing.

* Port the code to use safe strings only
* build: Remove the unsafe-strings flag
* Use tirpc as RPC implementation if available
* Fix generated IDL patch with recent versions of camlidl as some functions
renaming prevent spatch (coccinelle) from performing its semantic patch on
the pkcs11_stub.c
* Put back compatibility with OCaml < 4.02 where the Bytes module is not present.
This is achieved through preprocessing.
* Refresh IDL and RPC generated headers and files with more recent versions of
camlidl and rpcgen. This can be useful for people who do not want to activate
--with-idlgen and/or --with-rpcgen.
* Initial integration tests using Docker
* Implement tirpc fixes for OpenSSL
* Propagate the binding patches to the standalone mode.
* Add UNIX socket integration tests and more tirpc fixes

Co-authored-by: Simon Chopin <simon.chopin@canonical.com>
Co-authored-by: Ryad Benadjila <ryadbenadjila@gmail.com>

Fix GCC10 compilation

ci: name travis jobs properly

upstream modifications.

We identified a regression of the behavior in coccinelle in newer version and were unable to have an identical fix for all versions of spatch.
Therefore two version of the coccinelle will be distrubuted for backward and hopefully future compatibility versions.

Credits: Ryad Benadjila <ryadbenadjila@gmail.com>

* CI: Attempt docker build

* CI: Switch to full Docker builds

* CI: Use several scripts to check each docker progress

* CI: Use several scripts to check each docker progress v2

* CI: Use several scripts to check each docker progress v3

Fix Trusty legacy non TLS build, undefined X509

* Integrate with Travis CI for continuous builds.
* Disable Trusty build, SSL support will be disabled because of issues with old versions.

Merging previous PRs into the upstream repository

Various fixes.

First attempt to provide a Mingw cross-compilation Makefile for the client library.

the case Ocamlnet < 4.

authentication ('peer_auth=required'). We use the 'verify' hook of the Netplex_config
read_tls_config function in order to bypass the peer name verification.

We also use this hook to finaly add the certificate white list verification feature
that had not been migrated when moving from Ocamlnet < 4 to new versions (OpenSSL to
new TLS bindings).

Some code refactoring between the SSL and the LEGACY_SSL has also been performed.

OCaml 4.0.2, that is mainly an alias of the String module.
Replacing String by Bytes as it was done in commit 922580275caeec15173517cef4f1914c491593d7
introduces a regression for older versions of OCaml with compilation errors.

TODO: handle the camlp4 definition in the configure.ac file to handle the conditional
aliasing of the Bytes module depending on the OCaml version.
For now, the project should compile in all versions by emitting warning when OCaml >= 4.0.2.

be replaced by Bytes.create and Bytes.set).

(default behaviour of recent gcc is to treat default fallthrough as a warning).

client library.

This Makefile supposes:

1) That i686-w64-mingw32 and x86_64-w64-mingw32 cross-compilation toolchain are
both installed on the system.

2) That the oncrpc-win32 includes and 32-bit/64-bit libraries have been compiled
or downloaded in the relative paths: oncrpc-win32/win32/include for the includes,
../oncrpc-win32/win32/bin32/oncrpc.lib for the 32-bit oncrpc static library, and
../oncrpc-win32/win32/bin64/oncrpc.lib for the 64-but oncrpc static library.

3) The the OpenSSL includes and 32-bit/64-bit libraries have been compiled
or downloaded in the relative paths: ../openssl-1.1.0f/include for the includes,
../openssl-1.1.0f/win32/libssl.a for the 32-bit libssl static library,
../openssl-1.1.0f/win32/libcrypto.a for the 32-bit librcypto static library,
../openssl-1.1.0f/win64/libssl.a for the 64-bit libssl static library, and
../openssl-1.1.0f/win64/libcrypto.a for the 64-bit libcrypto static library.

The Makefile 'Makefile.Win32.mingw' can be adapted to only compile and use 32-bit
or 64-bit binaries. i686-w64-mingw32 and x86_64-w64-mingw32 and other elements
(such as the CamlCrush client libname and socket) are hardcoded: improving and
cleaning the Makefile to be more flexible and adapt to other systems are future
work.

Launching the standalone compilation of the client library is as easy as
(from the CamlCrush project root folder):
$ cd src/client-lib
$ make -f Makefile.Win32.mingw

This should produce:
libp11client_32.dll => the 32-bit client library WITHOUT the SSL support.
libp11client_32_ssl.dll => the 32-bit client library WITH the SSL support.
libp11client_64.dll => the 64-bit client library WITHOUT the SSL support.
libp11client_64_ssl.dll => the 64-bit client library WITH the SSL support.

This version have been tested against:
- The oncrpc library compiled with Mingw, see:
  https://github.com/calderonth/oncrpc-win32
- OpenSSL in version 1.1.0f compiled with Mingw (see the NOTES.WIN file
section "GNU C (MinGW/MSYS)" at the root folder of the project).

Even though it has not been tested, the current Makefile.Win32.mingw should
also work with static libraries for oncrpc and OpenSSL compiled with other
Win32/Win64 compatible compilers (such as Visual C++).

For most of the sensitive keys (private and secrets keys), the sensitive
attribute is a CKA_VALUE type. However, this is not true for RSA keys that do
not have such an attribute, and for which other attributes must be filtered
(namely CKA_PRIME_1, ...).

[Credits for finding the bug: Roman Cinkais]

release: Prepare release 1.0.8, closes #23

The main changes has been made to the readnet and writenet functions that handle
SSL hooking at the RPC level. The writenet function is roughly the same as in the
*NIX case, while the readnet one must handle timeout and is adapted to WIN32.

This has been tested with OpenSSL compiled for Windows in 32 and 64 bits flavors.

macro. OpenSSL version detection should now work.