5 ms·
This was a mistake on our website, which as since been removed. 1. We'll be open sourcing our client in the coming weeks so you can check out our code yourselv
by loopholelabs 6y ago
This was a mistake on our website, which as since been removed.
1. We'll be open sourcing our client in the coming weeks so you can check out our code yourselves.
2. We will be offering a self-hosted version which will decouple you entirely from our infrastructure and you can provide you own SSL certificates.
3. Lynk can forward traffic to your encrypted services - which of course would mean losing out on compression benefits, but Lynk is designed primarily for quick development work like testing out a Stripe or Github webhook on your local machine, or demoing your webapp to a remote client. For production use we recommend a reverse proxy or self-hosting Lynk.
- billyhoffman 6y agoThank you, this is helpful. You could use this "for dev" and "for prod" as a marketing/business opportunity. Distinct bullets points of use cases in "For Dev" and "For Prod" sections. For prod there are also add-on options that would not make sense for dev, and could provide additional value (custom support, pre-built packages for distros, analytics on traffic/usage analytics about the tunneled services, etc) Good Luck
- deathanatos 6y agoYou allow the user's machine to obtain a valid certificate for a subdomain of lynk.sh? (This would seem to me the only way to accomplish E2EE, given the example of connecting over TLS to a lynk.sh host, and it also seems very unlikely.)
- mcpeepants 6y agowhy does that seem unlikely?
- cbluth 6y agothe certificate at https://loopholelabs.io/ https://loopholelabs.io/ has been invalid for almost a month