Mojo-V: Secret Computation for RISC-V

Manfred 30 minutes ago | parent | next [-]

After skimming through the documentation this seems like a nice solution, but I'm not sure if this is a problem we want to solve.

Consumers are finding out the issue with cloud computing when their heating system can't turn on because Cloudflare is down. A cheaper and more reliable solution is still on-premises computing.

Large social network and content platforms don't have any incentive to keep your data safe because they want to monitor and own everything.

Maybe this is for something like a government running a public service?

▲

LarsDu88 30 minutes ago | parent | prev | next [-]

Was it really wise to name this Mojo when Chris Lattner, former Head 9f Engineering at SiFive also called his well funded programming language Mojo?

▲

shakna 3 hours ago | parent | prev | next [-]

This could be:

Great for security - Being able to safely compute secrets is a very difficult problem.

Fucking awful for security - More OEM secret controls and "analytics" that devolve into backdoors after someone yet again post keys online.

	▲	Manfred 37 minutes ago \| parent [-]
		The platform owner can manage keys and data contracts in the processor, that should enable them to rotate secrets constantly. In other hardware there is an OEM secret because the manufacturer is trying to keep users out of "their hardware", in this case we're trying to keep everyone except the data owner out.

▲

snvzz an hour ago | parent | prev | next [-]

RISC-V is inevitable.

▲

pjmlp 3 hours ago | parent | prev [-]

And the relationship to Mojo programming language is?