No you can't look inside, at least not with what we get from VM SSL. A client certificate is within the handshake, so the best you can do at that point is to close the connection. But again, not really with what you get from VM SSL. I don't have a solution for your authentication requirements.
Rob On Sat, Jun 14, 2025, 17:58 Donald Russell <[email protected]> wrote: > Hmmm that’s an interesting idea. Hmm, could I then look at a client cert > and know who is connecting to me? If they’re my friend I proceed without > the need for userid and passwords. > > Otherwise, no soup for you! (Seinfeld tv show reference) > > > > On Sat, Jun 14, 2025 at 08:33 Rob van der Heij <[email protected]> wrote: > > > 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. > > > > > > > > > > > > > > >
