Bug 255694
| Summary: | New port: security/tang: Small daemon for binding data to the presence of a network | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Howard Holm <hdholm> | ||||
| Component: | Individual Port(s) | Assignee: | Neel Chauhan <nc> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | hdholm, nc, rhurlin | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| URL: | https://github.com/latchset/tang | ||||||
| Bug Depends on: | 255693 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Committed! A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=996a6909ee6ea04ffc6962af5167811629275096 commit 996a6909ee6ea04ffc6962af5167811629275096 Author: Howard Holm <hdholm@alumni.iastate.edu> AuthorDate: 2021-05-10 01:21:25 +0000 Commit: Neel Chauhan <nc@FreeBSD.org> CommitDate: 2021-05-10 01:23:51 +0000 New port: security/tang: Small daemon for binding data to the presence of a network PR: 255694 security/Makefile | 1 + security/tang/Makefile (new) | 30 ++++++++++++++++++++++++++++++ security/tang/distinfo (new) | 3 +++ security/tang/pkg-descr (new) | 21 +++++++++++++++++++++ security/tang/pkg-plist (new) | 8 ++++++++ 5 files changed, 63 insertions(+) |
Created attachment 224758 [details] The port files in diff format A new port of github.com/latchset/tang Tang is a server for binding data to network presence. This sounds fancy, but the concept is simple. You have some data, but you only want it to be available when the system containing the data is on a certain, usually secure, network. This is where Tang comes in. First, the client gets a list of the Tang server's advertised asymmetric keys. This can happen online by a simple HTTP GET. Alternatively, since the keys are asymmetric, the public key list can be distributed out of band. Second, the client uses one of these public keys to generate a unique, cryptographically strong encryption key. The data is then encrypted using this key. Once the data is encrypted, the key is discarded. Some small metadata is produced as part of this operation which the client should store in a convenient location. This process of encrypting data is the provisioning step. Third, when the client is ready to access its data, it simply loads the metadata produced in the provisioning step and performs an HTTP POST in order to recover the encryption key. This process is the recovery step. This requires jose, which is being separately submitted.