Re: [Muscle] Login failed with GDM and libpam

2005-11-28 Thread Matthias Barmeier
Hi, Nope, nothing helps same error. I have checked the behaviour on two different computer with two different cardreaders. Any suggestions ??? BTW, do you have a link where pam-muscle-conf is documented I would like to check the LDAP stuff if it works. Maybe this works better ?! Ciao

[Muscle] SCU3 released

2005-11-28 Thread Philippe C. Martin
Hi, I'm posting this release on Muscle for info, as I hope that U3 will soon support Linux and as SCU3 should compile under Linux when the time comes. I feel this concept would simplify deployment: having pcsclite and other libraries/packages in the customer's pocket with no installation

Re: [Muscle] Login failed with GDM and libpam

2005-11-28 Thread Karsten Ohme
Matthias Barmeier wrote: Hi, Nope, nothing helps same error. I have checked the behaviour on two different computer with two different cardreaders. Any suggestions ??? Export the key again (the public key). And convert it again with b2fs. The error cannot read certificate from is only

Re: [Muscle] SCU3 released

2005-11-28 Thread Ludovic Rousseau
On 28/11/05, Philippe C. Martin [EMAIL PROTECTED] wrote: Hi, Hello, I am very happy to announce the release of SCU3 V 0.1 and SCU3Python.u3p V. 0.1. SCU3 is a python wrapper for U3 compliant devices What is a U3 compliant devices? Is it the devices described at [1]? What are the links

Re: [Muscle] SCU3 released

2005-11-28 Thread Philippe C. Martin
A U3 device (www.u3.com) is a flash drive which allows for applications installation: you plug the U3 device in the USB port and your application is available. If the application does its job correctly, application data is stored on the U3 device, not on the PC. Some of the issues I have been

Re: [Muscle] SCU3 released

2005-11-28 Thread Peter Tomlinson
So the U3 drive is not a secure device in its own right? (i.e. it seems to me that it does not incorporate a crypto chip such as is used in a strong security smart card, and nor does its flash memory have the kind of security protection against penetration that smart card flash has) (I looked on

Re: [Muscle] SCU3 released

2005-11-28 Thread Philippe C. Martin
Typos, sorry : ...I need to protect data that in on the drive ... I need to protect data that is on the drive ...but that I can help promote the smart card concept ... ... but that it can help promote the smart card concept ... Philippe C. Martin wrote: Hi, I do not know what

[Muscle] Problems with BasicCard, ACR38 on Linux

2005-11-28 Thread Gary Pearman
I've written a simple program using libbasiccard and libpcsclite that gets the ApplicationID from a ZeitControl BasicCard. The problem is that the program returns the correct value when run in Windows, but returns garbage when run on Linux. I think I'm missing something simple, but not sure what.

Re: [Muscle] SCU3 released

2005-11-28 Thread Peter Williams
I dont get it. Its a classical (removable) hard drive device. Little has changed here since ATA cards, and 16 bit plug and play!! For a short time, I worked on a recent project in which a combination ST22 secure core and an IDE bridge controller were SOC'ed together to make a

Re: [Muscle] Problems with BasicCard, ACR38 on Linux

2005-11-28 Thread Gary Pearman
On Mon, 2005-11-28 at 11:53 -0600, Philippe C. Martin wrote: Hi, I do not know about libbasiccard, but pcsclite works fine for me on a ZC5.5 (T=1) - mdk 10.1 (testing this week on suse 10.0) Regards, Philippe The first time I run my program, I get a card busy error, the second time it

Re: [Muscle] Problems with BasicCard, ACR38 on Linux

2005-11-28 Thread Philippe C. Martin
Hi, This dumps _seems_ to show pcsclite is unhappy figuring out the protocol - did you try to force it (T=1 or T=0) ? You might want to try with another reader also (or update its driver ?). Regards, Philippe Gary Pearman wrote: On Mon, 2005-11-28 at 11:53 -0600, Philippe C. Martin

Re: [Muscle] SCU3 released

2005-11-28 Thread Philippe C. Martin
Peter Williams wrote: I dont get it. Its a classical (removable) hard drive device. Little has changed here since ATA cards, and 16 bit plug and play!! The main difference here is that one installs the application on the flash drive, not the PC. The application/application data is available

Re: [Muscle] New pcsc-lite 1.2.9-beta9 available

2005-11-28 Thread Douglas E. Engert
Two problems: (1) minor problem that may have been around before: The libpcsclite.pc created with pcslite-1.2.9-beta9 has: includedir=${prefix}/include/PCSC When pkgconfig is used with ccid-0.9.4 the code tries to include PCSC/pcsclite.h and PCSC/ifdhandler.h which are not found as directory

Re: [Muscle] SCU3 released

2005-11-28 Thread Peter Williams
From: Philippe C. Martin [EMAIL PROTECTED] Reply-To: MUSCLE muscle@lists.musclecard.com To: MUSCLE muscle@lists.musclecard.com Subject: Re: [Muscle] SCU3 released Date: Mon, 28 Nov 2005 12:41:38 -0600 Peter Williams wrote: I dont get it. Its a classical (removable) hard drive device.

Re: [Muscle] SCU3 released

2005-11-28 Thread Philippe C. Martin
Hi, While memory sticks, CF cards, ATA cards (me old!), smartmedia devices are just flash, with a FAT support licensed from Microsoft, the USB frm factor of the same flash devices in the US shops tend to come with applications. All the finger-print enable USB flash drives have come with

Re: [Muscle] New pcsc-lite 1.2.9-beta9 available

2005-11-28 Thread Ludovic Rousseau
On 28/11/05, Douglas E. Engert [EMAIL PROTECTED] wrote: Two problems: (1) minor problem that may have been around before: The libpcsclite.pc created with pcslite-1.2.9-beta9 has: includedir=${prefix}/include/PCSC When pkgconfig is used with ccid-0.9.4 the code tries to include