|
Home > Archive > Debian Developers > December 2004 > Bug#287317: ITP: eid -- software to support the eID, the new Belgian electronical ID c
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Bug#287317: ITP: eid -- software to support the eID, the new Belgian electronical ID c
|
|
| Wouter Verhelst 2004-12-26, 8:47 pm |
| Package: wnpp
Severity: wishlist
* Package name : eid
Version : ??? (not specified, AIUI)
Upstream Author : Zetes NV <info@be.zetes.com>
* URL : http://www.belgium.be/zip/middlewar...ce_code_nl.html
* License : LGPL (and possibly others)
Description : software to support the eID, the new Belgian electronical ID card
The Belgian eID software consists of a slightly modified OpenSC, a few
applications to query the card, and an extra library. There are also a
few PDF files containing specifications of the card.
I might end up creating anywhere between one and three source packages,
but I'm not sure yet.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.9
Locale: LANG=nl_BE.UTF-8@euro, LC_CTYPE=nl_BE.UTF-8@euro (charmap=UTF-8)
--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Eric Dorland 2004-12-27, 5:52 pm |
| * Wouter Verhelst (wouter@debian.org) wrote:
> Package: wnpp
> Severity: wishlist
>
> * Package name : eid
> Version : ??? (not specified, AIUI)
> Upstream Author : Zetes NV <info@be.zetes.com>
> * URL : http://www.belgium.be/zip/middlewar...ce_code_nl.html
> * License : LGPL (and possibly others)
> Description : software to support the eID, the new Belgian electronical ID card
>
> The Belgian eID software consists of a slightly modified OpenSC, a few
> applications to query the card, and an extra library. There are also a
> few PDF files containing specifications of the card.
>
> I might end up creating anywhere between one and three source packages,
> but I'm not sure yet.
I have good contact with the OpenSC upstream. Wouldn't it be
beneficial to roll these changes into OpenSC proper?
--
Eric Dorland <eric.dorland@mail.mcgill.ca>
ICQ: #61138586, Jabber: hooty@jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+
G e h! r- y+
------END GEEK CODE BLOCK------
| |
| Eric Dorland 2004-12-28, 2:51 am |
| * Wouter Verhelst (wouter@debian.org) wrote:
> Op ma, 27-12-2004 te 15:55 -0500, schreef Eric Dorland:
>
> Absolutely, but I'd think it'd be better if Zetes would pursue this. I
> planned to contact them, but wanted to have a good look at what they
> actually changed before I'd do that.
Very sensible. If it's not too intrusive and everyone involved agrees,
I don't mind applying patches to the package, so feel free to feed me
some patches to review. I'm CCing Andreas (the main OpenSC upstream
developer), please keep him CCed on any replies.
> I should note, though, that I want to have these packages in Sarge. If
> that means I have to provide a forked OpenSC to be able to do that, then
> that is what I'll do.
I understand, I'd probably do the same thing if it's expedient. But in
the long term it's probably not desirable. And if you do package a
forked OpenSC, please have it play nice with my own packages 
> Of course, this is all only valid for the modified OpenSC part; the
> documentation and the applications will remain separated.
Of course.
--
Eric Dorland <eric.dorland@mail.mcgill.ca>
ICQ: #61138586, Jabber: hooty@jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+
G e h! r- y+
------END GEEK CODE BLOCK------
| |
| Eric Dorland 2004-12-28, 6:07 pm |
| * Andreas Jellinghaus (aj@dungeon.inka.de) wrote:
> Hi everyone,
>
> belgium releases the source code, a very nice chrismas present.
>
> the opensc developers already had it for a few days and we could
> take a look. we will merge most of the changes soon, but we are
> considering a different approach on some issues.
>
> the biggest issue is: belpic includes gtk code so it can do a gui
> popup to ask for a pin. I'm not sure it is nice to link libopensc
> with gtk. I'd rather prefer a mechanism where the application
> registeres a callback function. maybe also make it possible to
> specify a gui plugin in the config file that will be loaded
> automaticaly and used as default callback.
Well the pinentry program from the GnuPG folks seems to be their
solution to this problem. Maybe it could be used to solve this one?
> so a full featured integration of all changes into opensc will take some
> time. if you want to package belpic now with debian: I'm fine with
> it. in half a year or so opensc can obsolete it, but till
> then it might be the fastest solution to get belpic support
> for everyone ready into debian.
>
> a few comments:
> package name should be belpic to be consistent.
> (also because "eid" is generic, and other countries
> have eid software, too).
>
> license is LGPL (with a few files under bsd).
--
Eric Dorland <eric.dorland@mail.mcgill.ca>
ICQ: #61138586, Jabber: hooty@jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+
G e h! r- y+
------END GEEK CODE BLOCK------
| |
| Marco d'Itri 2004-12-28, 6:07 pm |
| On Dec 28, Eric Dorland <eric.dorland@mail.mcgill.ca> wrote:
> Well the pinentry program from the GnuPG folks seems to be their
> solution to this problem. Maybe it could be used to solve this one?
Yes. Other options:
- using the gnome-keyring framework
- discarding most of this openssl-based stuff, which is probably ugly,
and start using GnuPG 1.9 which supports X.509 certificates and smart
cards.
--
ciao,
Marco
| |
| Eric Dorland 2004-12-28, 6:07 pm |
| * Marco d'Itri (md@Linux.IT) wrote:
> On Dec 28, Eric Dorland <eric.dorland@mail.mcgill.ca> wrote:
>
> Yes. Other options:
> - using the gnome-keyring framework
What would the advantage of using their stuff be? pinentry seems to
support qt and a curses interface as well.
> - discarding most of this openssl-based stuff, which is probably ugly,
> and start using GnuPG 1.9 which supports X.509 certificates and smart
> cards.
Err, huh? If you look at http://www.gnupg.org/aegypten2/index.html,
which is the roadmap for GnuPG 1.9, you'll notice in the graphic that
OpenSC is slated to be used to interface with smart cards. So I'm not
sure where you're getting this "drop this openssl-based
stuff". Pinentry is out of the GnuPG 1.9 project, so we would be using
their stuff.
--
Eric Dorland <eric.dorland@mail.mcgill.ca>
ICQ: #61138586, Jabber: hooty@jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+
G e h! r- y+
------END GEEK CODE BLOCK------
| |
| Hamish Moffatt 2004-12-28, 9:01 pm |
| On Tue, Dec 28, 2004 at 02:54:29PM +0100, Wouter Verhelst wrote:
> retitle 287317 belpic -- software to support the new Belgian electronical ID card
"electronical"? May I suggest "electronic".
cheers
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|