When Microsoft, and later Google decided to update their SSL/TLS to use the
latest versions of both, we at the copier company I work for did not have the
luxury of saying that we couldn't ask our customers to update the software on
their copiers. We had to send technicians out and do it. When ma
Dan Friedman wrote:
> Later versions are simply more stable. Period.
Agreed, and I think that was Fraser's point. v8.0.2 has some 2000+
fixed and enhancements not found in v7.0.1.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
Dan Friedman wrote:
> Other than this issue, LC 7.0.1 is working well. Can you offer any support
> for this issue with 7.0.1? Or, do I just set libURLSetSSLVerification to
> false and hope for the best?
If you’d like to stay on LC 7.0.1, then to avoid the SNI bug, you’ll need to
ensure that
Dan Friedman wrote:
> I purchased a SSL certificate and installed it and set it as the default. It
> is working fine in every browser I try. However, in LiveCode (7.0.1), it's
> getting the previous self-signed SSL certificate and failing with this error:
It’s possible that you’re running in
Fraser,
Mainly, I can't ask thousands of people to reinstall my application at this
time. Also, I can't take the risk of rolling out a *new* version of LC. I've
done that in the past and it has cost me clients. With all new versions of
LC, there are known bugs, and unknown bugs. You and I
On 15/08/16 18:32, Dan Friedman wrote:
Lastly, it works fine in LC 8 (but for a verity of reasons, I can't use LC 8)
What is it that is causing you problems in LiveCode 8?
Other than that, why not use a newer version of LiveCode 7? 7.0.1 is
nearly 2 years old and there have been a huge numbe
Greetings!
I had a self-signed SSL certificate on my server (a generic certificate that
came with the server). I purchased a SSL certificate and installed it and set
it as the default. It is working fine in every browser I try. However, in
LiveCode (7.0.1), it's getting the previous self-sig
