On Tue 2019-10-22 23:03:49 +0200, Thomas Schmitt wrote:
> It does so for cross-table key matching, where MD5 suffices by all means
> of hash table theory.
I'm unaware of the meaning of "cross-table key matching", but it's known
to be relatively easy to find collisions in MD5.
If the adversary
Package: ftp.debian.org
Severity: normal
The Packages file is growing, and we would like to keep it smaller.
The MD5sum lines are vestigial at this point. Anything that they do
can be done better with the data from the SHA256sum lines.
Removal of the MD5sum lines would reduce the size of the
On Tue 2019-10-22 19:15:51 +0200, Thomas Schmitt wrote:
> Daniel Kahn Gillmor wrote:
>> I would even posit that temporarily breaking jigdo would be better than
>> keeping this additional bandwidth cost in play.
>
> To my knowledge, jigdo is the only way to get full DVD
On Sat 2018-01-20 13:06:06 +0100, Thomas Schmitt wrote:
> as described in
> https://lists.debian.org/debian-cd/2018/01/msg00021.html
> jigdo-file verifies the .template file and the resulting ISO image only
> by MD5 checksums which stem from the .jigdo file.
Apparently, the MD5 sums are only
On Fri 2019-10-18 09:56:31 -0400, Daniel Kahn Gillmor wrote:
> https://github.com/cabo/kramdown-rfc2629 suggests that version 1.2.12
> is available now, but debian unstable only has 1.2.9.
I've just uploaded 1.2.12-0.1 as an NMU to DELAYED/7.
I've also opened
https://salsa.debian.org/rub
Package: wnpp
Severity: normal
I am looking for external adoption of the python-dnsq package. I'm
assuming that Debian Python Modules Team (DPMT) is a reasonable
candidate if that group is interested.
The package description is:
dnsq is a high-level wrapper around dnspython for making caching
Package: lintian-brush
Version: 0.38
Severity: wishlist
Sometimes space-in-std-shortname-in-dep5-copyright shows up due to
people writing the license name as "Apache 2.0" or "GPL 3+", which
should be written as "Apache-2.0" and "GPL-3+", respectively.
lintian-brush ought to be able to detect
Package: ruby-kramdown-rfc2629
Version: 1.2.9-2
Severity: wishlist
Dear Maintainer,
https://github.com/cabo/kramdown-rfc2629 suggests that version 1.2.12
is available now, but debian unstable only has 1.2.9.
they are not complicated or large changes, but it would be nice to be
up to date :)
Package: xdg-utils
Version: 1.1.3-1
Severity: normal
Control: affects -1 gimp dekstop-file-utils xapers
Control: blocks 525077 by -1
different apps install .desktop files that contain a MimeType entry
that includes the same mime-types.
for example:
0 dkg@alice:~$ grep -l
Package: aiodns
Version: 1.1.1-1
Hi Tanguy--
aiodns 1.2.0 was released in January, and 2.0.0 was released in March.
It would be great to have an updated version of this package in debian.
Would you object to moving this packaging into the the Python module
packaging team on salsa? That should
Package: pycares
Version: 2.1.1-2
Control: affects -1 src:aiodns
Hi Tanguy--
pycares 3.0.0 was released in March. It would be great to have an
updated version of this package in debian.
Would you object to moving this packaging into the the Python module
packaging team on salsa? That should
On Sat 2019-10-05 10:21:05 -0700, Sean Whitton wrote:
> As an alternative to adding the integration tests, how about you use
> imap-dl on a daily basis for ~3 months with (I assume) a standard IMAP
> server, and if you don't have to make any nontrivial changes to the
> script during that time, we
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 src:publicsuffix
Please consider an update to publicsuffix in debian jessie.
This package reflects the state of the network, and keeping it current
is useful
Hi Willem--
On Tue 2019-10-01 06:50:29 +0200, Willem van den Akker wrote:
> I offer by help for maintaining packaging WG.
Thank you, happy to have help!
> Please let me know how I can help.
Please make sure you can build the package from the debian/master branch
at
rfcmarkup has been deprecated upstream, and will be replaced by
rfc2html, which can be found by svn at:
https://svn.tools.ietf.org/svn/src/rfc2html/trunk
If we want something like this in debian, it should probably be rfc2html
instead of rfcmarkup, which is why i'm closing #820153.
--dkg
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 src:publicsuffix
Please consider an update to publicsuffix in debian stretch.
This package reflects the state of the network, and keeping it current
is useful
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 src:publicsuffix
Please consider an update to publicsuffix in debian buster.
This package reflects the state of the network, and keeping it current
is useful
On Wed 2019-10-02 17:01:18 -0300, David Bremner wrote:
> Daniel Kahn Gillmor writes:
>
>> Thanks for this report. Do you want to recommend a specific behavior
>> for imap-dl in this login failure case? it sounds frustrating!
>
> I guess just a consistently formatted e
Package: clang-tools-8
Version: 1:8.0.1-3+b1
Severity: normal
File: /usr/share/clang/scan-build-8/bin/scan-build
Control: affects -1 src:wireguard
I'm running scan-build as part of "make check" in src/ of the
wireguard package. It terminates with this message:
Use of uninitialized value
On Wed 2019-10-02 16:05:06 +0800, Aron Xu wrote:
> I tried more to reproduce this bug, the problem only affect linux
> 4.19.0-0.bpo.4 and 4.19.0-0.bpo.5 (while I haven't tried earlier bpo
> versions), and does not affect 4.9 or 4.19.0-0.bpo.6
From Michel Meyers messages in this thread, it looks
On Tue 2019-10-01 10:21:31 -0300, David Bremner wrote:
> Here's the log about size mismatches. The only thing that jumps out at
> me is that it looks like the size mismatch doesn't get larger for big
> messages, so more like an additive error than multiplicative.
hm, only the first mismatch is
On Tue 2019-10-01 08:40:21 -0300, David Bremner wrote:
> Daniel Kahn Gillmor writes:
>> ok, in v2 of this patch, imap-dl will accept options.on_size_mismatch,
>> which can be either "exception" or "warn" or "none".
>>
>> If you
Package: torsocks
Version: 2.3.0-2+b1
Severity: normal
Control: affects + netcat-openbsd
On my system right now, nc is in a tight loop, burning 100% CPU:
```
0 dkg@alice:~$ strace -p 10348 -T -ttt 2>&1 | head
strace: Process 10348 attached
1569928260.402113 select(4, [3], NULL, NULL, NULL) = 1
On Thu 2019-08-08 23:17:00 -0400, Antoine Beaupré wrote:
> So if I could rephrase that bug, I'd say that gpg-agent is
> "sticky". Whenever it gets called first is what determines the TTY. If
> that TTY is messed up (because it gets called too early in the session),
> it's forever doomed and needs
Hi Sean--
Thanks for the review!
On Sat 2019-09-28 08:53:38 -0700, Sean Whitton wrote:
> I read through the script and I'm a bit apprehensive about the
> complexity involved in talking to the IMAP server, because it renders
> imap-dl significantly more complicated than anything else in
>
On Tue 2015-11-03 07:36:08 +0900, Daniel Kahn Gillmor wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Daniel Kahn Gillmor
>
> * Package name: pandoc2rfc
> Version : 2.14
> Upstream Author : Miek Gieben
> * URL : https://github.com/miek
On Mon 2019-09-16 22:27:49 -0300, David Bremner wrote:
> Daniel Kahn Gillmor writes:
>> If this is the case, and your server lies, and getmail is just confused,
>> perhaps we need to report a bug to getmail.
>
>> b) i can make imap-dl avoid this checking based on option i
getmail upstream appears to have no plans to convert to python3 in the
near future.
Some of us use only a minimal subset of features of getmail, and it
would be nice to have something simpler, with the main complexity
offloaded to the modern python3 stdlib.
Signed-off-by: Daniel Kahn Gillmor
Thanks for this, David.
On Mon 2019-09-16 10:04:10 -0300, David Bremner wrote:
> It looks like every message; see attached log. I haven't had a chance to
> try the patched imap-dl
It looks lke your server is indeed lying about the message size in the
initial summary.
It clearly says 41997
Thanks for the review!
On Sun 2019-09-15 21:39:33 -0300, David Bremner wrote:
> 1) It would be nice if path= supported ~ expansion, as getmail does;
> that's easy to work around for one machine, but it's harder to share
> configs between different machines.
gotcha, i've added that now:
diff
.
This allows those of us who use getmail to treat a remote IMAP store as
a POP message store to no longer depend on getmail (which is
python2-only at the time of this writing).
--dkg
From 0f17fac791cb6b2fd656b85d97c28f432571e750 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Sun, 15 Sep
Hi Sean--
On Sat 2019-09-14 09:19:01 -0700, Sean Whitton wrote:
> Can I get a Signed-off-by please?
>
> Please see CONTRIBUTING.md.
sure thing, please see the "use-https" branch on
https://salsa.debian.org/dkg/mailscripts.git
--dkg
signature.asc
Description: PGP signature
On Sat 2019-09-14 12:16:28 -0700, Sean Whitton wrote:
> Just fyi, I had to re-order your commits slightly for the sake of `git
> bisect`: you added the installation of the manpage before the commit
> which provided the manpage to be installed.
thanks for cleaning that up!
--dkg
On Sat 2019-09-14 09:27:02 -0700, Sean Whitton wrote:
> Yup, let's add this to mailscripts. Thank you for the idea and the
> work!
great!
> Yes. I'd be happy to merge and upload if you can just add a
> Signed-off-by: to *each* commit (per CONTRIBUTING.md).
ok, done, and force-pushed to an
>
Date: Sat, 14 Sep 2019 10:45:16 -0400 (EDT)
From: Daniel Kahn Gillmor
--161194241-1568472316=:825
Content-Type: text/plain; charset=UTF-8
Content-Disposition: attachment
Content-ID: <20190914104516.82...@alice.fifthhorseman.net>
Content-Transfer-Encoding: quoted-printable
this is
Hi David--
On Wed 2019-09-11 17:36:29 +0200, David Raison wrote:
>> But hm, maybe the 4.19.0-5 ABI wasn't actually stable? do either of you
>> (Matthew or David) know what version of 4.19.0-5 was actually running on
>> your system, vs. what version of linux-headers-4.19.0-5 you had
>> installed
Control: tags 939226 + confirmed
Control: affects 939226 + xdg-utils xapers
On Mon 2019-09-02 23:33:32 +1200, martin f krafft wrote:
> Trying to use the --action command line results in the following
> error being printed, as well as the tool exiting with exitcode
> -1/255:
>
> Can't use
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 src:publicsuffix
Please consider an update to publicsuffix in debian buster.
This package reflects the state of the network, and keeping it current
is useful
Over on https://bugs.debian.org/939845, On Wed 2019-09-11 00:26:18 -0400,
Matthew Gabeler-Lee wrote:
> Having a system update disable a network interface and fail to restore it is
> ... bad. Luckily I wasn't accessing the systems in question over that vpn!
i totally agree that this is bad.
Control: tags 939845 + moreinfo
On Wed 2019-09-11 00:33:19 -0400, Matthew Gabeler-Lee wrote:
> On Wed, 11 Sep 2019, Matthew Gabeler-Lee wrote:
>
>> Not sure if the common dkms scripts might be passing the KERNELRELEASE var
>> in a way that is messing up the build? In fairness, that seems ...
On Tue 2019-09-10 08:54:35 +0200, Michael Biebl wrote:
> wouldn't it be better if wireguard calls resolvctl directly?
> Then it knows exactly what kind of behaviour it'll get.
>
> You're right about the resolvconf.1 man page. We should not ship that in
> the systemd man page since we don't ship
Package: mailscripts
Version: 0.10-1
Severity: wishlist
Tags: patch
It's 2019, please use https!
Thanks for maintaining mailscripts.
--dkg
diff --git a/email-extract-openpgp-certs b/email-extract-openpgp-certs
index 2a95748..03b7753 100755
--- a/email-extract-openpgp-certs
+++
@@ -0,0 +1,77 @@
+#!/usr/bin/env python3
+# -*- coding: utf-8 -*-
+
+# Copyright (C) 2019 Daniel Kahn Gillmor
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version
Control: tag 939845 + moreinfo unreproducible
Hi David--
On Mon 2019-09-09 14:52:48 +0200, David Raison wrote:
> I upgraded the wireguard-dkms package during a regular apt upgrade,
> which seems to have produced an invalid module:
>
> Unpacking wireguard-dkms (0.0.20190905-1) over
Control: clone 930735 -1
Control: reassign -1 src:systemd
Control: severity -1 wishlist
Control: blocks 930735 with -1
Control: retitle -1 systemd should ship resolvconf symlink in some package
Control: affects -1 + wireguard-tools
Hi Willem--
Thanks for the followup.
It sounds to me like there
Control: retitle 921017 wireguard: wg setconf doesn't always set all allowed-ips
Control: reassign 921017 wireguard-tools
Hi Piotr--
On Mon 2019-09-09 12:40:30 +0200, Piotr Ożarowski wrote:
> yes, I can still replicate it with 0.0.20190905-1 but I do it on stable
> (first Stretch now Buster)
Version: 0.0.20190905-1
Over in 849...@bugs.debian.org, Daniel Kahn Gillmor wrote:
> I do plan for putting wireguard into buster-backports, since i expect
> the upstream inclusion issues to be resolved one way or another by the
> time of bullseye release. If anyone wants to help out
Control: tags 921017 + moreinfo unreproducible
Hi Piotr--
On Thu 2019-01-31 18:15:04 +0100, Piotr Ożarowski wrote:
> I have multiple peers defined in /etc/wireguard/wg0.conf
> but setting AllowedIPs doesn't fully work for some of them
> if I use `wg setconf`… and works perfectly fine if I do
Control: retitle 931440 dkms-built modules are not signed, do not work with
secureboot
Control: reassign 931440 dkms
Control: affects 931440 + wireguard-dkms src:wireguard
Control: tags 931440 + help
Hi Lizard--
On Fri 2019-07-05 01:32:58 +0100, hello i'm a lizard wrote:
> The wireguard kernel
On Sun 2019-09-01 13:24:14 +, Dmitry Bogatov wrote:
> Good. How urgent is fix? Can I just upload `dh-runit' into unstable and
> eventually fix will propagate to affected packages, or I have to request
> binNMU?
definitely start with a fix to unstable, but i don't know that it's
urgent to
Package: hopenpgp-tools
Version: 0.21.3-1
Severity: wishlist
RFC 4880 says:
In a V4 key, the primary key MUST be a key capable of certification.
(see https://tools.ietf.org/html/rfc4880#page-71)
"hokey lint" currently doesn't notice when the primary key's self-sig
does not have a
On Sat 2019-08-31 12:33:51 +0100, Adam D. Barratt wrote:
> I don't know if that will be in time, but while we wait feel free to
> upload so that the package is available if the timings turn out to be
> on our side.
uploaded now, thanks.
--dkg
signature.asc
Description: PGP signature
Hi Stephen--
On Thu 2019-08-29 23:18:53 +0200, Stephen Kitt wrote:
> Thanks for taking an interest in this, I’ve often wondered if I’d got my
> analysis right...
thanks for taking another look at this with me.
> But all this happens inside $tempdir, which is root:root 700. If anyone can
> race
On Mon 2016-01-25 18:20:11 +, Jelmer Vernooij wrote:
> The bzr bits have to be python2 because bzr is python 2 only at the moment.
>
> Bzr is optional though.
fwiw, i'd much rather see etckeeper shipping with python3 with bzr
disabled at this point. or maybe whatever folks need it to work
On Thu 2019-08-29 15:23:07 +, Dmitry Bogatov wrote:
> Thank you. I wasn't aware of such problems.
Thanks for the quick response, Dmitry.
> Then I plan to change script to following:
>
> 1 #!/bin/sh
> 2 chown runit-log:adm '/var/log/runit/tor'
> 3 chmod 750 '/var/log/runit/tor'
> 4 umask 0022
Package: rocksndiamonds
Version: 4.1.1.0+dfsg-1
the lintian override says:
# We recursively chown files to root:root after neutering their
# permissions, so the attacks mentioned by Lintian aren’t applicable
rocksndiamonds: maintainer-script-should-not-use-recursive-chown-or-chmod
postinst:340
Package: dh-runit
Version: 2.8.13.2
Tags: security
Control: affects -1 tor openssh-server
by default, dh-runit sets up logging runscripts like this:
1 #!/bin/sh
2 chown -R runit-log:adm '/var/log/runit/tor'
3 chmod 750 '/var/log/runit/tor'
4 chmod u+rw,g+r,o-rwx
ta loss, see
+ https://dev.gnupg.org/T4628 for more details.
+
+ -- Daniel Kahn Gillmor Wed, 21 Aug 2019 14:53:47
-0400
+
Let me know if you want me to re-generate a full debdiff, or if you're
ok with this plus the previous debdiff (with an updated date on
debian/changelog to match debian/NEWS
On Wed 2019-08-21 18:17:14 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Wed, 2019-08-21 at 13:05 -0400, Daniel Kahn Gillmor wrote:
>> Control: tags 931126 - moreinfo
>> Control: retitle 931126 unblock: enigmail/2:2.0.12+ds1~deb10u1
>
> The &quo
ypting/verifying quoted inline-PGP
+ - un-mangling MS Exchange: ensure that message structure is
+ as expected to avoid data loss
+ - only include Subject: line in legacy-display part for
+ protected headers
+ * move Vcs-Git fields to DEP-14 branch debian/buster
+ * refresh patches
+
+ -
On Tue 2019-08-20 22:36:07 +0200, Martin Höfling wrote:
> first of all, my bananapi 2 died and I will replace it, probably with a
> newer arm board.
ouch, sorry to hear that.
> Package: linux-headers-4.19.0-5-armmp-lpae
> Version: 4.19.37-5+deb10u1
>
> Package: linux-headers-4.19.0-5-common
>
Package: lintian
Version: 2.18.0
Severity: normal
Control: affects -1 src:wireguard
While resolving #930432 in the wireguard package, I noticed that the
code for lintian tag version-substvar-for-external-package appears to
only trigger if the dependency is on source:Version or binary:Version
but
Package: gitg
Version: 3.30.1-1
Severity: normal
try this (without any gitg instance already running):
$ git clone https://github.com/libreswan/libreswan
$ cd libreswan
$ gitg
The result is a bunch of lines like the following to stderr:
(gitg:27936): GLib-CRITICAL **:
Control: tags 932015 + moreinfo
Hi Martin--
On Sun 2019-07-14 02:26:05 +0200, Martin Hoefling wrote:
> Package: wireguard-dkms
> Version: 0.0.20190702-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Dear Maintainer,
>
>*
On Mon 2019-08-19 14:06:37 +0200, Markus Grundmann wrote:
> This is a new debian VM running on BHYVE. After the installation and
> upgrading operating system the following DKMS fails.
This is https://bugs.debian.org/934763, which i'll work around shortly
with the attached patch to the wireguard
Control: tags 934763 + confirmed
Control: clone 934763 -1
Control: reassign -1 linux-headers-4.9.0-9-common 4.9.168-1+deb9u5
Control: tags -1 + patch
Control: affects -1 + wireguard-dkms
On Wed 2019-08-14 17:50:08 +0300, Thomas Kapoulas wrote:
> Hello, wireguard-dkms failed to build its module on
Control: tags 928050 + wontfix
On Fri 2019-04-26 13:40:52 -0700, Anthony Metzidis wrote:
>* Upon attempting a build on raspbian-stretch, the build failed due to
> missing debhelper-compat=12 . debhelper-compat=12 is not available on
> raspbian
>* As a workaround, I removed the
Package: systemd
Version: 241-6
Severity: normal
Tags: upstream patch
Control: forwarded -1 https://github.com/systemd/systemd/issues/12784
from the journal:
-- Reboot --
Aug 19 10:55:17 tyr systemd[1]: Starting Network Service...
Aug 19 10:55:19 tyr systemd-networkd[230]: Enumeration completed
On Thu 2019-08-08 09:45:06 -0300, David Bremner wrote:
> I meant more specifically, the issue that this variable is only
> effective if your html converter is the default shr
Yes, this should be clearly documented, presumably in the documentation
text about the variable.
It would be even nicer
Package: lintian
Version: 2.17.0
Severity: wishlist
Over in #931954, Michael Biebl pointed out that the
move to debhelper 12 (which installs systemd user services) resulted in
a conflict with the old manual way of installing systemd user services.
It would be great if lintian could notice that
Control: tags 932474 - moreinfo
Control: tags 932474 + pending
On Tue 2019-07-30 16:53:34 -0400, Jeremiah C. Foster wrote:
> The document you point to shows our assignment of 0x316d as "Purism
> SPC". Of course our patch has to be updated accordingly -- please find
> attached an updated patch.
Package: python3-singledispatch
Version: 3.4.0.3-2
Control: affects -1 python3-librtmp python3-pecan python3-livestreamer
python 3.4 ships with singledispatch in functools.
python3-singledispatch is a backport of this functionality to python 2.6
- 3.3.
Since debian doesn't ship any older
On Sat 2019-07-27 21:52:55 +0100, Jonathan McDowell wrote:
> On Fri, Jul 26, 2019 at 09:18:29PM +0100, Sean Whitton wrote:
>> For the purposes of tag2upload work, would you mind confirming this:
>>
>> On Tue 23 Jul 2019 at 06:38AM +01, Sean Whitton wrote:
>>
>> > AIUI a fingerprint fails to
On Mon 2019-07-29 07:46:32 +0100, Sean Whitton wrote:
> Everything looks good, except that you didn't say you were happy for
> this to be under GPL-3+ rather than just GPL-3 -- are you okay with it
> being under GPL-3+?
yes, GPL-3+ is what i intended for email-extract-openpgp-certs. Thanks
for
On Sun 2019-07-21 15:55:28 -0400, Daniel Kahn Gillmor wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
> Control: affects -1 src:gnupg2
>
> The version of GnuPG in debian buster
Hi Sean--
On Thu 2019-07-25 18:22:14 +0100, Sean Whitton wrote:
> On Thu 25 Jul 2019 at 12:44PM -04, Daniel Kahn Gillmor wrote:
>
>> The attached patch supplies a python3 script for extracting OpenPGP
>> certificates from an rfc822/message input stream. I wrote it (with som
for wider distribution with the
mailscripts package.
Thanks for maintaining mailscripts!
--dkg
From ae2f662d2200fb7edc4f5cfff90e29e41bd5046f Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Thu, 25 Jul 2019 12:38:52 -0400
Subject: [PATCH] offer email-extract-openpgp-certs
On Mon 2019-06-03 12:35:45 -0400, Daniel Kahn Gillmor wrote:
> 0 dkg@alice:~$ grep CONFIG_XFRM_STATISTICS /boot/config-4.19.0-5-amd64
> # CONFIG_XFRM_STATISTICS is not set
> 0 dkg@alice:~$
>
> Paul Wouters, Libreswan upstream developer says:
>
>> Still this kernel optio
* debian/tests/gpgv-win32: make arch-specific (Closes: #905563)
-- Daniel Kahn Gillmor Sun, 21 Jul 2019 15:39:05
-0400
I recognize that this is a lot of changes, but upstream's 2.2 branch
is intended to be stable. (most of the GnuPG development work is
happening on the 2.3 branch, and most o
Package: debhelper
Version: 12.2.3
Severity: normal
https://tests.reproducible-builds.org/debian/dbd/unstable/i386/gnupg2_2.2.17-3.diffoscope.html
shows that the postinst script for gpg-agent, which has several
.socket units appears to be re-ordered depending on the different
build, in the
On Sat 2019-07-20 21:41:12 -0300, Jonathan Wiltshire wrote:
> Hi,
>
> On Mon, Jul 01, 2019 at 01:21:22PM -0400, Daniel Kahn Gillmor wrote:
>> On Sun 2019-06-30 20:01:21 +0200, Paul Gevers wrote:
>> > The time for unblocks for buster has come and gone. The deadline was
>&
Control: tags 932474 + moreinfo
Hi Jeremiah--
On Fri 2019-07-19 17:24:34 -0400, Jeremiah C. Foster wrote:
> I would like to add a USB VID:PID pair to the scdaemon package, please find a
> diff attached.
I'm really happy to see Librem getting this stuff working, and I'd be
happy to try to get
On Thu 2017-01-19 10:13:09 +0530, Deepak Gaur wrote:
> The problem comes with powerpc toolchain it seems. With MIPS toolchain it is
> getting cross - compiled easily. I don't
> have a native compiler on-board target hence won't be able to provide
> lock-obj-pub.powerpc-*.h
Over on
On Thu 2017-12-07 16:24:46 -0500, Daniel Kahn Gillmor wrote:
> Can you suggest a patch that would have helped you to avoid the problem?
it's been a year and a half with no followup and debian bug #883571 is
still in a moreinfo,unreproducible state. so i'm closing this bug
report. If anyone
Package: blhc
Version: 0.09-1
Severity: wishlist
Control: -1 affects + src:libgpg-error src:libassuan
libgpg-error and libassuan both use $(CC_FOR_BUILD) to compile helper
tools during build, like header generators.
Those helper programs are never redistributed, and probably do not
need all the
Package: wine64
Version: 4.0-2
Severity: normal
wine64(1) says:
WINESERVER
Specifies the path and name of the wineserver binary. If not
set, Wine will try to load /usr/lib/wine/wineserver, and if this
doesn't exist it will then look for a file
On Tue 2019-07-09 11:58:46 +0200, Emmanuel Revah wrote:
> I've followed these steps carefully, on 2 computers, both on Debian
> Buster, 64 bit. The only thing that seems logic to me is that there
> might be an issue with pinentry-qt itself.
>
> If I remove all pinentry-* except for qt and clean
Hi Maximilian--
On Wed 2019-07-10 10:12:37 +0200, Maximilian Krambach wrote:
> I have been tasked to prepare "debian packages" for the gpgme-json browser
> integration, to ease installation of native messaging between gnupg and
> browser
> extensions.
great, thanks for working on this! I
Package: python-django-doc
Version: 2:2.2.3-2
on upgrading to the above package, on a system with doc-base 0.10.8:
Processing 9 changed doc-base files...
Error in `/usr/share/doc-base/python-django-doc', line 19: all `Format'
sections are invalid.
Note: `install-docs --verbose --check
Package: monkeysphere
Version: 0.44-1
Severity: wishlist
Given the ongoing troubles with OpenPGP certificate distribution (SKS
certificate flooding, etc), it would be good to have a way to manually
inject certificates that the monkeysphere-authentication subsystem could
know about.
It would also
Package: gnupg-utils
Version: 2.2.16-2
migrate-pubring-from-classic-gpg fails partway through if any cert in
pubring.gpg is > 5MiB, because the keybox format has a 5MiB limit per
OpenPGP certificate, which was not enforced in the old pubring.gpg
format.
migrate-pubring-from-classic-gpg should be
On Sun 2019-06-30 20:01:21 +0200, Paul Gevers wrote:
> The time for unblocks for buster has come and gone. The deadline was
> last Tuesday, we are now in deep freeze and we were not able to process
> your unblock request and give it an exception. I assume this should be
> fixed via the security
Package: hopenpgp-tools
Version: 0.21.3-1
Severity: wishlist
"hot armor" currently adds a comment line to its enarmored content:
Version: hot 0.21.3
Best practices these days omits indicators of what particular OpenPGP
implementation is in use. Please do not emit it by default!
Package: hopenpgp-tools
Version: 0.21.3-1
Severity: wishlist
I'm looking at performance tests on large (spammed/flooded)
certificates. hopenpgp-tools consumes more CPU than GnuPG by a factor
of 2×, 5×, or 10× depending on the operation.
I provide these figures as a target for hopenpgp to meet
Package: gnupg
Version: 2.2.16-2
Control: clone -1 -2
Control: affects -1 monkeysphere enigmail sks
Control: found -1 2.2.13-2
Control: found -1 2.2.12-1
Control: found -1 2.1.18-8~deb9u4
Control: forwarded -1 https://dev.gnupg.org/T4592
Control: reassign -2 monkeysphere 0.41-1
Control: retitle -2
On Thu 2019-06-27 10:28:43 +0200, Emmanuel Revah wrote:
> In .gnupg/gpg-agent.conf I went from "pinentry-program pinentry-qt" to
> "pinentry-program pinentry".
"pinentry-program pinentry" is probably the same as no line at all (it
is the default). I strongly recommend sticking with the simplest
On Wed 2019-06-26 14:03:09 -0400, Daniel Kahn Gillmor wrote:
> * gcr prefers to grab the desktop inputs, to avoid other
> processes snooping on your password as it is typed. it's not clear
sorry, this last sentence got cut off. it was:
it's not clear to me how to use gcr in
On Tue 2019-06-25 22:35:44 +0200, Moritz Mühlenhoff wrote:
> Buster still has 2.0.10, what's the plan for it
I've just filed https://bugs.debian.org/931126 to unblock for buster.
> (and for stretch), should we fix this in older releases?
Given that we're updating thunderbird in stable, yes, we
Control: reassign 930062 pinentry-gnome3
Control: retitle 930062 pinentry-gnome3 grabs keyboard and mouse input despite
--no-global-grab or 'OPTION no-grab'
Control: forwarded 930062 https://dev.gnupg.org/T4587
Hi Emmanuel--
Thanks for the report! An explanation follows, along with some
able; urgency=medium
+
+ * minimize legacy-display protected headers for encrypted mails
+
+ -- Daniel Kahn Gillmor Thu, 30 May 2019 15:40:57 -0400
+
+enigmail (2:2.0.11+ds1-1) unstable; urgency=medium
+
+ * new upstream release
+ * refresh patches
+ * use the older import-show with --dry-run
601 - 700 of 4323 matches
Mail list logo
