requirements: pynacl is no longer needed

This is obsolete by now.

Signed-off-by: Jussi Kukkonen <[email protected]>

Author: jku

docs/INSTALLATION.rst

@@ -25,14 +25,13 @@ algorithms, and more performant backends. Opt-in is available via
 
 .. note::
 
-   Please consult with underlying crypto backend installation docs --
-   `cryptography <https://cryptography.io/en/latest/installation/>`_ and
-   `pynacl <https://pynacl.readthedocs.io/en/latest/install/>`_  --
+   Please consult with underlying crypto backend installation docs. e.g.
+   `cryptography <https://cryptography.io/en/latest/installation/>`_
    for possible system dependencies.
 
 ::
 
-   python3 -m pip securesystemslib[crypto,pynacl] tuf
+   python3 -m pip securesystemslib[crypto] tuf
 
 
 Install for development

requirements/main.txt

@@ -6,5 +6,5 @@
 # 'pinned.txt' is updated on GitHub with Dependabot, which
 # triggers CI/CD builds to automatically test against updated dependencies.
 #
-securesystemslib[crypto, pynacl]
+securesystemslib[crypto]
 requests

tox.ini

@@ -34,7 +34,7 @@ allowlist_externals = python3
 # Must to be invoked explicitly with, e.g. `tox -e with-sslib-main`
 [testenv:with-sslib-main]
 commands_pre =
-    python3 -m pip install --force-reinstall git+https://github.com/secure-systems-lab/securesystemslib.git@main#egg=securesystemslib[crypto,pynacl]
+    python3 -m pip install --force-reinstall git+https://github.com/secure-systems-lab/securesystemslib.git@main#egg=securesystemslib[crypto]
 
 commands =
     python3 -m coverage run aggregate_tests.py