2012/5/24 Hans Witvliet :
> Hi all,
Hello,
> >From what i learned, it seems that GSM-sims hold their info in specific
> EF's on the smartcard.
>
> Although they miss the directory structure normally found on cards, is
> there any reason why i should not be able to read thsoe EF's?
>
> I mean, whe
On Thu, 2012-05-24 at 17:48 +0300, Martin Paljak wrote:
> Hello,
>
>
> SPE is Secure PIN entry.
>
> Depending on the exact version of your reader (there are several) the
> S in SPE can be bogus:
>
>
> http://martinpaljak.net/2011/03/19/insecure-hp-usb-smart-card-keyboard/
>
>
> The reader wi
Hi all,
>From what i learned, it seems that GSM-sims hold their info in specific
EF's on the smartcard.
Although they miss the directory structure normally found on cards, is
there any reason why i should not be able to read thsoe EF's?
I mean, when inserting a SIM into a reader, i get the ATR,
On Thursday, May 24 at 03:21PM, NdK wrote:
>
> Hi all.
>
> Just received $subj and started testing.
>
> Too bad the cards aren't recognized by default:
> $ opensc-tool -a -n
> Using reader with a card: ACS ACR122U PICC Interface 00 00
> 3b:85:80:01:4d:79:45:49:44:78
> Unsupported card
>
> Is it
On 24/05/2012 18:33, Ludovic Rousseau wrote:
> ACS forked my CCID driver. I got no contract with ACS.
Argh!
> Your "ACS ACR122U PICC Interface" reader should work with my CCID driver.
Seems so. Might be useful to look at the differences?
BYtE,
Diego.
On 24/05/2012 17:56, NdK wrote:
Found some docs. Actually the reader's docs from ACS, that seems really
well-written (API_ACR122U_v2.01).
> BTW for the other ATR
> (3b:8f:80:01:80:4f:0c:a0:00:00:03:06:03:00:01:00:00:00:00:6a)
> I already found: it's a Mifare One card (just tested with others I had
2012/5/24 NdK :
> I think this one is well supported: its driver sources have 'rousseau'
> in nearly all headers :)
> Seems Ludovic got a contract with ACS (I hope for him) in 2009...
ACS forked my CCID driver. I got no contract with ACS.
Your "ACS ACR122U PICC Interface" reader should work with
On 24/05/2012 15:39, Martin Paljak wrote:
>> Too bad the cards aren't recognized by default:
>> $ opensc-tool -a -n
>> Using reader with a card: ACS ACR122U PICC Interface 00 00
>> 3b:85:80:01:4d:79:45:49:44:78
>> Unsupported card
> I'm not certain about all ACS products, but one of the 122 reader
2012/5/24 :
> Hi all,
Hello,
> Just accidentally I came across some lines in Lodovic's blog.
>
> For the latest version of licccid-1.4.6, he writes:
> "Disable SPE for HP USB CCID Smartcard Keyboard. The reader is bogus and
> unsafe."
>
> I am not sure what "SPE for HP..." means,
> but I certai
Hello,
SPE is Secure PIN entry.
Depending on the exact version of your reader (there are several) the
S in SPE can be bogus:
http://martinpaljak.net/2011/03/19/insecure-hp-usb-smart-card-keyboard/
The reader will still function as a standard reader, but the "PIN
entry through numpad" is disa
Hi all,
Just accidentally I came across some lines in Lodovic's blog.
For the latest version of licccid-1.4.6, he writes:
"Disable SPE for HP USB CCID Smartcard Keyboard. The reader is bogus and
unsafe."
I am not sure what "SPE for HP..." means,
but I certainly hope I can still use it for our
Hello,
On Thu, May 24, 2012 at 4:21 PM, NdK wrote:
> Hi all.
>
> Just received $subj and started testing.
>
> Too bad the cards aren't recognized by default:
> $ opensc-tool -a -n
> Using reader with a card: ACS ACR122U PICC Interface 00 00
> 3b:85:80:01:4d:79:45:49:44:78
> Unsupported card
I'm
Hi all.
Just received $subj and started testing.
Too bad the cards aren't recognized by default:
$ opensc-tool -a -n
Using reader with a card: ACS ACR122U PICC Interface 00 00
3b:85:80:01:4d:79:45:49:44:78
Unsupported card
Is it only matter of unknown ATR and I can safely use force myeid? Or
sho
13 matches
Mail list logo
