Live data from Hacker News

Show HN: Malai – securely share local TCP services (database/SSH) with others

malai.sh

1–10 of 72 posts

Show HN: Malai – securely share local TCP services (database/SSH) with others

#1
malai is a peer to peer network, and is a dead simple to share your local development HTTP server, without setting up tunnels, dealing with firewalls, or relying on cloud services.

In malai 0.2.5, we have added TCP support, which means you can expose any TCP service to others using malai, without opening the TCP service related port to Internet. With malai installed on both ends, any TCP service can be securely tunneled over it.

It can be used to secure your SSH service, or securely share your database server.

GitHub: https://github.com/kulfi-project/kulfi (star us!)

Would love feedback, questions, or ideas — thanks!

PS: We have also added `malai folder`, which lets you share (readonly) the content of a folder with others.

Show HN: Malai – securely share local TCP services (database/SSH) with others
malai.sh

Re: Show HN: Malai – securely share local TCP services (database/SSH) with others

#2
> In this case, you can visit kulfi://http-e9b1c82b43206c96173848ed0afad2fe633fdc8a02ba391a3d37, which is where the Talk App lives.

What is the DNS story for this platform? Or are you intending to be kind of like a replacement for Syncthing where each endpoint has to explicitly approve the other and thus discovery is left as an exercise to the reader?

Actually, even after further thought, I am still able to rename my peers in Syncthing, and unless one has to go to the dashboard for getting that Talk App link(? button?) all the time, it's been my experience that folks will always want aliases for ginormous hex strings

---

p.s. you have some broken images in your Journey docs

Re: Show HN: Malai – securely share local TCP services (database/SSH) with others

#10
post #3

Don't we use Tailscale for this?

Unlike tailscale/ngrok, malai is completely open source, does not rely on any company provided infrastructure (we have a http bridge to bridge http/tcp with http/kulfi at *.kulfi.site, but you can run your own http bridge), and once Kulfi app is ready, you will not need the bridge at all and Kulfi app (which is also basically a browser that speaks http(s) over kulfi along with http(s) over tcp) can talk kulfi protocol directly.
Post reply on HN