-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start tunnel using HTTPS authentication request #3
Comments
Phew, it's been over 18 months since I actually did any real coding on this - i'll have to give it a once over to see what changes would be needed. Just to clarify you want your private client to be able to establish a connection to the public server without having to authenticate? It seems a little insecure but might be quite simple to do :) I'm not sure this relates to the HTTPS thing in the roadmap which is more about just streamlining the process of establishing a connection and would still have involved authentication |
It may be as simple as making the following
Similarly in |
Oh there's also the tunnel created in
|
Just so you know if this disappears down a rabbit hole into |
Just rereading - i missed the bit about simple HTTP authentication - now I see why you want to switch to the HTTPS method. That will be more work indeed but the bit you're wanting to replace is that |
@pghalliday thanks! sorry for not responding sooner, I posted this right before disconnecting for a couple of weeks. i'm hopin to start playing with this over the next few weeks -- so thanks for the starting points! |
Thanks for the awesome lib!
In my use case, I'd like to remove the use of certificate verification, and add some simple HTTP authentication to initiate the tunnel. I see that you have something similar in your roadmap:
I'd be happy to work on this and contribute back, but am looking for some help with a starting point, where this would happen, etc.
The text was updated successfully, but these errors were encountered: