[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#854409: marked as done (ITP: tang -- A server for binding data to network presence)

Your message dated Mon, 20 Nov 2017 00:00:19 +0000
with message-id <E1eGZVb-0006SP-J1@fasolo.debian.org>
and subject line Bug#854409: fixed in tang 6-1
has caused the Debian Bug report #854409,
regarding ITP: tang -- A server for binding data to network presence
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
854409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854409
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist

* Package name    : tang
  Version         : 4
  Upstream Author : Nathaniel McCallum
* URL             : https://github.com/latchset/tang
* License         : GPL
  Programming Lang: C
  Description     : A server for binding data to network presence

I'm citing from the upstrem README here:

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.

The client side is implemented in clevis. The only missing dependency in
Debian is jose a C-language implementation of the Javascript Object
Signing and Encryption standards.

--- End Message ---
--- Begin Message --- 
Source: tang
Source-Version: 6-1

We believe that the bug you reported is fixed in the latest version of
tang, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854409@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Biedl <debian.axhn@manchmal.in-ulm.de> (supplier of updated tang package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 14 Nov 2017 18:59:31 +0100
Source: tang
Binary: tang tang-nagios
Architecture: source powerpc
Version: 6-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
Changed-By: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
Description:
 tang       - network-based cryptographic binding server
 tang-nagios - monitoring plugin to check the tang server
Closes: 854409
Changes:
 tang (6-1) unstable; urgency=medium
 .
   * Initial release. Closes: #854409
Checksums-Sha1:
 9b03a2608653782aa148beee4841ce818af62144 1807 tang_6-1.dsc
 452f38a7d722c2023f8ca33723f39d173dd9d52e 118040 tang_6.orig.tar.bz2
 2b7ce914067c9f33606061f70c64e65e1d57fdd1 1784 tang_6-1.debian.tar.xz
 b1675a6478fa62e8f9c175dcabb18ed66172d0df 16756 tang-dbgsym_6-1_powerpc.deb
 95b1764a8b4f79ffbe65446f4af4aba78d280ddd 16392 tang-nagios-dbgsym_6-1_powerpc.deb
 87f6ea86bb50e5d404a190c18929789bd41e1b57 8480 tang-nagios_6-1_powerpc.deb
 d0e4bd9014e7d94fffd02d3530eadfcaa45e573e 6348 tang_6-1_powerpc.buildinfo
 fb54a358fa580ad405680a1b6970c40f84da6fcd 13064 tang_6-1_powerpc.deb
Checksums-Sha256:
 8f91db39dbbb59c71c7783e95368273bb1015bba5857c57782b4014a887db73a 1807 tang_6-1.dsc
 1df78b48a52d2ca05656555cfe52bd4427c884f5a54a2c5e37a7b39da9e155e3 118040 tang_6.orig.tar.bz2
 b0093267d5fa51c7d44a2f54bf95966d225b56ac4b643182e9c5e790e2980095 1784 tang_6-1.debian.tar.xz
 0a17e1549f1383deda2022e165842c02cf8fdec6ebca37127317be0967e401ba 16756 tang-dbgsym_6-1_powerpc.deb
 74aceae9fe1bf1fc03fc112fa0250e88e4a6559d85fb255f4a8488e6b063eef2 16392 tang-nagios-dbgsym_6-1_powerpc.deb
 83e7a681033af6c2134e71d9e96922c572d69556eeae188b72ba25dc10bf085b 8480 tang-nagios_6-1_powerpc.deb
 250f0f4dc8b1ebb47740c3ced425652af820ff47b2cc4184aa2ba0f7750f6859 6348 tang_6-1_powerpc.buildinfo
 8d4c457df6e7f2f61da45d946d32c2ef5bf495132ca6a62ffdbff4b89dca2900 13064 tang_6-1_powerpc.deb
Files:
 e7367ed4d7b498f746d03c3c3f460245 1807 net optional tang_6-1.dsc
 249c927b4bac05ab07a37b46d71f1764 118040 net optional tang_6.orig.tar.bz2
 9ad0f1f5a0258de485718c5ea18e5b9d 1784 net optional tang_6-1.debian.tar.xz
 0611a310266ad3ba426e918ca7646137 16756 debug optional tang-dbgsym_6-1_powerpc.deb
 b77ed0eabf2175e33a8841dc1f6cd9a9 16392 debug optional tang-nagios-dbgsym_6-1_powerpc.deb
 af5b39121be72052777abbfa3aeb1eb2 8480 net optional tang-nagios_6-1_powerpc.deb
 d4b98a82351efbf328b74f26816c8961 6348 net optional tang_6-1_powerpc.buildinfo
 f7513e1245419b4fc5e4717fb6667b63 13064 net optional tang_6-1_powerpc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJaEf1GAAoJEMQsWOtZFJL9wuYQAMz9/QG3eiBfi6pwS59BqwqL
AXhdHZQlZn4m/NsTw06wD3n8u1n9yoU0Q25ya/nUpaHYGQE6DyOXbxGIF8UP4Rzd
mQEAt6zhOQLR8Plluzw4utPpoibVfNrdRLrE+MV6RPGI0nNhr/lWN2jjBE6vNyod
1nt8hZhuMVcU9UfECBYAXNMJI4Q95sPMoNHvfkUoASid52q0r0fx6LI9M0669qEu
anisDjeo8RDSw2wrxNfCsDKBaj/CnV+9eiUGXzl/fgR3E1m934y/1+bPXa55Lhor
tQEbsXMNlNnXqZoJRmRU7HV2q3pDjmg0ynNT3xAwnKSMESyXbDSHxk+ZhPDxIaMx
+Le29J/9XDxNpIkgddGhyDDNKMZdq22TVACxiCzQry3V1fdJg5sfAVUgMysQOWAV
YkUn6I7WcutE9fqZqZrYUD8Kfj6JcQIZC0ObG4nNMrjg2D9+wGw8U7A/PdODn/On
WxIpjT9z/Kl+B4svUXK02AEQX7w7gFmZVyD/42HFC3Gfk0RlwPhNLT96t92PaS5p
AET0XqulGtfqmVxcSh0swoTomNp3mhdidn57U4O2bMsKhAJ9wiWO7ACdoERIYEkL
iVUkQOEkV36lpMztaxjBitpcEnyAUmgQNDsvtCpgu3tDxI5O4VcB+q4od6bDfqZ6
hrDVvSDmI0uvIeTocvUo
=b4Vz
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: