Attachment #224758 for bug #255694

View | Details | Raw Unified | Return to bug 255694
Collapse All | Expand All




# $FreeBSD$

PORTNAME=	tang
DISTVERSION=	10
CATEGORIES=	security

MAINTAINER=	hdholm@alumni.iastate.edu
COMMENT=	Tang is a small daemon for binding data to the presence of a network

LICENSE=	GPLv3
LICENSE_FILE=	${WRKSRC}/COPYING

LIB_DEPENDS=	libjose.so:net/jose libhttp_parser.so:www/http-parser libjansson.so:devel/jansson
RUN_DEPENDS=	socat:net/socat
BUILD_DEPENDS=	socat:net/socat a2x:textproc/asciidoc

USES=           compiler:c11 meson ninja pkgconfig
USE_LDCONFIG=	yes
INSTALL_TARGET=	install-strip
DEFAULT_VERSIONS+=ssl=openssl

USE_GITHUB=	yes
GH_ACCOUNT=	latchset
GH_TAGNAME=	v10

post-install:
	${MKDIR} -m 0700 ${STAGEDIR}/var/db/tang

.include <bsd.port.mk>

Added Link Here

(-)b/security/tang/distinfo (+3 lines)
1	TIMESTAMP = 1620421972
2	SHA256 (latchset-tang-10-v10_GH0.tar.gz) = 168ceee00bcf1da3d4e595285947fdcd5822b2e4e5cdb4b0e69b450b2cac2ba6
3	SIZE (latchset-tang-10-v10_GH0.tar.gz) = 36469




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.

WWW: https://github.com/latchset/tang

Added Link Here

(-)b/security/tang/pkg-plist (+8 lines)
1	libexec/tangd
2	man/man1/tang-show-keys.1.gz
3	man/man8/tang.8.gz
4	libexec/tangd-keygen
5	libexec/tangd-rotate-keys
6	bin/tang-show-keys
7	etc/rc.d/tangd
8	@dir /var/db/tang

Return to bug 255694

Added Link Here

(-)b/security/tang/Makefile (+29 lines)
1	# $FreeBSD$
2
3	PORTNAME= tang
4	DISTVERSION= 10
5	CATEGORIES= security
6
7	MAINTAINER= hdholm@alumni.iastate.edu
8	COMMENT= Tang is a small daemon for binding data to the presence of a network
9
10	LICENSE= GPLv3
11	LICENSE_FILE= ${WRKSRC}/COPYING
12
13	LIB_DEPENDS= libjose.so:net/jose libhttp_parser.so:www/http-parser libjansson.so:devel/jansson
14	RUN_DEPENDS= socat:net/socat
15	BUILD_DEPENDS= socat:net/socat a2x:textproc/asciidoc
16
17	USES= compiler:c11 meson ninja pkgconfig
18	USE_LDCONFIG= yes
19	INSTALL_TARGET= install-strip
20	DEFAULT_VERSIONS+=ssl=openssl
21
22	USE_GITHUB= yes
23	GH_ACCOUNT= latchset
24	GH_TAGNAME= v10
25
26	post-install:
27	${MKDIR} -m 0700 ${STAGEDIR}/var/db/tang
28
29	.include <bsd.port.mk>

Added Link Here

(-)b/security/tang/pkg-descr (+21 lines)
1	Tang is a server for binding data to network presence.
2
3	This sounds fancy, but the concept is simple. You have some data, but you only
4	want it to be available when the system containing the data is on a certain,
5	usually secure, network. This is where Tang comes in.
6
7	First, the client gets a list of the Tang server's advertised asymmetric keys.
8	This can happen online by a simple HTTP GET. Alternatively, since the keys are
9	asymmetric, the public key list can be distributed out of band.
10
11	Second, the client uses one of these public keys to generate a unique,
12	cryptographically strong encryption key. The data is then encrypted using this
13	key. Once the data is encrypted, the key is discarded. Some small metadata is
14	produced as part of this operation which the client should store in a convenient
15	location. This process of encrypting data is the provisioning step.
16
17	Third, when the client is ready to access its data, it simply loads the metadata
18	produced in the provisioning step and performs an HTTP POST in order to recover
19	the encryption key. This process is the recovery step.
20
21	WWW: https://github.com/latchset/tang