Rc 1.1.19

[semuadmin]

pygnssutils Pull Request Template

Description

1. Add support for TLS connections in SocketServer. Introduces two alternative client request handler classes - ClientHandler (HTTP) or ClientHandlerTLS (HTTPS). TLS operation requires a suitable TLS certificate/key pair (in pem format) to be located at a path designated by environment variable PYGNSSUTILS_PEMPATH - the default path is $HOME/pygnssutils.pem. See Sphinx documentation for details.

   A self-signed pem file suitable for test and demonstration purposes can be created thus:

   openssl req -x509 -newkey rsa:4096 -keyout pygnssutils.pem -out pygnssutils.pem -sha256 -days 3650 -nodes

2. Additional --cliout option OUTPUT_SOCKET_TLS (6) added to gnssserver, gnssstreamer, gnssntripclient and gnssmqttclient cli utilities (remember to set PYGNSSUTILS_PEMPATH), e.g.:

   gnssstreamer -P /dev/tty.usbmodem101 --format 2 --cliout 6 --output '0.0.0.0:8443' --verbosity 2

Testing

Please test all changes, however trivial, against the supplied pytest suite tests/test_*.py. Please describe any test cases you have amended or added to this suite to maintain >= 99% code coverage.

• Test A
• Test B

Checklist:

• I agree to abide by the code of conduct (see CODE_OF_CONDUCT.md).
• My code follows the style guidelines of this project (see CONTRIBUTING.md).
• I have performed a self-review of my own code.
• (if appropriate) I have cited my u-blox documentation source(s).
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• (if appropriate) I have added test cases to the tests/test_*.py unittest suite to maintain >= 99% code coverage.
• I have tested my code against the full tests/test_*.py unittest suite.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I have signed my commits.
• I understand and acknowledge that the code will be published under a BSD 3-Clause license.