You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Standards/scs-0125-v1-secure-connections.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -271,7 +271,7 @@ See the [corresponding Design Considerations section](#libvirt-hypervisor-interf
271
271
Conformance tests are limited to communication channels exposed to users, such as the public API interfaces.
272
272
Internal channels and APIs are currently not part of the automated conformance tests because they are not exposed and cannot be audited without direct access to the infrastructure.
273
273
274
-
There is a test suite in [`tls-checker.py`](../Tests/iaas/secure-connections/tls-checker.py).
274
+
There is a test suite in [`tls-checker.py`](https://github.com/SovereignCloudStack/standards/blob/main/Tests/iaas/secure-connections/tls-checker.py).
275
275
The test suite connects to the OpenStack API and retrieves all public API endpoints from the service catalog.
276
276
It then connects to each endpoint and verifies the compliance to the standard by checking SSL/TLS properties against the Mozilla TLS preset.
277
-
Please consult the associated [README.md](../Tests/iaas/secure-connections/README.md) for detailed setup and testing instructions.
277
+
Please consult the associated [README.md](https://github.com/SovereignCloudStack/standards/blob/main/Tests/iaas/secure-connections/README.md) for detailed setup and testing instructions.
0 commit comments