zlacker

[parent] [thread] 3 comments
1. amluto+(OP)[view] [source] 2022-01-27 18:58:17
Many workflows are proxyable using fine grained IP-level or TCP-level security. (I believe that Tailscale does more or less this.). This can’t support RBAC or per-user dynamic authentication particularly well, but it can at least avoid trusting an entire network.
replies(1): >>zrail+82
2. zrail+82[view] [source] 2022-01-27 19:08:51
>>amluto+(OP)
Yeah, a thing that I wish Tailscale could do is hand off an attestation of some sort that says a TCP connection is being used by user X who is authorized by rule Y. Maybe "magic TLS client certs" is a thing coming on the horizon.
replies(1): >>madjam+tX
◧◩
3. madjam+tX[view] [source] [discussion] 2022-01-27 23:02:15
>>zrail+82
You can query the Tailscale API socket locally from your application to see who someone is (email address) based on the connecting IP. It would be nice if the API let you tap into their ACL system as well
replies(1): >>zrail+Io1
◧◩◪
4. zrail+Io1[view] [source] [discussion] 2022-01-28 02:18:34
>>madjam+tX
Oh interesting!
[go to top]