Accepted tlsdate 0.0.13-1 (source) into unstable

2015-05-29 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 May 2015 19:02:28 + Source: tlsdate Binary: tlsdate Architecture: source Version: 0.0.13-1 Distribution: unstable Urgency: high Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Accepted tlsdate 0.0.12-1 (source) into unstable

2014-10-26 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Oct 2014 15:03:41 + Source: tlsdate Binary: tlsdate Architecture: source Version: 0.0.12-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Accepted tlsdate 0.0.11-2 (source) into unstable

2014-10-21 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Oct 2014 12:53:17 + Source: tlsdate Binary: tlsdate Architecture: source Version: 0.0.11-2 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Accepted tlsdate 0.0.8-1 (source) into unstable

2014-09-14 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 14 Sep 2014 16:48:32 + Source: tlsdate Binary: tlsdate Architecture: source Version: 0.0.8-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Re: myth(?): places in the world where https is illegal? Re: people.debian.org will move from ravel to paradis and become HTTPS only

2014-07-21 Thread Jacob Appelbaum
On 7/21/14, Holger Levsen hol...@layer-acht.org wrote: Hi Iain, On Sonntag, 20. Juli 2014, Iain R. Learmonth wrote: The main one is that there are places in the world you just can't use HTTPS for legal reasons [...] I'm curious, can you name one? I'm also curious - is there a Debian

Re: myth(?): places in the world where https is illegal? Re: people.debian.org will move from ravel to paradis and become HTTPS only

2014-07-21 Thread Jacob Appelbaum
On 7/21/14, Iain R. Learmonth i...@fsfe.org wrote: On Mon, Jul 21, 2014 at 01:12:37PM +0200, Holger Levsen wrote: Hi Iain, On Sonntag, 20. Juli 2014, Iain R. Learmonth wrote: The main one is that there are places in the world you just can't use HTTPS for legal reasons [...] I'm

Re: myth(?): places in the world where https is illegal? Re: people.debian.org will move from ravel to paradis and become HTTPS only

2014-07-21 Thread Jacob Appelbaum
On 7/21/14, Iain R. Learmonth i...@fsfe.org wrote: Hi Jacob, On Mon, Jul 21, 2014 at 01:14:14PM +, Jacob Appelbaum wrote: I believe you are mistaken. My understanding is that you're not supposed to use crypto on the radio layer and IP packets are already several layers away from

Re: use of RDRAND in $random_library

2014-06-14 Thread Jacob Appelbaum
On 6/13/14, Theodore Ts'o ty...@mit.edu wrote: On Fri, Jun 13, 2014 at 06:51:44PM +, Jacob Appelbaum wrote: I would expect that if the NSA wanted to take control of the RDRAND or the rest of the CPU, they'd dynamically update the microcode in the CPU to change how it behaves. To do

Re: use of RDRAND in $random_library

2014-06-13 Thread Jacob Appelbaum
On 6/13/14, Theodore Ts'o ty...@mit.edu wrote: On Fri, Jun 13, 2014 at 10:09:02AM +0200, Martijn van Oosterhout wrote: Excuse me if I'm blunt here, but I understand that, on the point of using entropy to seed a PRNG, if you have several shitty entropy sources and one _really_ good one, and

Re: use of RDRAND in $random_library

2014-06-11 Thread Jacob Appelbaum
On 6/11/14, Joey Hess jo...@debian.org wrote: I stumbled over a library which has switched to using RDRAND in a new upsteam version (not yet packaged), instead of /dev/urandom[1]. Which library is using it? I don't have a stong opinion on the security of RDRAND, which is a contentious topic

Accepted torbrowser-launcher 0.0.7-1 (source all)

2014-06-11 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 11 Mar 2014 18:54:47 + Source: torbrowser-launcher Binary: torbrowser-launcher Architecture: source all Version: 0.0.7-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob

Re: goals for hardening Debian: ideas and help wanted

2014-04-28 Thread Jacob Appelbaum
On 4/25/14, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote: previously on this list Paul Wise contributed: I have written a non-exhaustive list of goals for hardening the Debian distribution, the Debian project and computer systems of the Debian project, contributors and users.

Accepted blockfinder 3.14159-1 (source all)

2014-04-04 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Mar 2014 15:22:21 + Source: blockfinder Binary: blockfinder Architecture: source all Version: 3.14159-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Accepted novena-eeprom 1.0-1 (source amd64)

2014-04-04 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Mar 2014 12:08:44 + Source: novena-eeprom Binary: novena-eeprom Architecture: source amd64 Version: 1.0-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum

Accepted golang-xmpp-dev 0.0~git20140304-1 (source all)

2014-03-06 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Mar 2014 16:06:45 + Source: golang-xmpp-dev Binary: golang-xmpp-dev Architecture: source all Version: 0.0~git20140304-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed

Accepted torbirdy 0.1.2-1 (source all)

2014-03-04 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 21 Feb 2014 17:43:54 + Source: torbirdy Binary: xul-ext-torbirdy Architecture: source all Version: 0.1.2-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Accepted tlsdate 0.0.7-1 (source amd64)

2014-02-28 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 02 Nov 2013 01:26:22 +0100 Source: tlsdate Binary: tlsdate Architecture: source amd64 Version: 0.0.7-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Re: when will we finally throw away binary uploads (Re: Please upgrade your build environment when you are affected by transition

2014-02-13 Thread Jacob Appelbaum
No kidding! How many uploaded binaries might include malware? A lack of binary determinism in the build process basically ensures that it isn't feasible to discover an answer to this question. :( All the best, Jacob On 2/13/14, Holger Levsen hol...@layer-acht.org wrote: Hi, On Donnerstag,

Re: when will we finally throw away binary uploads (Re: Please upgrade your build environment when you are affected by transition

2014-02-13 Thread Jacob Appelbaum
On 2/13/14, Jakub Wilk jw...@debian.org wrote: * Jacob Appelbaum ja...@appelbaum.net, 2014-02-13, 18:36: How many uploaded binaries might include malware? *shrug* It's not like it's difficult to hide malicious code in source packages. It is much harder for you to hide source code changes

Re: when will we finally throw away binary uploads (Re: Please upgrade your build environment when you are affected by transition

2014-02-13 Thread Jacob Appelbaum
Heya Sam, On 2/14/14, Sam Hartman hartm...@debian.org wrote: All rants aside, I believe there's a fairly wide agreement that we should throw away binaries from builds. I'd encourage something slightly different and then I'd expand on it a bit. I think it would be useful to have an historical

Re: when will we finally throw away binary uploads (Re: Please upgrade your build environment when you are affected by transition

2014-02-13 Thread Jacob Appelbaum
On 2/14/14, Paul Tagliamonte paul...@debian.org wrote: On Fri, Feb 14, 2014 at 04:44:21AM +, Jacob Appelbaum wrote: Heya Sam, On 2/14/14, Sam Hartman hartm...@debian.org wrote: All rants aside, I believe there's a fairly wide agreement that we should throw away binaries from builds

Re: Bug#733860: ITP: pond -- Forward secure, asynchronous messaging for the discerning.

2014-01-02 Thread Jacob Appelbaum
Philip Rinn: Hi, I think it's important to add also the paragraph about actual usability for the homepage: Dear God, please don't use Pond for anything real yet. I've hammered out nearly 20K lines of code that have never been reviewed. Unless you're looking to experiment you should

Accepted tlsdate 0.0.5-1 (source amd64)

2013-01-28 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 22 Jan 2013 23:08:21 +0100 Source: tlsdate Binary: tlsdate Architecture: source amd64 Version: 0.0.5-1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Accepted tlsdate 0.0.4-1 (source amd64)

2012-12-09 Thread Jacob Appelbaum
-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 ja...@appelbaum.net Changed-By: Jacob Appelbaum ja

Accepted aeskeyfind 1.0.0-1 (source i386)

2009-08-10 Thread Jacob Appelbaum
-By: Jacob Appelbaum ja...@appelbaum.net Description: aeskeyfind - tool for finding and repairing AES keys Closes: 495416 Changes: aeskeyfind (1.0.0-1) unstable; urgency=low . * Initial release (Closes: #495416) * Adjusted the Makefile to add $DESTDIR Checksums-Sha1

Accepted rsakeyfind 1.0.0-1 (source i386)

2009-08-10 Thread Jacob Appelbaum
-By: Jacob Appelbaum ja...@appelbaum.net Description: rsakeyfind - tool for finding and repairing AES keys Closes: 495418 Changes: rsakeyfind (1.0.0-1) unstable; urgency=low . * Initial release (Closes: #495418) * Adjusted the Makefile to add $DESTDIR * Added a man page. Checksums-Sha1

Accepted aesfix 1.0.1-1 (source i386)

2009-08-10 Thread Jacob Appelbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 17 Aug 2008 21:02:09 -0300 Source: aesfix Binary: aesfix Architecture: source i386 Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Debian Forensics forensics-de...@lists.alioth.debian.org Changed-By: Jacob

Bug#495416: ITP: AESKeyFinder -- A tool for finding and reconstructing AES keys.

2008-08-17 Thread Jacob Appelbaum
Package: wnpp Severity: wishlist Owner: Debian Forensics [EMAIL PROTECTED] * Package name: AESKeyFinder Version : 1.0.0 * URL : http://citp.princeton.edu/memory/code/ * License : BSD Programming Lang: C Description : A tool for finding and repairing AES

Bug#495418: ITP: RSAKeyFinder -- A tool for locating RSA private and public keys.

2008-08-17 Thread Jacob Appelbaum
Package: wnpp Severity: wishlist Owner: Debian Forensics [EMAIL PROTECTED] * Package name: RSAKeyFinder Version : 1.0.0 * URL : http://citp.princeton.edu/memory/code/ * License : BSD Programming Lang: C++ Description : A tool for locating RSA private and

Bug#495419: ITP: AESFix -- A tool for correcting bit errors in an AES key schedule.

2008-08-17 Thread Jacob Appelbaum
Package: wnpp Severity: wishlist Owner: Debian Forensics [EMAIL PROTECTED] * Package name: AESFix Version : 1.0.1 * URL : http://citp.princeton.edu/memory/code/ * License : BSD Programming Lang: C++ Description : A tool for correcting bit errors in an AES

Bug#495422: ITP: biosmemimage -- Tools for capturing memory dumps on x86 and x86-64 systems

2008-08-17 Thread Jacob Appelbaum
Package: wnpp Severity: wishlist Owner: Jacob Appelbaum [EMAIL PROTECTED] * Package name: biosmemimage Version : 1.0.0 * URL : http://citp.princeton.edu/memory/code/ * License : BSD Programming Lang: C Description : Tools for capturing memory dumps on x86