Choose style:

Author Topic: PIV OR CAC card reader  (Read 1392 times)

0 Members and 1 Guest are viewing this topic.

Offline ScubaSteve

  • Jr. Member
  • **
  • Posts: 33
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): PeppermintOS 8 64 bit
Re: PIV OR CAC card reader
« Reply #15 on: April 16, 2018, 11:01:19 pm »
No giving up.

I have completed these steps and I feel like everything from a hardware situation has been handled. I believe the drivers are working because the SC reader will actually light up now when plugged in or when I insert the card.This changed after installing the drivers. nothing from LSUSB has changed. Thanks for fixing all that stuff.

Sounds like the next big hurdle is downloading the certs, and I have contacted IT about this. Does that sound right. Is there a way to check if I have installed the drivers correctly? Again thanks for all the help with this guys. Super helpful.

Offline christianvl

  • Member
  • ***
  • Posts: 190
  • Karma: 33
  • The Wheel weaves as the Wheel wills
    • View Profile
  • Peppermint version(s): 9
Re: PIV OR CAC card reader
« Reply #16 on: April 17, 2018, 08:20:37 am »
You can try your card reader typing in the terminal
Code: [Select]
pcsc_scan

This is what I get when I run the command with the card inserted in the reader:

Code: [Select]
$ pcsc_scan
PC/SC device scanner
V 1.4.25 (c) 2001-2011, Ludovic Rousseau <ludovic.rousseau@free.fr>
Compiled with PC/SC lite version: 1.8.20
Using reader plug'n play mechanism
Scanning present readers...
0: Gemalto PC Twin Reader (D09B9070) 00 00

Tue Apr 17 09:07:20 2018
Reader 0: Gemalto PC Twin Reader (D09B9070) 00 00
  Card state: Card inserted,
  ATR: NN NN NN NN NN NN NN NN NN NN NN NN

ATR: NN NN NN NN NN NN NN NN NN NN NN NN
+ TS = 3B --> Direct Convention
+ T0 = 68, Y(1): 0110, K: 8 (historical bytes)
  TB(1) = 00 --> VPP is not electrically connected
  TC(1) = 00 --> Extra guard time: 0
+ Historical bytes: NN NN NN NN NN NN NN NN NN NN NN NN
  Category indicator byte: 00 (compact TLV data object)
    Tag: 7, len: 3 (card capabilities)
      Selection methods: C8
        - DF selection by full DF name
        - DF selection by partial DF name
        - Implicit DF selection
      Data coding byte: 40
        - Behaviour of write functions: write OR
        - Value 'FF' for the first byte of BER-TLV tag fields: invalid
        - Data unit in quartets: 1
      Command chaining, length fields and logical channels: 13
        - Logical channel number assignment: by the card
        - Maximum number of logical channels: 4
    Mandatory status indicator (3 last bytes)
      LCS (life card cycle): 00 (No information given)
      SW: 9000 (Normal processing.)

Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
NN NN NN NN NN NN NN NN NN NN NN NN
        MASTERCARD issued by MLP (Marschollek, Lautenschläger and Partner)
        G&D 12696-GDM-10/11 DEBIT CARD issued by BANCO DE CREDITO DEL PERU
        Visa from Caisse populaire Desjardins (Canada) (Bank)
        https://www.desjardins.com/
There are neither beginnings or endings to the turning of the Wheel of Time. But it was a beginning.

Offline ScubaSteve

  • Jr. Member
  • **
  • Posts: 33
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): PeppermintOS 8 64 bit
Re: PIV OR CAC card reader
« Reply #17 on: April 23, 2018, 11:56:59 pm »
This is what I get, which does not appear to be a change compared to before. Still think the drivers are working thought

Code: [Select]
Mon Apr 23 23:55:17 2018
Reader 0: SCM Microsystems Inc. SCR 3310 [CCID Interface] (53311724217924) 00 00
  Card state: Card inserted,
  ATR: 3B DB 96 00 80 1F 03 00 31 C0 64 B0 F3 10 00 0F 90 00 88

ATR: 3B DB 96 00 80 1F 03 00 31 C0 64 B0 F3 10 00 0F 90 00 88
+ TS = 3B --> Direct Convention
+ T0 = DB, Y(1): 1101, K: 11 (historical bytes)
  TA(1) = 96 --> Fi=512, Di=32, 16 cycles/ETU
    250000 bits/s at 4 MHz, fMax for Fi = 5 MHz => 312500 bits/s
  TC(1) = 00 --> Extra guard time: 0
  TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0
-----
  TD(2) = 1F --> Y(i+1) = 0001, Protocol T = 15 - Global interface bytes following
-----
  TA(3) = 03 --> Clock stop: not supported - Class accepted by the card: (3G) A 5V B 3V
+ Historical bytes: 00 31 C0 64 B0 F3 10 00 0F 90 00
  Category indicator byte: 00 (compact TLV data object)
    Tag: 3, len: 1 (card service data byte)
      Card service data byte: C0
        - Application selection: by full DF name
        - Application selection: by partial DF name
        - EF.DIR and EF.ATR access services: by GET RECORD(s) command
        - Card with MF
    Tag: 6, len: 4 (pre-issuing data)
      Data: B0 F3 10 00
    Mandatory status indicator (3 last bytes)
      LCS (life card cycle): 0F (unknown)
      SW: 9000 (Normal processing.)
+ TCK = 88 (correct checksum)

Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
## ## ## ## ##...