Replies: 2 comments
-
Try looking into self-signed certificates and how to add them to your trust store. Most operating systems provide a way to do this, and the OpenSSL CLI tool has a utility to generate a self-signed certificate. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Lit, thanks man I’ll try to figure that out
… On Feb 4, 2022, at 1:42 AM, Ethan Marshall ***@***.***> wrote:
Try looking into self-signed certificates and how to add them to your trust store. Most operating systems provide a way to do this, and the OpenSSL CLI tool has a utility to generate a self-signed certificate.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
All modern browsers give me a "not secure" warning when on the site, because it's not https. I've looked and it doesn't seem like there's a way around this without adding an ssl certificate to the site so you can manually trust it. If there is an alternative please let me know, I just need to get rid of the warning so scammers don't get suspicious. I can't imagine a real bank using an unsecured connection.
Beta Was this translation helpful? Give feedback.
All reactions