FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 05-17-2011, 07:29 AM
Godfrey Chung
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Package: wnpp
Severity: wishlist
Owner: Godfrey Chung <godfrey.chung@acs.com.hk>


* Package name : libacsccid
Version : 1.0.2
Upstream Author : Advanced Card Systems Ltd. <info@acs.com.hk>
* URL : http://www.acs.com.hk/
* License : LGPL-2.1
Programming Lang: C
Description : PC/SC driver for ACS USB CCID smart card readers

This library provides a PC/SC IFD handler implementation for the ACS USB smart
card readers compliant to the CCID protocol.

This package is needed to communicate with the ACS CCID smartcard readers
through the PC/SC Lite resource manager (pcscd).



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110517072952.31404.48239.reportbug@debian.acshko ">http://lists.debian.org/20110517072952.31404.48239.reportbug@debian.acshko
 
Old 05-17-2011, 10:09 AM
Hendrik Sattler
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Zitat von Godfrey Chung <godfrey.chung@acs.com.hk>:

Package: wnpp
Severity: wishlist
Owner: Godfrey Chung <godfrey.chung@acs.com.hk>


* Package name : libacsccid
Version : 1.0.2
Upstream Author : Advanced Card Systems Ltd. <info@acs.com.hk>
* URL : http://www.acs.com.hk/
* License : LGPL-2.1
Programming Lang: C
Description : PC/SC driver for ACS USB CCID smart card readers

This library provides a PC/SC IFD handler implementation for the ACS
USB smart

card readers compliant to the CCID protocol.

This package is needed to communicate with the ACS CCID smartcard readers
through the PC/SC Lite resource manager (pcscd).


Does libccid not work for your reader? If it doesn't, maybe reword the
description about the differences to libccid (which should support
CCID compliant devices).


The URL above only links to the main page of the vendor. Can it be a
bit more specific (the URL where you got the source from)?


HS



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110517120941.20100vn51cac8ghw@v1539.ncsrv.de">ht tp://lists.debian.org/20110517120941.20100vn51cac8ghw@v1539.ncsrv.de
 
Old 05-18-2011, 07:46 AM
Hendrik Sattler
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Hi,

Zitat von Godfrey Chung <godfrey.chung@acs.com.hk>:

Yes, libccid works for a few models only while libacsccid works for
all models of ACS CCID smart card readers.


You can download the drivers from
http://www.acs.com.hk/index.php?pid=drivers. For example, select
ACR122U (http://www.acs.com.hk/index.php?pid=drivers&id=ACR122U) and
you will find the driver
(http://www.acs.com.hk/drivers/eng/ACR122U_driver_Lnx_Mac10.5_10.6_1.02_P.zip). The driver "acsccid-1.0.2.tar.bz2" is in the zip
file.


I am a maintainer of the driver. acsccid-1.0.2 is based on
ccid-1.3.11 and supports all models of ACS CCID smart card readers.
The driver is tested by software and hardware engineers from ACS.


I figured from your mail address that ACS is directly involved here.
OTOH, why are those changes not pushed to libccid upstream? For
generic protocols like CCID (where even Windows has a generic driver
for it), there should not be a driver set for each vendor, it simply
defeats the purpose of generic protocols like that.


Your example of ACR122U is marked as "should work" at
http://pcsclite.alioth.debian.org/ccid/iManufacturer.html#2

If the libccid upstream is not cooperative for including your changes
(if it's done in a clean way), maybe you can work with the Debian
libccid maintainer?


HS



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110518094650.47921ux2i5xma6is@v1539.ncsrv.de">ht tp://lists.debian.org/20110518094650.47921ux2i5xma6is@v1539.ncsrv.de
 
Old 05-18-2011, 08:21 AM
"Godfrey Chung"
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Before we started the driver project in 2009, we had requested to join as a
developer for libccid in alioth.debian.org but the author rejected us with
no reason. As the same time, our customer pushed us to release Linux driver.
Therefore, we decided to release our Linux driver based on libccid and had a
plan to release our driver to any Linux Distributions.


For the Windows platform, we also release our own driver. It is because the
generic driver does not work with multi-slot smart card readers and we can
control our driver source code to fix bugs from the readers.


Please note that libccid upstream author and Debian maintainer are same
person. He may reject our changes.


Godfrey

-----Original Message-----
From: Hendrik Sattler

Sent: Wednesday, May 18, 2011 3:46 PM
To: Godfrey Chung
Cc: 627038@bugs.debian.org ; debian-devel@lists.debian.org
Subject: Re: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID
smart card readers


Hi,

Zitat von Godfrey Chung <godfrey.chung@acs.com.hk>:

Yes, libccid works for a few models only while libacsccid works for all
models of ACS CCID smart card readers.


You can download the drivers from
http://www.acs.com.hk/index.php?pid=drivers. For example, select ACR122U
(http://www.acs.com.hk/index.php?pid=drivers&id=ACR122U) and you will
find the driver
(http://www.acs.com.hk/drivers/eng/ACR122U_driver_Lnx_Mac10.5_10.6_1.02_P.zip).
The driver "acsccid-1.0.2.tar.bz2" is in the zip file.


I am a maintainer of the driver. acsccid-1.0.2 is based on ccid-1.3.11
and supports all models of ACS CCID smart card readers. The driver is
tested by software and hardware engineers from ACS.


I figured from your mail address that ACS is directly involved here.
OTOH, why are those changes not pushed to libccid upstream? For
generic protocols like CCID (where even Windows has a generic driver
for it), there should not be a driver set for each vendor, it simply
defeats the purpose of generic protocols like that.

Your example of ACR122U is marked as "should work" at
http://pcsclite.alioth.debian.org/ccid/iManufacturer.html#2

If the libccid upstream is not cooperative for including your changes
(if it's done in a clean way), maybe you can work with the Debian
libccid maintainer?

HS



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 79A371CA9F0942B28C1C4E9401C36BB2@GODFREYPC">http://lists.debian.org/79A371CA9F0942B28C1C4E9401C36BB2@GODFREYPC
 
Old 05-18-2011, 08:48 AM
Hendrik Sattler
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Zitat von Godfrey Chung <godfrey.chung@acs.com.hk>:

Before we started the driver project in 2009, we had requested to
join as a developer for libccid in alioth.debian.org but the author
rejected us with no reason. As the same time, our customer pushed us
to release Linux driver. Therefore, we decided to release our Linux
driver based on libccid and had a plan to release our driver to any
Linux Distributions.


But libccid evolves and forks of such projects do usually not follow.
This leaves both in a rather sad situation. Did you track the changes
of 1.3.12 and 1.3.13? Any intention to rebase the work on 1.4.x so
libusb-1.0 gets used instead of libusb-0.1?


For the Windows platform, we also release our own driver. It is
because the generic driver does not work with multi-slot smart card
readers and we can control our driver source code to fix bugs from
the readers.


The Windows driver is also not very standard-compliant and does nasty
things. It took me 30min on XP and Vista to get a bluescreen from it :-/
Note that there is also libusb-win32, making it potentially possible
to use the same source there (ignoring the Microsoft driver for it)
once it is compatible with (or integrated into) libusb-1.0.


Please note that libccid upstream author and Debian maintainer are
same person. He may reject our changes.


Let's CC him so that he can comment...

HS



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110518104806.17831ti5w4pzq95w@v1539.ncsrv.de">ht tp://lists.debian.org/20110518104806.17831ti5w4pzq95w@v1539.ncsrv.de
 
Old 05-18-2011, 09:56 AM
Ludovic Rousseau
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Hello,

2011/5/18 Hendrik Sattler <post@hendrik-sattler.de>:
> Zitat von Godfrey Chung <godfrey.chung@acs.com.hk>:
>
>> Before we started the driver project in 2009, we had requested to join as
>> a developer for libccid in alioth.debian.org but the author rejected us with
>> no reason. As the same time, our customer pushed us to release Linux driver.
>> Therefore, we decided to release our Linux driver based on libccid and had a
>> plan to release our driver to any Linux Distributions.

Godfrey, I do not remember rejecting your request. The normal steps
are first to send good patches to the project before requesting to
join. You do not need to be on alioth.debian.org to participate to the
development of libccid.

Godfrey, do you participate on the MUSCLE (Movement for Using Smart
Card in a Linux Environment) mailing list [1]?

I could not find any message from "Godfrey Chung" in my email archives.

> But libccid evolves and forks of such projects do usually not follow. This
> leaves both in a rather sad situation. Did you track the changes of 1.3.12
> and 1.3.13? Any intention to rebase the work on 1.4.x so libusb-1.0 gets
> used instead of libusb-0.1?

Good question.

>> Please note that libccid upstream author and Debian maintainer are same
>> person. He may reject our changes.
>
> Let's CC him so that he can comment...

Thanks for the notice.

Godfrey, are you a Debian Developer? If not the bug should be an RFP
instead of ITP. But that is a minor point.

Bye,

[1] http://musclecard.com/list.html

--
*Dr. Ludovic Rousseau


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTikqPrmNPy8s6NTJGNeVte4rfr+81Q@mail.gmail.com ">http://lists.debian.org/BANLkTikqPrmNPy8s6NTJGNeVte4rfr+81Q@mail.gmail.com
 
Old 05-18-2011, 10:06 AM
Didier Raboud
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Le mercredi, 18 mai 2011 11.56:39, Ludovic Rousseau a écrit :
> Godfrey, are you a Debian Developer? If not the bug should be an RFP
> instead of ITP. But that is a minor point.

Wrong. Anyone can submit an ITP if he Intends To Package something. Getting
it uploaded by a DD is then still mandatory to get the package to the
archive, but said DD will not be the maintainer of the package.

--
OdyX
 
Old 05-19-2011, 02:02 AM
"Godfrey Chung"
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Yes, we track the changes on every libccid release and update back to
acsccid release if the changes are correct. Starting from libccid 1.3.11, we
found that libccid blacklisted our best selling reader "ACR122U" of some
firmware versions (< 2.06). Therefore, it made our customer getting into
trouble and created a storm of customer complaints. We introduced them to
use our officially supported driver.


Starting from libccid 1.3.12, we found that it did not maintain backward
compatibility. The users are required to upgrade pcsc-lite to 1.6.x and
libusb to 1.0.x. We have a lot of customer using old Linux distributions and
these required components will not be ported. We must maintain our quality
standard and customer satisfaction. However, acsccid can be used with
pcsc-lite 1.3.3 - 1.7.x and kept to use libusb 0.1.x. We also consider to
use libusb 1.0.x on future release but the driver will be modified to use
either libusb 0.1.x or libusb 1.0.x to maintain backward compatibility. Next
release of our driver also include ACS non-CCID readers support.


Godfrey

-----Original Message-----
From: Hendrik Sattler

Sent: Wednesday, May 18, 2011 4:48 PM
To: Godfrey Chung
Cc: 627038@bugs.debian.org ; debian-devel@lists.debian.org ;
rousseau@debian.org
Subject: Re: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID
smart card readers


Zitat von Godfrey Chung <godfrey.chung@acs.com.hk>:

Before we started the driver project in 2009, we had requested to join as
a developer for libccid in alioth.debian.org but the author rejected us
with no reason. As the same time, our customer pushed us to release Linux
driver. Therefore, we decided to release our Linux driver based on
libccid and had a plan to release our driver to any Linux Distributions.


But libccid evolves and forks of such projects do usually not follow.
This leaves both in a rather sad situation. Did you track the changes
of 1.3.12 and 1.3.13? Any intention to rebase the work on 1.4.x so
libusb-1.0 gets used instead of libusb-0.1?

For the Windows platform, we also release our own driver. It is because
the generic driver does not work with multi-slot smart card readers and
we can control our driver source code to fix bugs from the readers.


The Windows driver is also not very standard-compliant and does nasty
things. It took me 30min on XP and Vista to get a bluescreen from it :-/
Note that there is also libusb-win32, making it potentially possible
to use the same source there (ignoring the Microsoft driver for it)
once it is compatible with (or integrated into) libusb-1.0.

Please note that libccid upstream author and Debian maintainer are same
person. He may reject our changes.


Let's CC him so that he can comment...

HS



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: E6EBDFA9262B4D578EE6E6AE3EAC0E9F@GODFREYPC">http://lists.debian.org/E6EBDFA9262B4D578EE6E6AE3EAC0E9F@GODFREYPC
 
Old 05-19-2011, 02:13 AM
"Godfrey Chung"
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Thank you for your information. I think you should provide some instructions
on alioth.debian.org and not reject us with no reason.


No, I did not subscribe MUSCLE mailing list.

No, I am not a Debian Developer. I am looking for sponsor to upload our
package and I follow the steps from Developer Reference. Therefore, I chose
ITP.


Godfrey

-----Original Message-----
From: Ludovic Rousseau

Sent: Wednesday, May 18, 2011 5:56 PM
To: Hendrik Sattler ; Godfrey Chung
Cc: 627038@bugs.debian.org ; debian-devel@lists.debian.org
Subject: Re: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID
smart card readers


Hello,

2011/5/18 Hendrik Sattler <post@hendrik-sattler.de>:

Zitat von Godfrey Chung <godfrey.chung@acs.com.hk>:


Before we started the driver project in 2009, we had requested to join as
a developer for libccid in alioth.debian.org but the author rejected us
with
no reason. As the same time, our customer pushed us to release Linux
driver.
Therefore, we decided to release our Linux driver based on libccid and
had a

plan to release our driver to any Linux Distributions.


Godfrey, I do not remember rejecting your request. The normal steps
are first to send good patches to the project before requesting to
join. You do not need to be on alioth.debian.org to participate to the
development of libccid.

Godfrey, do you participate on the MUSCLE (Movement for Using Smart
Card in a Linux Environment) mailing list [1]?

I could not find any message from "Godfrey Chung" in my email archives.


But libccid evolves and forks of such projects do usually not follow. This
leaves both in a rather sad situation. Did you track the changes of 1.3.12
and 1.3.13? Any intention to rebase the work on 1.4.x so libusb-1.0 gets
used instead of libusb-0.1?


Good question.


Please note that libccid upstream author and Debian maintainer are same
person. He may reject our changes.


Let's CC him so that he can comment...


Thanks for the notice.

Godfrey, are you a Debian Developer? If not the bug should be an RFP
instead of ITP. But that is a minor point.

Bye,

[1] http://musclecard.com/list.html

--
Dr. Ludovic Rousseau



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 8DAE5E21224C4CC88275860B1DC3A476@GODFREYPC">http://lists.debian.org/8DAE5E21224C4CC88275860B1DC3A476@GODFREYPC
 
Old 05-19-2011, 02:16 AM
"Godfrey Chung"
 
Default Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Thank you for your clarification.

-----Original Message-----
From: Didier Raboud

Sent: Wednesday, May 18, 2011 6:06 PM
To: Ludovic Rousseau
Cc: Hendrik Sattler ; Godfrey Chung ; 627038@bugs.debian.org ;
debian-devel@lists.debian.org
Subject: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart
card readers


Le mercredi, 18 mai 2011 11.56:39, Ludovic Rousseau a écrit :

Godfrey, are you a Debian Developer? If not the bug should be an RFP
instead of ITP. But that is a minor point.


Wrong. Anyone can submit an ITP if he Intends To Package something. Getting
it uploaded by a DD is then still mandatory to get the package to the
archive, but said DD will not be the maintainer of the package.

--
OdyX


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 0624333F990C45A98ADDF80D3490ECE3@GODFREYPC">http://lists.debian.org/0624333F990C45A98ADDF80D3490ECE3@GODFREYPC
 

Thread Tools




All times are GMT. The time now is 07:11 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org