On Friday 17 March 2006 15:20, Justin Karneges wrote:
> On Friday 17 March 2006 08:19, Chaskiel M Grundman wrote:
> > Since it doesn't seem to break this device, I would put back the other
> > card_reset code you pulled out, since it might be needed with other
> > hardware (and it might deal with t
On Friday 17 March 2006 15:20, Justin Karneges wrote:
> On Friday 17 March 2006 08:19, Chaskiel M Grundman wrote:
> > it is openct's job to do the T=1 framing. The problem is that the
> > device's ATR reports that it supports both T=0 and T=1.
> > ifd_protocol_select picks T=0 (because it is report
On Friday 17 March 2006 08:19, Chaskiel M Grundman wrote:
> it is openct's job to do the T=1 framing. The problem is that the device's
> ATR reports that it supports both T=0 and T=1. ifd_protocol_select picks
> T=0 (because it is reported earlier in the ATR) and tries to use it.
> Unfortunately, e
On 17.03.2006, at 16:00, [EMAIL PROTECTED] wrote:
Log Message:
---
fix build-tokend to unmount virtual disk at the end of compilation
Actually I don't see the real reason behind the automatic mounting/
unmounting. Whoever works with bilding tokend usually has to first
some time manual
On Fri, Mar 17, 2006 at 11:19:18AM -0500, Chaskiel M Grundman wrote:
> >Another question: Does it matter that all the windows USB writes
> >beginn with 42? In the openct driver, the init writes begin with
> >41, and the "normal" writes begin with 42. I tried changing the
> >opensc driver to use
However, eutron_send gets this:
00 a4 00 0c 02
This is not "t=1" format. Is opensc forgetting to frame the content
before
passing to openct?
it is openct's job to do the T=1 framing. The problem is that the device's
ATR reports that it supports both T=0 and T=1. ifd_protocol_select pic
On Friday 17 March 2006 02:36, Justin Karneges wrote:
> I've not yet put this in the code because surely this is much more than
> just the initialization. The openct eutron init is 2 exchanges, and this
> log shows 10 already. I hope you can make sense of this data and tell me
> where the boundar
Hi,
On 16.03.2006, at 21:24, Andreas Jellinghaus wrote:
0.) things to do before a first beta release:
does anyone have a major issue we should wait for?
please let us know as soon as possible.
It was discussed some time ago, but I'd like to have a common
agreement on the lock_login default v
On Friday 17 March 2006 00:40, you wrote:
> > Could you briefly explain what each phase of this function is? There
> > seems to be a lot of calls to ifd_usb_control() in chunks or in loops.
>
> card_reset does exactly the same commands I saw in a lot. they
> worked. no changes at all. then there i
Am Freitag, 17. März 2006 00:21 schrieb Eric Dorland:
> This doesn't sound all that robust. Is the issue some of the headers
> aren't available on some architectures? Or the structures are
> different? Whose suggested best practice is this?
usb device filesystem is available on all linux architect
10 matches
Mail list logo
