-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
19 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
This is the first public release of Disco! :tada: | ||
|
||
Needless to say, the project is in very early alpha stages, but the basic design and functionality I had in mind are implemented: | ||
|
||
- Storing and retrieving data from a key-value store. | ||
- Data is secured at rest using symmetric encryption (NaCl). | ||
- Multi-user support with a flexible [role-based access control system](https://github.com/hackfixme/disco/blob/v0.1.0/docs/roles.md). | ||
- Remote access using invitation tokens. Nodes exchange secrets using ECDH, and clients are authenticated using mutual TLS. Data is only transferred over TLS 1.3 using Ed25519 keys. | ||
- Namespacing support for separating environments (development, staging, production, etc.), with minimal maintenance. | ||
- User-friendly and intuitive CLI. | ||
|
||
Please report any issues [here](https://github.com/hackfixme/disco/issues). | ||
|
||
You can see planned work on the [roadmap](https://github.com/orgs/hackfixme/projects/1/views/1). Please vote on issues by giving them a :thumbsup:. | ||
|
||
The goal of this project is to become more broadly usable than "just" for secret management. Securely transferring arbitrary data between nodes opens up the possibility for configuration management, deployments, notifications, and other uses.[^1] But... humble beginnings. :) | ||
|
||
[^1]: Yes, there are many other projects that already do this in one way or another. But the ones I've used so far have shortcomings that sacrifice some of the design aspects and features I'm looking for. |