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

Bug#670367: marked as done (pu: package coolkey/1.1.0-6)

Your message dated Wed, 2 Oct 2013 00:56:22 +0200
with message-id <20131001225622.GW3076@mraw.org>
and subject line Re: Bug#670367: pu: package coolkey/1.1.0-6
has caused the Debian Bug report #670367,
regarding pu: package coolkey/1.1.0-6
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.)


-- 
670367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670367
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: pu
Severity: normal

Coolkey 1.1.0-6 in Debian stable lacks support for new Gemalto TOPDLGX4 144K CAC cards.

People who have been using coolkey in Debian are likely to have these new cards, as
the old cards have an expiration date and will be replaced with the new hardware.

Coolkey 1.1.0-12 in Debian wheezy/sid supports both the old and new card hardware.

Not fixing this problem in Debian stable will mean that as new cards are issued,
formerly happy coolkey users will have their browsers crash, as the new hardware
exposes a grave bug in coolkey.

I have good results with my own squeeze backport - but since I am new to the 
stable proposed updates process I would like advice from the release team on what
version number I should use to upload to stable. I'll post the package diff
to this bug soon...

- -Maitland


- -- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.9 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAk+XQOQACgkQkwbJvNrxBUyXrwCfcrC/Bkbb1K4tppDrJzxz2N6f
eIQAn1ul6vMn3nrYAqwlG3FWvlPOc+rw
=7xf/
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Adam D. Barratt <adam@adam-barratt.org.uk> (2012-05-03):
> Apparently that review process didn't notice - or didn't care about -
> the fact that the changes in the above patch cause an ABI break in
> libckyapplet1.  The Debian packages should really have changed SONAME at
> that point; looking at the packages in testing/sid, it appears that
> didn't happen.  This would also be an issue for partial squeeze to
> wheezy upgrades already - installing wheezy's libckyapplet1 on a system
> with squeeze's coolkey will break if the affected functions are called.
> 
> Specifically:
> 
> 459	 CKYStatus
> 460	-CACAppletFactory_SignDecrypt(CKYAPDU *apdu, const void *param)
> 461	+CACAppletFactory_SignDecryptStep(CKYAPDU *apdu, const void *param)
> [...]
> 467	+CKYStatus
> 468	+CACAppletFactory_SignDecryptFinal(CKYAPDU *apdu, const void *param)
> [...]
> 955	CKYStatus
> 956	-CACAPDUFactory_SignDecrypt(CKYAPDU *apdu, const CKYBuffer *data)
> 957	+CACAPDUFactory_SignDecrypt(CKYAPDU *apdu, CKYByte type, const CKYBuffer *data)
> 
> Both CACAPDUFactory_SignDecrypt and CACAppletFactory_SignDecrypt are
> exported from the library.

Given that was almost 1.5y ago, and that I believe we won't knowingly
break ABI in (old)stable, I'm closing this bug report.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: