Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Project Oak: Meaningful control of data in distributed systems

github.com

Post reply on HN
Print view View original

41–50 of 55 posts

Re: Project Oak: Meaningful control of data in distributed systems

#41

Post by leoqa »

nepthar wrote: post #33
spankalee wrote: post #2

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 th…

Honestly, I think it will be used for the reverse (and unfortunately more evil) - Google wants to be able to control YOUR machine's compute environment for things like playing back of DRM'd content. They want a chain of trust that your browser cannot be modified to do things like block ads.

From a service owner perspective, if I offer content and want to enforce strong identity from the user then this seems like a win. I may lose eyeballs but will gain higher confidence that my content is being consumed as intended.

I'm fine with more controls in place, a safer internet is clearly a social win that would reduce life alerting fraud, scams etc. If power users want to go to their peer-to-peer cesspool then go for it.

Re: Project Oak: Meaningful control of data in distributed systems

#42

Post by tiziano88 »

warkdarrior wrote: post #34
dboreham wrote: post #21

Earlier quoted context omitted.

Except the other way around.

Except that Apple actually uses this privacy stuff. Is Project Oak used by Android or Pixel?

https://arxiv.org/abs/2404.10764 describes some of the current use cases already using Oak

Re: Project Oak: Meaningful control of data in distributed systems

#43

Post by tiziano88 »

nepthar wrote: post #33
spankalee wrote: post #2

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 th…

Honestly, I think it will be used for the reverse (and unfortunately more evil) - Google wants to be able to control YOUR machine's compute environment for things like playing back of DRM'd content. They want a chain of trust that your browser cannot be modified to do things like block ads.

Oak focuses on running workloads on server-side TEEs

Re: Project Oak: Meaningful control of data in distributed systems

#46

Post by AlotOfReading »

leoqa wrote: post #41
nepthar wrote: post #33

Earlier quoted context omitted.

Honestly, I think it will be used for the reverse (and unfortunately more evil) - Google wants to be able to control YOUR machine's compute environment for things like playing back of DRM'd content. They want a chain of trust that your browser cannot be modified to do things like block ads.

From a service owner perspective, if I offer content and want to enforce strong identity from the user then this seems like a win. I may lose eyeballs but will gain higher confidence that my content is being consumed as intended. I'm fine with more controls in place, a safer internet is clearly a social win that would reduce life alerting fraud, scams etc. If power users want to go to their peer-to-peer cesspool then…

How does enforcing strong attestation from the user result in a safer internet or reduce life alerting frauds and scams? It's not users injecting that onto pages, it's the ad networks that operators choose to use.

Re: Project Oak: Meaningful control of data in distributed systems

#47

Post by nepthar »

leoqa wrote: post #41
nepthar wrote: post #33

Earlier quoted context omitted.

Honestly, I think it will be used for the reverse (and unfortunately more evil) - Google wants to be able to control YOUR machine's compute environment for things like playing back of DRM'd content. They want a chain of trust that your browser cannot be modified to do things like block ads.

From a service owner perspective, if I offer content and want to enforce strong identity from the user then this seems like a win. I may lose eyeballs but will gain higher confidence that my content is being consumed as intended. I'm fine with more controls in place, a safer internet is clearly a social win that would reduce life alerting fraud, scams etc. If power users want to go to their peer-to-peer cesspool then…

A safer internet does not necessarily follow from having this system in place. I'd like to point out that this is an opinion that you have which I and others disagree with.

I also don't believe that content creators have any kind of legal or moral right to force the general public to "consume as intended". For instance, I've got a shelf in my office that's built with supports that are designed for plumbing. I have not consumed these pipes as intended.

Re: Project Oak: Meaningful control of data in distributed systems

#49

Post by [deleted] »

saagarjha wrote: post #14
trallnag wrote: post #4

Nice, seems like a more cost-effective alternative to homomorphic encryption

Attestation is to homomorphic encryption as storing things in a bank safe is to burying it out in the woods. There’s an entity providing you service and they’re trying their best to guarantee that they’re not going to decrypt your stuff but there’s usually some sort of collusion that will make it possible.

[deleted]
Post reply on HN