[crypto] Use Cryptodome namespace instead of Crypto PyCryptodome comes in two flavors: “an almost drop-in replacement for the old PyCrypto library” and “a library independent of the old PyCrypto”. The former uses the Crypto namespace, and is shipped as `pycryptodome` while the latter uses Cryptodome instead and lies in the `pycryptodomex` package. Given the reason to switch to PyCryptodome is that PyCrypto in unmaintained, its probably better to avoid any mistake and mandate the specific usage of the Cryptodome namespace by requiring `pycryptodomex` instead of `pycryptodome`. A more present reason is that Debian buster will only provide a package with the separate namespace flavor. The current Recommends is not working with the current code. Although it's important to note that the package name will probably have to be changed to `python3-pycryptodomex` once https://bugs.debian.org/886291 is solved.

     1

Additional services

     2

===================

     3

     4

In this chapter, we introduce services crossing the *web -

     5

repository - administration* organisation of the first parts of the

     6

CubicWeb book. Those services can be either proper services (like the

     7

undo functionality) or mere *topical cross-sections* across CubicWeb.

     8

     9

.. toctree::

    10

   :maxdepth: 2

    11

    12

   undo

    13

    14