oqs-test/try_connection.py tests what is in the README.

[xvzcf]

No description provided.

[baentsch]

Please check the specific comments above.
Generally, using the regress data works, of course; but I'd then also suggest adding that

• host and client keys can be separately generated using ssh-keygen
• configuration options (like port etc.) can either be set on the command line or in the respective ssh_config and sshd_config files in the regress folder.

Also, if the whole build documentation is reduced to running the build scripts, I'd suggest adding that "PREFIX" can be set to facilitate a specific oqs-openssh install location: I can't imagine someone trying this will want to replace their system-wide ssh right away :-)

[xvzcf]

Generally, using the regress data works, of course; but I'd then also suggest adding that

* host and client keys can be separately generated using `ssh-keygen`

Added a brief note about this.

* configuration options (like port etc.) can either be set on the command line or in the respective `ssh_config` and `sshd_config` files in the `regress` folder.

Same here.

Also, if the whole build documentation is reduced to running the build scripts, I'd suggest adding that "PREFIX" can be set to facilitate a specific oqs-openssh install location: I can't imagine someone trying this will want to replace their system-wide ssh right away :-)

The oqs-scripts/build_openssh.sh script already has an INSTALL_PREFIX variable, set by default to a non-system location. The README instructions (and the test scripts) however don't use this install location, and simply use the default location of the built artifacts.

[baentsch]

Thanks for the updates. LGTM.