Lines Matching +full:engine +full:- +full:specific

14 First checkout the `PYCA/Cryptography` module into `./pyca-cryptography` using:
16     $ git submodule update --init
20     $ ./config enable-external-tests
29 ------------------------------
44 krb5's master has to pass this same CI, but a known-good version is
45 krb5-1.15.1-final if you want to be sure.
48     $ git checkout krb5-1.15.1-final
53     $ ./config enable-external-tests
61 Test-failures suppressions
62 --------------------------
68 GOST engine test suite
71 Much like the PYCA/Cryptography test suite, this builds and runs the GOST engine
74 You will need a git checkout of gost-engine at the top level:
76     $ git submodule update --init
80     $ ./config enable-external-tests
83 GOST engine requires CMake for the build process.
85 GOST engine tests will then be run as part of the rest of the suite, or can be
94 (OpenQuantumSafe -- www.openquantumsafe.org) provider tests against the
99     $ git submodule update --init
103     $ ./config enable-external-tests
113 The names of all supported quantum-safe algorithms are available at
114 <https://github.com/open-quantum-safe/oqs-provider#algorithms>.
116 Please note specific limitations of oqsprovider operations dependent on specific
118 <https://github.com/open-quantum-safe/oqs-provider#note-on-openssl-versions>.
120 pkcs11-provider test suite
123 This builds and runs pkcs11-provider tests against the local OpenSSL build.
125 You will need a git checkout of pkcs11-provider at the top level:
127     $ git submodule update --init
131     $ ./config enable-external-tests
134 pkcs11-provider requires meson for the build process. Moreover, it requires
135 softhsm and nss softokn tokens and certtool, certutil, pkcs11-tool and expect
144 ------------------------------
146 There are tests for different software tokens - softhsm, nss-softokn and kryoptic.
154 - Make sure the submodules are cloned locally:
156     $ git submodule update --init --recursive
158 - Enter subdirectory and pull from the repository (use a specific branch/tag if required):
160     $ cd `<submodule-dir>`
163 - Go to root directory, there should be a new git status:
168       #       modified:   `<submodule-dir>` (new commits)
171 - Add/commit/push the update
173     $ git add `<submodule-dir>`
174     $ git commit -m `"Updated <submodule> to latest commit"`