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

Bug#834869: marked as done (ITP: keysafe -- back up secret keys to cloud servers)

Your message dated Thu, 03 Nov 2016 12:00:13 +0000
with message-id <E1c2Ggn-0002Il-PX@fasolo.debian.org>
and subject line Bug#834869: fixed in keysafe 0.20161022-1
has caused the Debian Bug report #834869,
regarding ITP: keysafe -- back up secret keys to cloud servers
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.)


-- 
834869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834869
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Sean Whitton <spwhitton@spwhitton.name>

* Package name    : keysafe
  Version         : 0.20160819
  Upstream Author : Joey Hess <joeyh@joeyh.name>
* URL             : https://joeyh.name/code/keysafe/
* License         : AGPL-3
  Programming Lang: Haskell
  Description     : back up secret keys to cloud servers

Upstream synopsis:

> Keysafe backs up a secret key to several cloud servers, split up so
> that no one server can access the whole secret by itself.

> A password is used to encrypt the data, and it is made expensive to
> decrypt, so password cracking is infeasibly expensive.

LWN write-up: https://lwn.net/Articles/696765/

The intended audience of keysafe is those using secret keys to encrypt
only their personal data, when storing it in the cloud.  Such a user
doesn't need to take the security precautions that a Debian Developer or
Debian Maintainer must take to protect their secret key.  However, they
still don't want to lose it and thus invalidate their backups.  Keybase
is designed to make it easy to backup secret keys in the cloud for this
kind of user.

Although this software is experimental, it has the potential to enable a
lot more Debian users to use public/private key cryptography to protect
the data that they store in the cloud.

I intend to package this and submit it for upload to experimental.  I
want to do this because I believe it will enable a lot more testing, and
useful feedback submitted to Joey.  In particular, it will enable
feedback from those who know a lot about cryptography but not much about
Haskell.  Further, we will want it in unstable eventually, and getting
the packaging in shape in advance makes that easy (Joey isn't the kind
of upstream to abandon the software while it's still alpha).

--
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: keysafe
Source-Version: 0.20161022-1

We believe that the bug you reported is fixed in the latest version of
keysafe, 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 834869@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton <spwhitton@spwhitton.name> (supplier of updated keysafe 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: SHA256

Format: 1.8
Date: Sun, 23 Oct 2016 13:39:53 -0700
Source: keysafe
Binary: keysafe-bin keysafe keysafe-server
Architecture: source amd64 all
Version: 0.20161022-1
Distribution: experimental
Urgency: medium
Maintainer: Sean Whitton <spwhitton@spwhitton.name>
Changed-By: Sean Whitton <spwhitton@spwhitton.name>
Description:
 keysafe    - securely back up secret keys to cloud servers
 keysafe-bin - keysafe's shared, architecture-dependent files
 keysafe-server - run a keysafe cloud server
Closes: 834869
Changes:
 keysafe (0.20161022-1) experimental; urgency=medium
 .
   * Initial release (Closes: #834869).
Checksums-Sha1:
 aa2be03e220fd35f97601762a440899ac35e4af2 3975 keysafe_0.20161022-1.dsc
 9fce4dd22813d5fb7a1f3d7e633cd0d5dc1391cc 58716 keysafe_0.20161022.orig.tar.xz
 3457b503d73fd71db89ae2344ab36895375ffe6d 15700 keysafe_0.20161022-1.debian.tar.xz
 95072e70d2c0e07de91e60f9b41e1450a1c21682 2782010 keysafe-bin_0.20161022-1_amd64.deb
 19b9ca9429673abba3bfe225e8d58810d7a585fa 17892 keysafe-server_0.20161022-1_all.deb
 97b9803bec23de1f8c0be4a9e3a46bff1bec80f1 16382 keysafe_0.20161022-1_all.deb
Checksums-Sha256:
 5134145011d94934eb1f9c00d6244372f43c6ec8c8e68e1ee97722fd00ca515c 3975 keysafe_0.20161022-1.dsc
 7d8ac5f6697f21b8d2fb975ac536f9ca12041de063ac8b587011f6b20adad9ae 58716 keysafe_0.20161022.orig.tar.xz
 34d82388bf11cb6d146856156a9fbb11d42f9a395e56fc41f2e7a536a966a7f6 15700 keysafe_0.20161022-1.debian.tar.xz
 d3a15e0e57ed6ac7a88d07adca0c2e43af62c1ed8ec987ab6a77e13c2f116d88 2782010 keysafe-bin_0.20161022-1_amd64.deb
 140cbf6c76e72483ed6cc2ff0baebdc2557c46a3b862024ec7ddc101264e10ce 17892 keysafe-server_0.20161022-1_all.deb
 d5fe5f01ea843922d3160fb7f94375093441026b5b74c3529e4d6b9240df38cc 16382 keysafe_0.20161022-1_all.deb
Files:
 55744ab5532aadd76f89460c963282d4 3975 utils optional keysafe_0.20161022-1.dsc
 95ae96f9beaf85f92d4cfdef1da0bfa5 58716 utils optional keysafe_0.20161022.orig.tar.xz
 c501f3dcbbfa675e02da8c551109cd31 15700 utils optional keysafe_0.20161022-1.debian.tar.xz
 dd380408dee0852d717344a91eb7eb59 2782010 misc optional keysafe-bin_0.20161022-1_amd64.deb
 8fd56aa7f88ce941735dcad683d637f2 17892 misc optional keysafe-server_0.20161022-1_all.deb
 355980ce8a228d8c4dfacf9b3361e5bd 16382 misc optional keysafe_0.20161022-1_all.deb

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

iQIcBAEBCAAGBQJYEdtxAAoJEPNPCXROn13ZSeIQAIwFw7j0Zp+Vnb48UfDoXc9x
bqj8RPKlmTbf3rvmnInBxrVk3L53YA4R/u9TY2GqcuOXKZSf0LjmdPoMFQudanp+
CQc5a1Z4ggmyx9LtDZ5KxS26tK5z5NrlmRuwfE2d1kdX48WlvnCQP+ZaUF1TThM5
Tis4BwZN4ee3msRaO0hTYagdxdNfBbMS0ZNViw2dPhjlYcMXOQgNbr5HRRLLOtCj
Mscw7YuSwtsFrVGI8lkZGXycVlklh+JGlye+kHD5e6KB/4LQj5ZJYt06k+mDetYh
rGqzRqcYe3ZZjrUHumCr4tqEK+gEArvfscmWVMx5nTBXMlAZQF3k2ficN5xyYIgU
gnoTEbcUtlIlO2uPWGUccH6hDb7Imu0bZW7+wWkrUwYOT2jhiOZRO3CRAYoDD8jV
OsxHjNbmfMBZpTBGRmfjTK2mjRtyCFcTgnN0uAMrFIGZQIh3TgP1CYWZJ6rxMA7j
SpIFn/z0mMMARHQcmv0JA52m/U0p6LNquMv9wdni+9ekcHAgA7rv75kJqBX153dG
AXHPc1lRCFFDG2XW7YLC/GiAsPxC7c9a/UIco2Nu1kBavIsh8zUSjKGS+jJ7ofKP
TY5Q8kNpeFqiWQeprmDRj0zRtYHALU/zYAXtXVnRiCl17xV10UiT1N11hM3w0mQ3
x34Uhn/Ue5ze0jNG1+ir
=m1ki
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: