The lede is a little buried in that README [1]:
## Sealed Computing
A canonical use of Oak is to build privacy-preserving sealed computing applications.
In a sealed computing application, a node (usually a client device) sends data to an enclave application (usually a server), which processes data without the service provider hosting the enclave application being able to see the inputs, outputs, or side effects of the computation.
[1]: https://github.com/project-oak/oak?tab=readme-ov-file#sealed...
---
Seems like an attempt at a privacy-preserving alternative to running your whole phone OS image on a server?
So, something that can be used to run Tor relays that provably don't intentionally misbehave? Or hidden services that the hosting provider has no way to give other people access to?
Nice, seems like a more cost-effective alternative to homomorphic encryption
Based on the headline, I thought this was a reference to Gosling's pre-Java language.
I was curious if someone would build something that allows the DCAP datacenter attestation to be exposed to applications, e.g. "prove via intel that the SHA of the software running on the machine is XYZ"
Super cool. I did some reading about Secure Enclaves with I was dreaming up ways to democratize compute; very cool to see a project like this making it a reality.
This reminds me of Spritely Goblins from the Spritely Institute, which has "vats" where you can run code in a distributed manner using object capabilities.
How does this compare with https://github.com/confidential-containers?
How does this relate/compare to AWS Nitro Enclaves? It looks like the same concept, except integrated into Intel and AMD CPUs.
Maybe I’m just paranoid, but isn’t the (possibly unwritten) intent of this project to be able to flip the client and server around and run code in your browser and phone? I don’t understand their incentive to work on this unless they can use it to gatekeep “official” youtube clients (for example).
At first I thought this is related to the Oak server: https://github.com/oakserver/oak
This seem to be Google's response to Apple private cloud compute [1]?
A bit surprised that it’s written in rust, rather than Go. I suppose rust can take advantage of more low level apis, plus no overhead of garbage collection.
edit: love that the community is not silo’d into a proprietary chat platform as well:
> We welcome contributors! To join our community, we recommend joining the mailing list.
- https://github.com/project-oak/oak?tab=readme-ov-file#gettin...
I really wish more open source projects used mailing lists.
1) decentralized means of communication
2) able to join these communities from any type of environment (ie, corporate hell hole) without much friction. With discord, slack (especially at fortune 500s). It usually involved a whole process of approvals to get the damn thing installed and punch a hole through the firewall to get access to the service.
No, using a personal email and device for what I consider contributing from a work aspect (ie, submitting patch to OSS to solve specific problem with project) is not acceptable.
I think the authors should mention the background story for how this project originated at Google in Google Research (UK). Tried browsing through the Github project page and didn't see any obvious references, aside from the committers list.
AFAIK, the first time I heard about "Project Oak" was about four or five years ago.
This predates Apple's Private Cloud Compute.