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

Bug#918744: marked as done (stretch-pu: package opensc/0.1.9-1~deb9u1)

Your message dated Tue, 16 Jun 2020 21:21:46 +0100
with message-id <dcd9a3539a4390d943b2b34edbecd2bb83a0b3a6.camel@adam-barratt.org.uk>
and subject line Re: Bug#918744: stretch-pu: package opensc/0.1.9-1~deb9u1
has caused the Debian Bug report #918744,
regarding stretch-pu: package opensc/0.1.9-1~deb9u1
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.)


-- 
918744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918744
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian.org@packages.debian.org
Usertags: pu

Dear release team,

I'd like to update opensc in stretch to 0.1.9-1~deb9u1 in order to fix a
regression that introduced with the last update, 0.1.6-3+deb9u1, in an
attempt to fix security issues (see #910786 for details).

I am aware that this is by no means a minimal change. I have tried to
fix the backported patch that broke Yubikey NEO support for me, but I
have not been able to restore functionality without reverting the patch
that fixed a CVE-worthy buffer overflow.

Because I own no other smartcard hardware, I cannot tell if the other
patches that were introduced with 0.16.0-3+deb9u1 broke any other
hardware support.

The .debian.tar.xz is attached. Given the size of the effective change,
a debdiff does not seem to make a lot of sense. I have not done an
upload yet.

Cheers,
-Hilko

Attachment: opensc_0.19.0-1~deb9u1.debian.tar.xz
Description: application/xz


--- End Message ---
--- Begin Message --- 
On Tue, 2020-06-16 at 21:26 +0200, Hilko Bengen wrote:
> * Adam D. Barratt:
> 
> > > Reading through the changelog between the two Debian versions,
> > > there
> > > are several changes that we normally would not consider,
> > > including a
> > > switch to Debhelper 11 and a change of supported OpenSSL version.
> > > 
> > > In order to try and assess the practical impact, would it be
> > > possible
> > > to have a binary debdiff between the current packages and your
> > > proposed
> > > upload.
> > 
> > That was over a year ago now, and there doesn't appear to have been
> > any
> > further response.
> > 
> > We're now planning for the final point release for stretch before
> > it
> > moves to LTS status, so it may be too late to handle this in
> > practical
> > terms.
> 
> Sorry for forgetting.
> 
> I'm inclined to leave this unresolved.
> 
> I'm assuming that that most if not all users who have run into the
> YubiKey/OpenSC problems have upgraded to buster (or beyond) or solved
> their problems otherwise.

I think that sounds fair under the circumstances. Let's close this now
then. Thanks for your work on this.

Regards,

Adam

--- End Message ---
Reply to: