Is it possible to specify which SSL certs to accept? (Or to only accept certs from recognized public CAs?)

[billyJoePiano]

Issue: It seems that the client will accept any self-signed cert since the WebMessage server by default is using one.

My current setup: I'm using an nginx reverse proxy with a valid public cert (via Let's Encrypt) to serve the WebMessage API, even on my local network. The jailbroken iPhone is directly tethered to this server and can only be accessed through it (server also functions as the router/gateway for the iPhone to the outside)

Solution: I'd like to configure the client to only accept a valid SSL cert. Of course, doing this also requires that the server is reached by domain name rather than IP (which seems to be working fine on both my Windows and Linux clients) so the cert could be compared against that domain name to ensure it matches.

Offer/Request: I'm fairly experienced in JS, though mostly in webpage and some Node, and wouldn't mind contributing to (or making a custom tweak to) the client source code myself. If you could just point me to the section that deals with SSL connections to the server, that would be very helpful! I've been trying to find the relevant files in the repo, but can't seem to locate them. I've never worked with Vue before, but I tend to pick up new languages/platforms pretty quickly.

Thanks!

[billyJoePiano]

p.s.

When installing all the dependencies with yarn, I am getting an error message that the vue-lazy-image module cannot be found. I've already reached out to the (former?) maintainer of this package to find out if there's a way to get it. But it would seem it is no longer available???

[ersan]

p.s.

When installing all the dependencies with yarn, I am getting an error message that the vue-lazy-image module cannot be found. I've already reached out to the (former?) maintainer of this package to find out if there's a way to get it. But it would seem it is no longer available???

If you go into the yarn.lock file and change the URL for vue-lazy-image from https://registry.npmjs.org to https://registry.npmmirror.com it will fix the dependency. I still had a terrible time trying to build this project for production though.