The idea is also that before accepting the connection request, you could look at the ip address of the client and use a different server certificate
On Sat, Jun 14, 2025, 17:05 Donald Russell <[email protected]> wrote: > Thanks Rob, > I was looking up the wrong tree. 🙂 > > > > > On Sat, Jun 14, 2025 at 07:27 Rob van der Heij <[email protected]> wrote: > > > It's up to TCPDATA to secure the connection > > > > On Sat, Jun 14, 2025, 16:02 Donald Russell <[email protected]> > wrote: > > > > > If I have a (z)cms pipe application using tcplisten, how can I make > sure > > > the in/outgoing traffic is encrypted? > > > > > > Does the port being listened on have to be explicitly configured in > TCPIP > > > to require encryption? > > > > > > I was hoping I could do something in the pipe server code like PIPE > > > TCPLISTEN port SECURE.. > > > > > > I don’t see any encryption related options for that stage. > > > > > >
