enclaver
FluidFramework
enclaver | FluidFramework | |
---|---|---|
8 | 12 | |
119 | 4,611 | |
2.6% | 0.1% | |
8.1 | 10.0 | |
3 months ago | 7 days ago | |
Rust | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
enclaver
-
PostgreSQL Encryption: The Available Options
If you're looking for the best way to take a container and run it with Nitro, I work on https://github.com/edgebitio/enclaver
Works great with Kubernetes as a DaemonSet or straight on a VM.
-
Ask HN: What Are You Working on This Year?
Building a tool for running secure enclaves called Enclaver (https://github.com/edgebitio/enclaver). There is a big opportunity for keeping data encrypted while running code against it within enclaves.
And a more secure software supply chain is possible with device attestation and cryptographic measurements of software.
-
My company open sourced our tool to mix pods with secure enclaves into a regular EKS cluster
Check out the code on GitHub: https://github.com/edgebitio/enclaver
-
Supabase secrets management available in beta
I'm building the "in-use" part of this right now...what if you could encrypt your data with an encryption key (at-rest), _but also_ to a set of code that is allowed to decrypt it (in-use). If that code is identified cryptographically, its identity can't be spoofed or stolen.
We're exploring secure enclaves as the protected runtime env and the code attestation generation: https://github.com/edgebitio/enclaver
- Enclaver - run code in secure enclaves so it can't be observed by any human (like your iPhone enclave, but on AWS servers instead)
- Show HN: Enclaver – create and run secure enclaves
-
What’s the coolest thing you did this year?
I have been building out an open source project called Enclaver, which allows you to wrap sensitive workloads inside of a secure enclave (the same as your iPhone, but on servers). It's intended for anything you don't want observed, like JWT signers, encryption/decryption, partner integrations using highly privileged API keys, etc.
-
The Security Design of the AWS Nitro System
I found the side channel protection and CPU/L1 isolation between customers to be particularly interesting.
Very cool to see the physical hardware interconnects for resetting the system. Also the PCI bus as one of the isolating boundaries.
I have built an open source project for managing Nitro Enclaves (https://github.com/edgebitio/enclaver), so it is cool to see how these build on this foundation to provide even more protection.
FluidFramework
- FluidFramework: Build distributed, real-time collaborative web applications
-
Ask HN: What Are You Working on This Year?
Have you seen FluidFramework? It's open source (MIT): https://github.com/microsoft/FluidFramework
I think the first product they're building on it is Loop: https://www.zdnet.com/article/microsoft-introduces-loop-a-ne...
- Ask HN: Apps that are built with Git as the back end?
- Realtime: Multiplayer Edition
- Fluid Framework: Data Sync Reimagined
-
Woe be onto you for using a WebSocket
Full disclosure I work at MSFT and on the fluid framework.
If you are interested in this you may also be interested in the fluid framework, https://github.com/microsoft/FluidFramework
We use websockets and solve a lot of the state management problem called out here by keeping very little state on the server itself. The primary thing on server is a monotonically increasing integer we use to stamp messages, this gives us total order broadcast which we then build upon: https://en.m.wikipedia.org/wiki/Atomic_broadcast
Here are some code pointers if you want to take a look:
The map package is a decent place to look for how we leverage total order broadcast to keep clients in sync in our distributed data structures:
-
Microsoft Launches Google Wave
(Disclosure: Work at Microsoft, but I work in Azure and some open source stuff, not on or directly with Fluid/Office/etc.)
That's just a trademark clause for Microsoft logos and brands. The Fluid Framework itself is [MIT licensed](https://github.com/microsoft/FluidFramework/blob/main/LICENS...) and doesn't require exposing any of those logos/brands when you use it, so the framework itself is fairly open for usage.
I think the main thing that would slow down adoption for Fluid is that the only "production" backend is an Azure service, which isn't part of the open source Fluid Framework. [Other open source backends](https://fluidframework.com/docs/deployment/service-options/) aren't recommended for productions. Until there are some open source ones, I'd assume adoption will be limited to folks in the Azure ecosystem.
-
The Lost Apps of the 80s
Within the context of the Microsoft-verse, Fluid Framework (https://fluidframework.com) is supposed to be solving similar problems in web apps, although I haven't personally played with it.
-
A couple of questions about dotnet from a Java developer :)
Microsoft recently open sourced fluid framework. It is a distributed, consensus based, real time collaboration framework written in typescript. Fluid would keep your clients synced up and your server code would only have to handle when someone hits submit. Fluid Framework
-
Fluid Framework discovery
The official documentation and the github repository seem clear.