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

Bug#681000: marked as done (ITP: tlsdate -- secure parasitic rdate replacement)

Your message dated Sun, 09 Dec 2012 16:00:06 +0000
with message-id <E1ThjIU-0000lF-Ot@franck.debian.org>
and subject line Bug#681000: fixed in tlsdate 0.0.4-1
has caused the Debian Bug report #681000,
regarding ITP: tlsdate -- secure parasitic rdate replacement
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.)


-- 
681000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681000
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Jacob Appelbaum <jacob@appelbaum.net>

* Package name    : tlsdate
  Version         : 0.0.1
  Upstream Author : Jacob Appelbaum <jacob@appelbaum.net>
* URL             : https://www.github.com/ioerror/tlsdate
* License         : BSD
  Programming Lang: C
  Description     : secure parasitic rdate replacement

tlsdate sets the local clock by securely connecting with TLS to remote
servers and extracting the remote time out of the secure handshake.
Unlike ntpdate, tlsdate uses TCP and verifies all data with
cryptographic signatures.

--- End Message ---
--- Begin Message --- 
Source: tlsdate
Source-Version: 0.0.4-1

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

Debian distribution maintenance software
pp.
Jacob Appelbaum <jacob@appelbaum.net> (supplier of updated tlsdate 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@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 16 Nov 2012 02:00:00 -0800
Source: tlsdate
Binary: tlsdate
Architecture: source amd64
Version: 0.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Jacob Appelbaum <jacob@appelbaum.net>
Changed-By: Jacob Appelbaum <jacob@appelbaum.net>
Description: 
 tlsdate    - secure parasitic rdate replacement
Closes: 681000
Changes: 
 tlsdate (0.0.4-1) unstable; urgency=low
 .
   * Initial release (Closes: #681000)
   * New upstream version.
   * Merge in all git fixes after 0.0.4 to fix various lintian issues.
Checksums-Sha1: 
 e4a0c1083287b5a279b69dfc7bac507842e4330c 1125 tlsdate_0.0.4-1.dsc
 3f65090416bdd6becba818a3063c56b2db6ac41a 474325 tlsdate_0.0.4.orig.tar.gz
 433db2e8c028bca606bbbb4867f0c962d4c1b0ee 9741 tlsdate_0.0.4-1.debian.tar.gz
 aac308c1462270f40b1b5d75a7c243ae594043c0 197492 tlsdate_0.0.4-1_amd64.deb
Checksums-Sha256: 
 a8d0eda6cb5e73c9a4f14e19cf4a7ba3583573f766c70aeba5da659e5da111b9 1125 tlsdate_0.0.4-1.dsc
 bf774354964b006687bf38e081e6b611464b076bb938c0c99b27a78054e7a90e 474325 tlsdate_0.0.4.orig.tar.gz
 8010a060029f0847b30ff8e3dbcab3d0e3e135d545366741142ba5ec57a99169 9741 tlsdate_0.0.4-1.debian.tar.gz
 146ff45682e0b2d428bdc26b468e40741252223022c72a14b6ad23ae2740b996 197492 tlsdate_0.0.4-1_amd64.deb
Files: 
 4b96e9bb602e4a285253046532885ff4 1125 net extra tlsdate_0.0.4-1.dsc
 060bbbe4ca9c0fff12503a273078c0e0 474325 net extra tlsdate_0.0.4.orig.tar.gz
 dfe8a40b41ab92677350619b239a1f80 9741 net extra tlsdate_0.0.4-1.debian.tar.gz
 d94fb18762c8bd3366b9d3ce456cee88 197492 net extra tlsdate_0.0.4-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlCu/2QACgkQoRg/jtECjI1LJQCeL9rFPL1wyVImY7jWALkK3ci1
p6oAoIx1gbsoBDKAiRodpqQj3FxsOOlP
=lUP9
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: