Secure sockets problem... any update?
bobsneidar at iotecdigital.com
Mon Aug 8 15:54:48 EDT 2016
If the issue is SSL 4.0 vs 3.0 or TLS 1.2 vs. 1.0, it all goes back to the heartbleed exploit and the countermeasures for that.
> On Aug 8, 2016, at 11:56 , Richard Gaskin <ambassador at fourthworld.com> wrote:
> Stephen MacLean wrote:
> > Hi Richard,
> > Thanks for adding yourself to the CC list on this bug:)
> It's an important bug, very much looking forward to following its progress. Thank you for providing a link to it here.
> > I think you may be reading the post from Panos with the wrong date
> > though, understandable given all of us being on EU date format the
> > last week with the conference.
> > Panos confirmed it on Feb 2 (2016-02-08) and changed it to "Expert
> > Review” then. My “Any update” post on the bug report was on Aug 6
> > (2016-08-06).
> Yes indeed, I was quite mistaken. Thanks for drawing my attention to that. I had glanced near the top of the report and misread the order of the date elements, completely overlooking the light-gray date on Panos' post.
> That your "tickle" of the report came only after a very patient waiting period is not surprising; you've always seemed a patient person.
> It's just so rare these days that something of this significance remains outstanding for that long that I was clearly over-confident about the follow-up there.
> With the recent tickle, fingers crossed it'll get some love shortly.
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> Ambassador at FourthWorld.com http://www.FourthWorld.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode