Thanks for confirming it Mark. I feel like a sucker. I started on this project a few months ago on the assumption that socket certificates now worked as they'd been included in the Dictionary for years. I was away from development for a few years and hadn't noticed the complaints that the Dictionary was misrepresenting the situation. Depressing to see my own name in that bug report from 7 years ago, pointing out that secure sockets with certificates was something that we'd been told was on the horizon in LC version 2, which must have been around 2004.
https://quality.livecode.com/show_bug.cgi?id=13410 Regards, Bernard On Wed, Jan 27, 2021 at 12:57 AM Mark Wieder via use-livecode < email@example.com> wrote: > On 1/26/21 6:05 AM, Bernard Devlin via use-livecode wrote: > > > Is it really the case that for the past 6 years LC documentation has been > > misleading people concerning the implementation of certificates for > secure > > socket connections? > > Sadly, yes. > > > > > I notice in the Dictionary the entry for "open socket" in the table of > > options for this command has entries for "certificate" and "key", but > these > > are both empty. As if these features were meant to be implemented but > were > > never implemented and the Dictionary was never updated to remove this > > misleading information. > > > > I just find that hard to believe. > > https://quality.livecode.com/show_bug.cgi?id=13410 > > although the earliest bug report seems to be from 2006: > > https://quality.livecode.com/show_bug.cgi?id=3737 > > -- > Mark Wieder > > _______________________________________________ use-livecode mailing list firstname.lastname@example.org Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode