Date: Fri, 07 May 2021 23:17:39 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 255694] security/tang New port Message-ID: <bug-255694-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255694 Bug ID: 255694 Summary: security/tang New port Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: hdholm@alumni.iastate.edu Created attachment 224758 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D224758&action= =3Dedit 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 o= nly 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 ke= ys. 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 t= his 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 rec= over the encryption key. This process is the recovery step. This requires jose, which is being separately submitted. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255694-7788>