Warning during update command

[ollihoo]

During the start of an update in yadtshell there was a warning (see below). What do I have to do to fix this warning?

`

## /etc/yadtshell/targets/... $ update host://hamgac*

/usr/lib64/python2.6/site-packages/twisted/internet/_sslverify.py:184: UserWarning: You do not have the service_identity module installed. Please install it from https://pypi.python.org/pypi/service_identity. Without the service_identity module and a recent enough pyOpenSSL tosupport it, Twisted can perform only rudimentary TLS client hostnameverification. Many valid certificate/hostname mappings may be rejected.
verifyHostname, VerificationError = _selectVerifyImplementation()
/usr/lib64/python2.6/site-packages/twisted/internet/_sslverify.py:184: UserWarning: You do not have the service_identity module installed. Please install it from https://pypi.python.org/pypi/service_identity. Without the service_identity module and a recent enough pyOpenSSL tosupport it, Twisted can perform only rudimentary TLS client hostnameverification. Many valid certificate/hostname mappings may be rejected.
verifyHostname, VerificationError = _selectVerifyImplementation()
`

[mriehl]

Hi @ollihoo ,

This is actually a packaging issue. The state of affairs is as follows:

• The library (twisted) that is used for internal HTTP communication between yadtcontroller, yadtreceiver, yadtbroadcaster and yadtshell is SSL-capable (but we do not use SSL)
• The library needs additional dependencies for exhaustive SSL certificate validation

The warning you are seeing could be dealt with using any of the approaches below:

• Package the modules required for exhaustive SSL certificate validation - this will disable the warning. This should be done by the people who packaged your version that produces this warning.
• Use the warnings module to disable the warning. This would be an applicative change (in this repository) but I don't agree with it, since SSL will probably be used at some point.
  I know that you don't care about SSL as an end user but if it was to be used at some point then certificate validation would probably cause strange errors and it would be difficult to understand where these errors stem from.

What I (as a maintainer) can do for you is silence the warning. But as stated above, I don't think it's the correct solution. What are your thoughts?