secure socket | ||||||||||
Type | command | |||||||||
Dictionary | LCS | |||||||||
Library | LiveCode Script | |||||||||
Syntax |
| |||||||||
Associations | ssl & encryption | |||||||||
Summary | Secures an open socket. | |||||||||
Introduced | 6.6 | |||||||||
OS | mac, windows, linux, ios, android | |||||||||
Platforms | desktop, mobile | |||||||||
Parameters |
| |||||||||
Example |
| |||||||||
Related | Property: sslCertificates Message: socketError Command: open socket Glossary: Standalone Application Settings, command, LiveCode custom library, standalone application, message, property Library: SSL & Encryption library | |||||||||
Security | network | |||||||||
Description | Use the secure socket command to secure an open socket. If 'with verification' is specified, when connecting to a remote peer, the client verifies the peers certificate during the handshake process. The sslCertificates property can be used to specify a list of certificates to verify against. In addition you can place system wide certificates in System/Library/OpenSSL/certs. If a verificationhostname is specified, the socket will be verified against that verificationhostname. An example of this is when you want to create a secure connection with a host while tunnelling through a proxy. Specifying the final host allows LiveCode to verify the socket against that host, rather than the proxy server. If 'without verification' is specified then peers credentials are not authenticated, and any connection is accepted. Once secured:
If the socket fails secure, a socketError message is sent to the object that opened the socket (not the object that attempted to secure it).
| |||||||||
Tags | file system |