[mythtv] 'Couldn't create VideoOutput instance. Exiting..

John Pilkington johnpilk222 at gmail.com
Mon Feb 3 11:34:30 UTC 2020


On 03/02/2020 09:46, John Pilkington wrote:
> On 03/02/2020 01:19, Mark Perkins wrote:
>>
>>
>>      >
>>      > There may be some delay.  I'm suddenly getting an sslv3 alert
>>     handshake
>>      > failure in the build script.  It looks as if curl, used by
>>     spectool, has
>>      > got fussy.
>>      >
>>
>>     No joy with the rpms yet.  I've filed
>>
>>     https://bugzilla.redhat.com/show_bug.cgi?id=1797256
>>
>>     _______________________________________________
>>
>>
>>     Are you sure that curl is the issue? As I understand it the (very
>>     strong?) recommendation is that sites should refuse connections via
>>     SSLv2, SSLv3 or TLSv1.0, irrespective of client request.
>>
>>     Perhaps the site hosting the rpm files has been updated accordingly?
>>
>>     What happens if put url in https://www.cdn77.com/tls-test
> 
> 
> Yes, I was beginning to realise that handshakes are two-sided.  It's 
> trying to download the MythTV tarball from codeload.github.com, and 
> spectool appears to be configured to use curl in --insecure mode.
> 
> In fact by that stage in the script I already have what appears to be 
> that tarball, but so far I haven't succeeded in dropping it into the 
> right place to continue the build.

Hmm.  https://www.cdn77.com/tls-test said the site had TLS 1.3, but with 
/etc/rpmdevtools/curlrc holding --tlsv1.3 and --verbose I get

*     CAfile:  /etc/pki/tls/certs/ca-bundle.crt
    CApath none

TLSv1.3 (IN), TLS alert, handshake failure (552):

followed by the original sslv3 handshake failure...  Do I need to 
specify ciphers etc?

Thanks,

John



More information about the mythtv-dev mailing list