On Fri, 2019-05-10 at 22:32 +0900, Ramses Ramirez wrote: > Hi David, > > Thanks for the explanation. That was helpful! I think I was confused > about the difference between private keys and certificates. > > I don't think that the vpn server I am trying to reach uses > certificates then. It just has a port number. > On my Windows account, I was able to access this vpn server just > knowing the IP address and port number (using Fortclient). > A public/private key pair was then used to ssh into a particular host > on that network (my own external workstation). You didn't have a username or password or anything else at all? > How would I use openconnect to access the vpn without needing a > certificate (so that I can next ssh into my host computer using my > private key)? Setting aside the question of where it gets its credentials, I don't think that's even a protocol that OpenConnect supports, is it? If you want to stick a MITM proxy in the middle and observe the traffic, it would probably be fairly easy to add. But it's going to require a little bit of development work.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ openconnect-devel mailing list openconnect-devel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/openconnect-devel
