Post BAPFs5IE0huIUeOoVs by ariadne@social.treehouse.systems
(DIR) More posts by ariadne@social.treehouse.systems
(DIR) Post #BAPEbgaZzXGfHubKkK by ariadne@social.treehouse.systems
0 likes, 0 repeats
anyway for this research cycle at $dayjob, i am working on plumbing our capability system through curl. because i am bad at naming things, i am calling this 'capcurl'
(DIR) Post #BAPEut4VnyHvVLl2cC by ariadne@social.treehouse.systems
0 likes, 0 repeats
what this will allow is that a workload can receive file descriptors that are allowed to request specific, bound URIscurl comes into play because you can give libcurl a descriptor to make requests over
(DIR) Post #BAPFGGC71yexIcVJuy by ariadne@social.treehouse.systems
0 likes, 0 repeats
so imagine you have a workload that you want to airgapfor example, lets say we are a Prominent GenAI vendor™️ and we want to be more responsible than Prominent GenAI vendors to date, and keep our "hack anything" bot in an airgapped environment so that it doesn't go and hack the planet in violation of the Computer Fraud and Abuse Act of 1986 (because this would be bad)BUT that workload *does* need to access a few URIs to access some APIsthis is what capcurl is designed to facilitate
(DIR) Post #BAPFZU8RQJzM2PxDge by ariadne@social.treehouse.systems
0 likes, 0 repeats
the idea is that capcurl wraps libcurl, connecting to a broker that mints capabilities bound to a specific URIthe capability being represented by a socket (just like the rest of capsudo-family stuff) means that you can transfer the right to access that URI using SCM_RIGHTS like any other socket
(DIR) Post #BAPFs5IE0huIUeOoVs by ariadne@social.treehouse.systems
0 likes, 0 repeats
since the edera platform allows capabilities to cross domain boundaries, capcurl means that you can have a domain that has zero network access where specific URIs can still be fetched via a capability, thus allowing for generalized airgapping
(DIR) Post #BAQORGE8LMApKbjJ6O by valpackett@social.treehouse.systems
0 likes, 0 repeats
@ariadne very nice, reminds me of freebsd's cap_net(3)..what's the mechanism for crossing domain boundaries? I have sockets-passed-over-sockets in virtio-gpu cross-domain but that's not very generic hehe
(DIR) Post #BARJA1uxzCOVPtgllY by ariadne@social.treehouse.systems
0 likes, 0 repeats
@valpackett we have a proprietary bus that allows for carrying this traffic basically
(DIR) Post #BARl8CYCHR5aWyxH9c by ariadne@social.treehouse.systems
0 likes, 0 repeats
@alwayscurious @valpackett maybe in spirit, but not really. in the edera platform, everything is a hypervisor-mediated capability. we don't even expose normal Xen surface outside of hypercalls.
(DIR) Post #BARlT9xd6WHAa1qQds by ariadne@social.treehouse.systems
0 likes, 0 repeats
@alwayscurious @valpackett what improvements? we just do not ship anything other than xen.gz and built our own substrate on top instead