Any tries to stream media from https fails with TLS plugin not available error (see message log here)
Whereas, trying the same stream using Win32 VLC version (also 2.1.5) succeeds (see message log here.
Is there a reason why x64 VLC version does not support encrypted connections?
Windows 8.1, VLC 2.1.5
It's due to a bug. In VLC 3.0.0, the latest nightly build, there appears to be no problems streaming videos that require TLS. You can find it here if interested: http://nightlies.videolan.org/build/win64/vlc-3.0.0-20150203-0441/
Note that because it's an unstable build there may be other issues.
Related
I am new to ISIS.
When I run the ./qview application
the following error display.
[libprotobuf FATAL google/protobuf/stubs/common.cc:68] This program requires version 3.9.0 of the Protocol Buffer runtime library, but the installed version is 3.5.1. Please update your library. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".)
terminate called after throwing an instance of 'google::protobuf::FatalException'
what(): This program requires version 3.9.0 of the Protocol Buffer runtime library, but the installed version is 3.5.1. Please update your library. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "google/protobuf/any.pb.cc".)
Aborted (core dumped)
I am wondering why I am getting this error. Please help.
Many applications have known security or stability issues if you link them against old versions of libraries. This is a common issue when building from source rather than downloading a precompiled container, because you often have to upgrade the versions of a dozen libraries that were previously installed on your system, but are not at the most current revision level. For example, perhaps the newer versions of google’s GRPC library has some feature that was not supported in older versions, and Isis cannot be used without this feature because it requires it. By trying to compile against an old version of the library on which it depends, you end up with a broken qview application, but luckily for you, it self diagnosed the issue and tells you exactly what went wrong.
So, you need to upgrade to the new version of the GRPC library, then rebuild it, then rebuild Isis. Alternatively, download a container or VM that has the entire system already built for your computer architecture and operating system.
I want to play around with the QtCOAP plugin. Unfortunately the DTLS support is missing on my OS-X Catalina. All I got is this error:
qt.coap.connection: DTLS is disabled, falling back to QtCoap::NoSecurity mode.
I have fully installed Qt 5.14.1 (with sources) with the online installer and compiled the COAP Plugin afterwards by myself with the prebuilt qmake.
The DTLS specific parts in the QtCoap code are wrapped within #if QT_CONFIG(dtls) (qcoapqudpconnection_p.h) blocks. Which seems to be evaluated to false.
What can I do to enable DTLS support?
From a quick look at the sources, it seems that DTLS is currently only available using OpenSSL. By default Qt is built using the SecureTranport framework on macOS which is the official cryptographic library for that OS.
You can rebuild the qtbase module to use OpenSSL instead but ensure to install the latest version of the 1.1 series.
You can use either macports or brew to get OpenSSL.
I have downloaded WSO2 IoT server version 3.0.0, and followed all the instructions to run the product on Windows 10 machine with JDK 1.8 installed. Everything was going fine until I tried to download virtual fire alarm device agent.
Simple, it was not working, and a blank page with no response was all that I have got. Then I tried the same for a Raspberry Pi device, and again the device agent failed to be downloaded. It is interesting that this bug was reported for Alpha and 3.1.0 product versions, so it seemed that the current official version is free from this.
Do you have any explanation of this ill behavior (it doesn't seem to me that anything is missing in the documentation)?
My app uses NSURLConnection to post an xml file to a financial organization in my country that will at some point next year stop using SSL protocols and switch to TLS 1.1 or 1.2.
My app is linked to 10.6 SDK as many of my clients use older systems. There are several questions I like to ask and I am not sure how this all affects me.
Does it matter to what SDK am I linked? If my app is used on latest Mac OS will NSURLConnection use latest TLS by default? How do I test the TLS version on a system?
Should I link to the newer SDK? Or just tell affected clients to upgrade to Mountain Lion or newer?
The problem is I can't test anything now as the organization in question just announced that at some point in 2016. they'll stop support for anything less than TLS 1.1.
No need to keep yourself confined to an ancient version of Xcode (I think Xcode 3?), what you can do is use the latest version of Xcode and
1)
specify MacOS 10.6 as the "minimum deployment version"
(honestly, in my opinion, you should only support 1 - 3 MacOS versions back... MacOS 10.6 dates from 2011).
2)
And make sure to use app transport security exceptions to allow for older TLS under MacOS 10.11 and newer MacOS versions.
Apple will happily support TLS 1.2 going forward. If you still need to support TLS 1.1, that'll still require an exception in the app's info.plist file.
I do have the FortiGate client installed and it is not disabled. It worked until I upgraded Firefox to version 22. How do I get this to work with the new version?
This a known bug related to Firefox issue. SSl vpn client plugin's would not work if you are running Firefox version higher then 20 Reference to bug id (0211153).The purposed workaround at this time would be to download stand alone sll vpn client.Please see the link given below for downloading stand alone ssl vpn or go back on a previous version (like 21)
Download SslvpnClient.msi from http://dekiwiki.ties2.net/Fortinet/Fortinet_SSL_VPN_Client_Installers