Post #1496854
2026-03-02 07:43 UTC
…the ability to authenticate connections via classic SSH keys (mutual TLS is supported too of course).
The bridge can be used to expose local Varlink services to remote peers via HTTP, opening up those services to the HTTP world. But sometimes the other direction is useful too: i.e. being able to access remote Varlink services exposed via HTTP via sd-varlink + varlinkctl. With v260 that's easy to do: if you specify a Varlink service not via an AF_UNIX socket path, but via an HTTP URL…
Replies (1)
-
@pid_eins@mastodon.social 2026-03-02 07:46
…then sd-varlink/varlinkctl will fork off /usr/lib/systemd/varlink-bridges/http (and analogue for https, or any other protocol scheme), and communicate through it. In fact, Michael's bridge implements this client side too, and hence after installing it, you can do stuff such as: varlinkctl call httqs://my.web-server.com:8080/ws/sockets/io.systemd.Hostname io.systemd.Hostname.Describe {} and the right thing will happen. (I replaced a p with a q in the above, to trick Mastodon's formatting.)