Hi Richard, it's client side.

The project is a messaging app, principally for mobile.  SSL/TLS
certificates issued with client software enable servers to know that the
connection is allowed at a network level before any user authentication.

In the early stages of development it was simple enough for a LC messaging
server to dismiss connections which didn't come from an accepted client and
didn't meet the specification.  Once I moved to an industry standard server
then the connections have to be encrypted with certificates at both ends.

Regards, Bernard

On Thu, Jan 28, 2021 at 4:44 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Bernard Devlin wrote:
>
>  > 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.
>
> Is this specific to the server "accept" not supporting SSL, or something
> client-side?
>
> --
>   Richard Gaskin
>   Fourth World Systems
>   Software Design and Development for the Desktop, Mobile, and the Web
>   ____________________________________________________________________
>   ambassa...@fourthworld.com                http://www.FourthWorld.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to