ATR statistics: TC2 - Specific to T=0

Article from the series "ATR statistics"

TC2 - Specific to T=0

If present in the Answer-to-Reset, the interface byte TC2 encodes the waiting time integer WI over the eight bits, except the value '00' reserved for future use. If TC2 is absent, then the default value is WI = 10.

TC2 # %

1889 91.17 %
0x0A 47 2.27 %
0xFF 20 0.97 %
0x10 19 0.92 %
0x14 18 0.87 %
0x0F 14 0.68 %
0x96 11 0.53 %
0x20 10 0.48 %
0x80 9 0.43 %
0x60 5 0.24 %
0x18 4 0.19 %
0x1E 4 0.19 %
0x2A 3 0.14 %
0x78 3 0.14 %
0x00 2 0.10 %
0x23 2 0.10 %
0x32 2 0.10 %
0x3E 2 0.10 %
0xF0 2 0.10 %
0x09 1 0.05 %
0x1C 1 0.05 %
0x28 1 0.05 %
0x64 1 0.05 %
0xFA 1 0.05 %
0xFE 1 0.05 %



TC2 is only for T=0 cards.
It is surprising that 47 cards declare TC2=0x0A knowing that this is the default value.
It is also surprising that 2 cards (3B 95 15 40 00 68 01 02 00 00 and 3B A7 00 40 00 80 65 A2 08 00 00 00) are using the reserved value 0.

PC/SC sample in Smart Card Connector on Chromebook

To continue the list of PC/SC wrappers initiated in 2010 with "PC/SC sample in different languages" I now present a sample in Smart Card Connector on Chromebook (or Chrome browser).

Smart Card Connector

Smart Card Connector is a Chrome extension developed by Google and available at https://chrome.google.com/webstore/detail/smart-card-connector/khpfeaanjngmcnplbdlpegiifgpfgdco.

It allows to use the PC/SC API from a JavaScript application in a Chromebook. The project is a port of pcsc-lite, libccid and libusb to ChromeOS and is available at chromeos_smart_card_connector under the Apache v2 license.

I do not have a Chromebook myself but it is possible to use the Chrome browser instead (with some limitations).

Installation

Go to https://chrome.google.com/webstore/detail/smart-card-connector/khpfeaanjngmcnplbdlpegiifgpfgdco and select "Add to Chrome".

You should see the "Smart Card Connector" application in your chrome://apps/.

If you click on the application icon you should see something like:

Since the "Smart Card Connector" application completely replaces pcsc-lite and the CCID driver the normal pcsc-lite provided by the system must be stopped. See "Troubleshooting Apps under desktop OSes" to know how to stop pcscd.

Sample application

I created a simple test application for ChromeOS. The application is available from google-smart-card-client-library-hello-world.

You need to fetch a client library google-smart-card-client-library.js from Google and also jQuery. Just follow the Building instructions.

My sample application is greatly inspired from the Hello World Chrome application and Example JavaScript Smart Card Client app. My contribution is (mainly) the last 4 JavaScript functions.

Sample source code

I only provide the source code for the file pcsc_appli.js.


/** @license
 * Copyright 2017 Google Inc. All Rights Reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

/**
 * @fileoverview Entry point of the Smart Card Client App background script (see
 * <https://developer.chrome.com/apps/event_pages>).
 */

/**
 * Client title for the connection to the server App.
 *
 * Currently this is only used for the debug logs produced by the server App.
 * @const
 */
var CLIENT_TITLE = 'example_js_client_app';

/**
 * Context for talking to the Smart Card Connector app for making PC/SC API
 * requests.
 * @type {GoogleSmartCard.PcscLiteClient.Context}
 */
var apiContext = null;

/**
 * Object that allows to make PC/SC API requests to the Smart Card Connector
 * app.
 * @type {GoogleSmartCard.PcscLiteClient.API}
 */
var api = null;

var API = GoogleSmartCard.PcscLiteClient.API;


/**
 * PC/SC-Lite SCard context.
 * @type {int}
 */
var sCardContext = null;

function initialize() {
  myLog('Establishing connection to the Connector app...');
  console.log('Establishing connection to the Connector app...');
  apiContext = new GoogleSmartCard.PcscLiteClient.Context(CLIENT_TITLE);
  apiContext.addOnInitializedCallback(onInitializationSucceeded);
  apiContext.addOnDisposeCallback(contextDisposedListener);
  apiContext.initialize();
}

function onInitializationSucceeded(constructedApi) {
  myLog('Successfully connected to the Connector app');
  console.log('Successfully connected to the Connector app');
  api = constructedApi;
  establishContext();
}

function establishContext() {
  myLog('Establishing PC/SC-Lite context...');
  console.log('Establishing PC/SC-Lite context...');
  api.SCardEstablishContext(
      GoogleSmartCard.PcscLiteClient.API.SCARD_SCOPE_SYSTEM, null, null).then(
      function(result) {
        result.get(onContextEstablished, onPcscLiteError);
      }, onRequestFailed);
}

/** @param {int} establishedSCardContext PC/SC-Lite SCard context. */
function onContextEstablished(establishedSCardContext) {
  myLog('Established PC/SC-Lite context ' + establishedSCardContext);
  console.log('Established PC/SC-Lite context ' + establishedSCardContext);
  sCardContext = establishedSCardContext;
  listReaders();
}

function listReaders() {
  myLog('Obtaining list of PC/SC-lite readers...');
  console.log('Obtaining list of PC/SC-lite readers...');
  api.SCardListReaders(sCardContext, null).then(function(result) {
    result.get(onReadersListed, onPcscLiteError);
  }, onRequestFailed);
}

/** @param {!Array.<string>} readers List of reader names. */
function onReadersListed(readers) {
  myLog('List of PC/SC-Lite readers: ' + readers);
  console.log('List of PC/SC-Lite readers: ' + readers);

    // Use the 1st reader
    reader = readers[0];
    myLog('Using reader: ' + reader);

    myCode(reader);
}

function contextDisposedListener() {
  myLog('Connection to the server app was shut down');
  console.warn('Connection to the server app was shut down');
  sCardContext = null;
  api = null;
  apiContext = null;
}

/** @param {int} errorCode PC/SC-Lite error code. */
function onPcscLiteError(errorCode) {
  myLog('PC/SC-Lite request failed with error code ' + errorCode);
  console.warn('PC/SC-Lite request failed with error code ' + errorCode);
}

/** @param {*} error The exception that happened during the request. */
function onRequestFailed(error) {
  myLog('Failed to perform request to the Smart Card Connector app: ' +
               error);
  console.warn('Failed to perform request to the Smart Card Connector app: ' +
               error);
}


function myLog(text)
{
    $("#logs").append($("<li>").text(text));
}

function myCode(readerName)
{
    myLog('Connect to the reader: ' + readerName);
    api.SCardConnect(sCardContext,
        readerName,
        API.SCARD_SHARE_SHARED,
        API.SCARD_PROTOCOL_ANY).then(function(result) {
            result.get(onConnected, onPcscLiteError);
    }, onRequestFailed);
}

function onConnected(cardHandle, protocol)
{
    APDU_SELECT = [0x00, 0xA4, 0x04, 0x00, 0x0A, 0xA0, 0x00, 0x00, 0x00,
        0x62, 0x03, 0x01, 0x0C, 0x06, 0x01];

    myLog('Sending ' + dump(APDU_SELECT));
    api.SCardTransmit(
      cardHandle,
      protocol == API.SCARD_PROTOCOL_T0 ?
          API.SCARD_PCI_T0 : API.SCARD_PCI_T1,
      APDU_SELECT).then(function(result) {
        result.get(function (ioRecvPci, response) {
            myLog('response: ' + dump(response));

            // get the 2 last bytes
            sw = response.slice(-2);
            if (sw[0] == 0x90 && sw[1] == 0x00)
            {
                APDU_COMMAND = [0x00, 0x00, 0x00, 0x00];
                myLog('Sending ' + dump(APDU_COMMAND));
                api.SCardTransmit(
                    cardHandle,
                    protocol == API.SCARD_PROTOCOL_T0 ?
                    API.SCARD_PCI_T0 : API.SCARD_PCI_T1,
                    APDU_COMMAND).then(function(result) {
                        result.get(function(ioRecvPci, response) {
                            myLog('response: ' + dump(response));

                            // get the 2 last bytes
                            sw = response.slice(-2);
                            if (sw[0] == 0x90 && sw[1] == 0x00)
                            {
                                // convert to an ASCII string
                                result = "";
                                for (var i = 0; i < response.length; i++)
                                {
                                    result += String.fromCharCode(response[i]);
                                }
                                myLog('response: ' + result);
                            }
                        }, onPcscLiteError);
                    }, onRequestFailed);
            }
            }, onPcscLiteError);
      }, onRequestFailed);
}


function dump(bytes)
{
    return (bytes.map(function (x) {
        return ('00' + x.toString(16).toUpperCase()).substr(-2)
    })).join(" ");
}

window.onload = initialize;

Remarks

This API is very verbose and low level. You can compare it to the node-pcsclite project API, also in JavaScript, I used in a previous article "PCSC sample in JavaScript (Node.js)".

The API uses a lot of call back functions. But that is not surprising for a JavaScript code.

Installation

To install the application in Chrome go to chrome://extensions/ and click on the "Load non packaged extension" button (label translated from French so the real English text may be different) and select the root directory of the sample application.

You should then see a new "Hello World PC/SC" extension in the list. Click on the "Run" link to start the extension. A new window should be created as displayed in the Output section bellow.

Output

Conclusion

This API is useful mainly/only on Chromebook computers. I guess it is the only smart card interface for this kind of computer.

If you know a PC/SC wrapper that is not yet in my list then please contact me.

macOS Sierra bug: SCardTransmit() silently truncates the card response

This is the first new PC/SC bug I find in macOS Sierra.
I imagine this bug is also present in El Capitan and Yosemite but I have not checked.

SCardTransmit() returns SCARD_S_SUCCESS when it should return SCARD_E_INSUFFICIENT_BUFFER

SCardTransmit() is used to transfer a command to the smart card and get the smart card answer.

If the reception buffer is not large enough to contain the card answer the PC/SC error SCARD_E_INSUFFICIENT_BUFFER should be returned and the expected size indicated in the pcbRecvLength parameter.

Instead, on macOS Sierra, SCARD_S_SUCCESS is returned and the card response is truncated with no indication that something went wrong.

See also

Apple bug report #30868184 "PC/SC SCardTransmit() silently truncates the smart card response".

Sample code

#include <stdio.h>
#include <string.h>

#ifdef __APPLE__
#include <PCSC/winscard.h>
#include <PCSC/wintypes.h>
#else
#include <winscard.h>
#endif

#define CHECK_RV(fct) if (SCARD_S_SUCCESS != rv) { printf(fct"() failed: %s\n", pcsc_stringify_error(rv)); ret = 0; goto error; } else { printf(fct"(): OK\n"); }

int main(void)
{
    int ret = 1;
    SCARDCONTEXT hContext;
    SCARDHANDLE hCard;
    DWORD dwActiveProtocol;
    LONG rv;
    char mszReaders[1024];
    DWORD dwReaders = sizeof(mszReaders);
    SCARD_IO_REQUEST ioRecvPci = *SCARD_PCI_T0; /* use a default value */
    unsigned char bSendBuffer[MAX_BUFFER_SIZE];
    unsigned char bRecvBuffer[MAX_BUFFER_SIZE];
    DWORD send_length, length;

    rv = SCardEstablishContext(SCARD_SCOPE_SYSTEM, NULL, NULL, &hContext);
    CHECK_RV("SCardEstablishContext");

    rv = SCardListReaders(hContext, NULL, mszReaders, &dwReaders);
    CHECK_RV("SCardListReaders");

    rv = SCardConnect(hContext, mszReaders, SCARD_SHARE_SHARED,
        SCARD_PROTOCOL_T0 | SCARD_PROTOCOL_T1, &hCard,
        &dwActiveProtocol);
    CHECK_RV("SCardConnect");

    send_length = 5;
    /* GET RANDOM for a GPK card */
    memcpy(bSendBuffer, "\x80\x84\x00\x00\x20", send_length);

    /* expected size is 0x20 + 2 = 34 bytes */
    length = 2;
    printf("Given length: %d\n", length);
    rv = SCardTransmit(hCard, SCARD_PCI_T0, bSendBuffer, send_length,
        &ioRecvPci, bRecvBuffer, &length);
    printf("Expected length: %d\n", length);
    if (SCARD_E_INSUFFICIENT_BUFFER == rv)
        printf("test PASS. Insufficient buffer is expected\n");
    else
        printf("test FAIL\n");
    CHECK_RV("SCardTransmit");
    if (SCARD_S_SUCCESS == rv)
    {
        size_t i;

        for (i=0; i<length; i++)
            printf("%02X ", bRecvBuffer[i]);
        printf("\n");
    }

    rv = SCardDisconnect(hCard, SCARD_UNPOWER_CARD);
    CHECK_RV("SCardDisconnect")

    rv = SCardReleaseContext(hContext);
    CHECK_RV("SCardReleaseContext")

error:
    return ret;
}

The program sends a GET RANDOM command to a GPK card (very old card from Gemplus). The card will answer with 32 random bytes + 2 bytes for SW.

You can use any command that sends at least one bye of data instead.

Result (on Sierra)

$ cc -framework PCSC -g -Wall main.c -o main

SCardEstablishContext(): OK
SCardListReaders(): OK
SCardConnect(): OK
Given length: 2
Expected length: 2
test FAIL
SCardTransmit(): OK
5B 8F 
SCardDisconnect(): OK
SCardReleaseContext(): OK

The value "5B 8F" is just the 2 first bytes returned by the card. The other 30 bytes and the status word (SW) are lost.

I note that if I use the values 0 or 1 for length then SCardTransmit() correctly returns SCARD_E_INSUFFICIENT_BUFFER. So the Sierra code has a check to reject a buffer of smaller than 2 bytes. The code should check the given size compared to the real card answer.

Expected result (on Debian)

$ CFLAGS=`pkg-config --cflags libpcsclite` LDFLAGS=`pkg-config --libs libpcsclite` make main
cc -pthread -I/usr/include/PCSC   -lpcsclite   main.c   -o main

SCardEstablishContext(): OK
SCardListReaders(): OK
SCardConnect(): OK
Given length: 2
Expected length: 34
test PASS. Insufficient buffer is expected
SCardTransmit() failed: Insufficient buffer.

On Debian we get the expected SCARD_E_INSUFFICIENT_BUFFER error. And we also get the correct length value to store the complete card answer. Here 34 bytes.

Known workaround

Be sure your reception buffer is large enough to contain the card answer + 2 bytes for SW.

This should be the case for all correctly written application. That explains why nobody found the bug earlier.

I found the problem while playing with a particular PC/SC Unitary Test (for pcsc-lite) on macOS: BufferOverflow_SCardTransmit.c

PySCard 1.9.5 released

I just released a new official version 1.9.5 of pyscard. PySCard is a python module adding smart cards support (PC/SC) to Python.

The PySCard project is available at:


Changes

1.9.5 (Feb 2017)
  • SCardGetStatusChange(): fix a memory leak with Python 3
  • SCardTransmit(): use SCARD_PCI_RAW for undefined protocol
  • Improve epydoc documentation

Mostly CCID driver for some Morpho devices

Some devices from Morpho are mostly CCID compliant. The devices are too far from the CCID specification so I do not plan to add support of these devices in my CCID driver.

Patches

Morpho sent me (untested) patches:
These patches for for the CCID driver version 1.4.3 (released in April 2011) and may not apply correctly on the latest CCID driver.

Devices

Morpho devices supported by the patches:
Name VendorID ProductID
MORPHO TOKEN E2 0x079B 0x008F
MORPHO TOKEN EM 0x6767 0x0104
MORPHO TOKEN EM 0x1A6F 0x0104

The token "MORPHO TOKEN EM" is also known as "Morpho ypsID Key E". This device is in my "Disabled CCID readers" list.

No support from me

I do not support these devices or the patches. Do not request help from me, contact Morpho instead.

I just make the patches public and document them so you may have a chance to use your Morpho token.

New PyKCS11 1.4.0 available

I just released a new version of PyKCS11, a Python wrapper above the PKCS#11 API.

See PyKCS11 introduction for more details about PyKCS11.

 Changes:
1.4.0 - February 2017, Ludovic Rousseau

  • fix closeAllSessions() and move it from Session to PKCS11Lib
  • add RSAOAEPMechanism to support RSA Encryption
  • add DigestSession which enables multi-part digesting
  • add Elliptic Curve keypair generating mechanism
  • fix bug in Templates using booleans CK_TRUE/CK_FALSE
    Templates are used by generateKey(), generateKeyPair(), findObjects() createObject(), unwrapKey()
  • fix dumpit.py sample for Python 3

I also noticed that I forgot to blog about the previous version: 1.3.3

1.3.3 - November 2016, Ludovic Rousseau
  • PKCS#11 definitions: sync with Cryptoki version 2.40
    • add missing CKM_* and CKP_* defines
  • Add generateKey() with default mechanism CKM_AES_KEY_GEN
  • Make sure the PyKCS11Lib is referenced as long as Session object is live
  • Fix OverflowError on Windows
  • Attribute CKA_WRAP_WITH_TRUSTED is bool
  • samples
    • dumpit: ask to enter the PIN on the pinpad if needed
    • getinfo & dumpit: add --slot= parameter
  • some minor improvements

macOS Sierra and (legacy) smart card login

It is easy to configure a user account to use a smartcard to login with macOS Sierra. Some steps are not easy to guess so I wrote this documentation for me to remember.

System configuration

Enable smart card login

$ security authorizationdb smartcard enable
YES (0)

Check configuration

$ security authorizationdb smartcard status
Current smartcard login state: enabled (system.login.console enabled, authentication rule enabled)
YES (0)

Note: you will also get the "YES (0)" result if the smartcard login is disabled. You must check the "enabled" in the output.

User configuration

You need to generate a key pair and a certificate in your smartcard. I used Cacert.org as it is a free CA.



The tokend system is read only so you can't enrol with Safari. You need to use Firefox and the smartcard PKCS#11 library to enrol your card.

After that your smartcard should be visible in the Keychain Access application:

List the possible hashes

$ sc_auth hash
4AB9854A2FFFCFC18EDA76B10B2A7EDCB028300C CAcert WoT User
9F050FD8D4781472FA56AC599BF952052E5EDA65 com.apple.systemdefault
9B6CCF907A02C78774AEEEC7D2501165FB98231A com.apple.kerberos.kdc
9F050FD8D4781472FA56AC599BF952052E5EDA65 com.apple.systemdefault
9B6CCF907A02C78774AEEEC7D2501165FB98231A com.apple.kerberos.kdc

I want to use the CAcert certificate and key.

Configure the hash

$ sudo sc_auth accept -u lroussea -h 4AB9854A2FFFCFC18EDA76B10B2A7EDCB028300C

Check it worked:
$ sc_auth list 
Hash (legacy): 4AB9854A2FFFCFC18EDA76B10B2A7EDCB028300C

Certification Authority configuration

One major problem with CAcert is that this CA is not recognised as trusted by (major) operating systems and (major) web browsers. That is why you get a red warning "This certificate was signed by an unknown authority" in the Keychain Access application.


You need to import and trust the CAcert root certificate. You can get CAcert root certificate from https://www.cacert.org/index.php?id=3. I fetched the root certificate in PEM format and saved it as root.cer.

Import CAcert root certificate

You can import the CACert root certificate using the Keychain Access application but the certificate would not get the needed trust level. You need to use the command line (I got the command from Adding new trusted root certificates to System.keychain):
$ sudo security add-trusted-cert -d -r trustAsRoot -k "/Library/Keychains/System.keychain" root.cer

Note: I had to use -r trustAsRoot instead of -r trustRoot as in the Adding new trusted root certificates to System.keychain web page. Maybe the CAcert root certificate is not considered as a real root certificate.

The CAcert root certificate should be trusted and should not display any blue mark.

Bad:
Good:

User certificate validity

Check your certificate in the smartcard is now considered as valid (with no special blue mark on it):

The certificate must be valid for any user, not just yourself. A good way to check that is to verify the certificate is also valid from another user account. The certificate must be valid before the user is logged so must not have a special (trust) configuration for a particular user.

You can get more details by evaluating the certificate from Keychain Access application.
  1. Control-click on the certificate
  2. Select "Evaluate ..." from the popup menu

  3. Click "Continue" in the next dialog box
  4. Check the certificate status

Enjoy

You can now logout to go back to the login screen. After inserting your smartcard your user should be selected and the prompt should display "PIN code:" instead of the classic "Password:".

You may want to update your default keychain password to be the same as your PIN code so can access your saved password automatically after login using the smartcard.

Conclusion

Using a smartcard to login in macOS Sierra is easy to configure. But you have to take great care about the certificate chain between the CA and your certificate.

I used and described the legacy smart card authentication system. macOS Sierra introduced a new "smart card token" mechanism to replace tokend. That is for another blog article.

macOS Sierra 10.12.2 and CCID upgrade

In macOS Sierra 10.12.2 Apple upgraded the CCID driver from version 1.4.24 (present in macOS Sierra 10.12 and 10.12.1) to version 1.4.25.

See "New version of libccid: 1.4.25" to get the list of changes.

Releases

The CCID driver 1.4.25 was released September, 30th 2016. And the macOS Sierra 10.12.2 upgrade was released December 14, 2016 so 2.5 months later.

That is a good news to see Apple integrating new versions of the CCID driver in "minor" operating system upgrades. It was already the case with macOS El Capitan (see "OS X El Capitan and CCID evolution")

Next upgrade

The current CCID version is 1.4.26 from 7 January 2017. I expect to see this version in the next minor Sierra upgrade: 10.12.3.

MUSCLE mailing list statistics for 2016

As I did in 2009, 2010, 2011, 2012, 2013, 2014 and 2015 I propose some statistics of the MUSCLE mailing list usage.

Evolution

Year Total number of messages Progression
2009 603
2010 718 +19 %
2011 999 +39 %
2012 207 -79 %
2013 198 -4 %
2014 194 -2 %
2014 194 -2 %
2015 120 -38 %
2016 125 +4 %

The number of messages is stable this year.

Comments

I am still the top poster on the MUSCLE mailing list with 33% of the messages.

The second top poster is Maksim Ivanov (emaxx@google.com) with 12 messages about fixing bugs in pcsc-lite and CCID. Thanks Maxim.

Then William To (william.to@erg.com.hk) working on a port of pcsc-lite and CCID on Solaris.


Statistics from 10.1.2016 to 22.12.2016
for pcsclite-muscle@lists.alioth.debian.org



People who have written most messages:


 Author   Msg   Percent
1 ludovic.rousseau@gmail.com 41 32.80 %
2 emaxx@google.com 12 9.60 %
3 william.to@erg.com.hk 11 8.80 %
4 oliver.graute@gmail.com 6 4.80 %
5 christophe.ferrando@sylyca.com 5 4.00 %
6 Gregory_W_Barry@rl.gov 4 3.20 %
7 amacias@solutia-it.es 4 3.20 %
8 vindrg@gmail.com 3 2.40 %
9 pcsclite-muscle-request@lists.alioth.debian.org 3 2.40 %
10 jay.aurabind@gmail.com 3 2.40 %
11 ivo.raisr@oracle.com 3 2.40 %
12 ben.mehlman@sweetsams.com 3 2.40 %
13 godfreyhkchung@gmail.com 3 2.40 %
14 00cpxxx@gmail.com 2 1.60 %
15 dbaryshkov@gmail.com 2 1.60 %
16 stephan@matrixstorm.com 2 1.60 %
17 janprunk@gmail.com 2 1.60 %
18 martin@martinpaljak.net 2 1.60 %
19 informatica@actiu.net 1 0.80 %
20 andrey.roussev@gmail.com 1 0.80 %
21 andre@florath.net 1 0.80 %
22 richardhackers@gmail.com 1 0.80 %
23 dirkx@webweaving.org 1 0.80 %
24 nmav@redhat.com 1 0.80 %
25 dwmw2@infradead.org 1 0.80 %
26 nicola.barbon@italdes.it 1 0.80 %
27 trenta.sis@gmail.com 1 0.80 %
28 pcsc@wulf.eu.org 1 0.80 %
29 my.nl.abos@gmail.com 1 0.80 %
30 maximilian.stein@secunet.com 1 0.80 %
other 2 1.60 %

Best authors, by total size of their messages (w/o quoting):


 Author   KBytes
1 ludovic.rousseau@gmail.com 1398.8
2 oliver.graute@gmail.com 665.2
3 pcsclite-muscle-request@lists.alioth.debian.org 157.5
4 william.to@erg.com.hk 116.0
5 amacias@solutia-it.es 106.3
6 martin@martinpaljak.net 85.7
7 emaxx@google.com 60.2
8 christophe.ferrando@sylyca.com 43.6
9 ivo.raisr@oracle.com 39.9
10 Gregory_W_Barry@rl.gov 24.8
11 godfreyhkchung@gmail.com 21.0
12 ben.mehlman@sweetsams.com 20.4
13 andrey.roussev@gmail.com 16.3
14 janprunk@gmail.com 15.6
15 stephan@matrixstorm.com 13.6
16 vindrg@gmail.com 12.6
17 00cpxxx@gmail.com 11.9
18 my.nl.abos@gmail.com 10.8
19 jay.aurabind@gmail.com 10.4
20 dirkx@webweaving.org 10.2
21 trenta.sis@gmail.com 10.0
22 nicola.barbon@italdes.it 8.6
23 nmav@redhat.com 7.1
24 maximilian.stein@secunet.com 7.0
25 dwmw2@infradead.org 6.5
26 dbaryshkov@gmail.com 6.2
27 andre@florath.net 3.5
28 pcsc@wulf.eu.org 2.9
29 richardhackers@gmail.com 2.6
30 informatica@actiu.net 2.5

Best authors, by average size of their message (w/o quoting):


 Author   bytes
1 oliver.graute@gmail.com 113525
2 pcsclite-muscle-request@lists.alioth.debian.org 53774
3 martin@martinpaljak.net 43854
4 ludovic.rousseau@gmail.com 34936
5 amacias@solutia-it.es 27220
6 andrey.roussev@gmail.com 16730
7 ivo.raisr@oracle.com 13633
8 my.nl.abos@gmail.com 11023
9 william.to@erg.com.hk 10794
10 dirkx@webweaving.org 10400
11 trenta.sis@gmail.com 10220
12 christophe.ferrando@sylyca.com 8939
13 nicola.barbon@italdes.it 8782
14 janprunk@gmail.com 8006
15 nmav@redhat.com 7244
16 godfreyhkchung@gmail.com 7182
17 maximilian.stein@secunet.com 7175
18 stephan@matrixstorm.com 6978
19 ben.mehlman@sweetsams.com 6956
20 dwmw2@infradead.org 6639
21 Gregory_W_Barry@rl.gov 6344
22 00cpxxx@gmail.com 6074
23 emaxx@google.com 5134
24 vindrg@gmail.com 4310
25 andre@florath.net 3614
26 jay.aurabind@gmail.com 3537
27 dbaryshkov@gmail.com 3177
28 pcsc@wulf.eu.org 2938
29 richardhackers@gmail.com 2710
30 informatica@actiu.net 2540

Table showing the most successful subjects:

   Subject   Msg   Percent 
1 [Pcsclite-muscle] ccid 1.3.13 IFD require manual smart card
9 7.20 %
2 [Pcsclite-muscle] pccs-lite 1.8.xx on Solaris 11
8 6.40 %
3 [Pcsclite-muscle] pcsc-lite-1.8.17 on solaris system
7 5.60 %
4 [Pcsclite-muscle] High CPU load with pcscd and Kerkey security
6 4.80 %
5 [Pcsclite-muscle] Looking/developing magstripe API
4 3.20 %
6 [Pcsclite-muscle] SCARD_E_NOT_TRANSACTED
4 3.20 %
7 [Pcsclite-muscle] cannot erase epass2003auto - token init
4 3.20 %
8 [Pcsclite-muscle] Tracing feature in the client side
3 2.40 %
9 [Pcsclite-muscle] Error handling when reading driver configs
3 2.40 %
10 [Pcsclite-muscle] Increasing connected smart card reader count
3 2.40 %
11 [Pcsclite-muscle] Difference with Windows (maybe a bug)
3 2.40 %
12 [Pcsclite-muscle] Smartcard reader Precise Biometrics 200 MC
3 2.40 %
13 [Pcsclite-muscle] Bug in CCID library
3 2.40 %
14 [Pcsclite-muscle] Difference from Windows' implementation with
3 2.40 %
15 [Pcsclite-muscle] SCardConnect: socketcall.sendto(msg) points to
2 1.60 %
16 [Pcsclite-muscle] pcscd jams when using '--auto-exit'
2 1.60 %
17 [Pcsclite-muscle] further issues with O2MICRO OZ776 (0b97:7772)
2 1.60 %
18 [Pcsclite-muscle] SCARD : PROTOCOL_T1 and PROTOCOL_RAW
2 1.60 %
19 [Pcsclite-muscle] SCardEndTransaction(hCard,SCARD_EJECT_CARD);
2 1.60 %
20 [Pcsclite-muscle] can't "make" ccid on Ubuntu 14.04.4 LTS
2 1.60 %
21 [Pcsclite-muscle] Possible generation of duplicate SCARDHANDLE
2 1.60 %
22 Pam-pkcs#11 needs a new maintainer(s) soon, or it will die
2 1.60 %
23 [Pcsclite-muscle] Support for multiple devices with ifdnfc,
2 1.60 %
24 [Pcsclite-muscle] Bug in reconnecting to a card.
2 1.60 %
25 [Pcsclite-muscle] ReinerSCT Cyberjack e-com:
2 1.60 %
26 [Pcsclite-muscle] ReinerSCT Cyberjack e-com: readerfactory.c:1097:RFInitializeReader()
2 1.60 %
27 [Pcsclite-muscle] High CPU load with pcscd and Kerkey security Module
2 1.60 %
28 [Pcsclite-muscle] [PATCH] fix racecondition between winscard
2 1.60 %
29 New version of libccid: 1.4.22
1 0.80 %
30 PySCard 1.9.2 released
1 0.80 %
  other 32 25.60 %

Most used email clients:

   Mailer   Msg   Percent 
1 (unknown) 98 78.40 %
2 Mozilla/5.x 12 9.60 %
3 Microsoft Outlook 16.0
9 7.20 %
4 Apple Mail (2.3124)
1 0.80 %
5 Evolution 3.20.3 (3.20.3-1.1.fc24)
1 0.80 %
6 Microsoft Outlook 15.0
1 0.80 %
7 NeoMutt/20160910 (1.7.0)
1 0.80 %
8 Centrum Email 5.3
1 0.80 %
9 KMail 1 0.80 %
  other 0 0.00 %


Table of maximal quoting:


 Author   Percent
1 plomba@net.hr 87.42 %
2 maximilian.stein@secunet.com 56.36 %
3 ben.mehlman@sweetsams.com 33.15 %
4 nicola.barbon@italdes.it 33.13 %
5 informatica@actiu.net 30.77 %
6 jay.aurabind@gmail.com 27.79 %
7 trenta.sis@gmail.com 26.20 %
8 andre@florath.net 23.89 %
9 william.to@erg.com.hk 21.53 %
10 christophe.ferrando@sylyca.com 18.63 %
11 dbaryshkov@gmail.com 18.42 %
12 florian_kaiser@genua.de 17.73 %
13 vindrg@gmail.com 16.60 %
14 emaxx@google.com 15.90 %
15 Gregory_W_Barry@rl.gov 15.07 %
16 00cpxxx@gmail.com 15.04 %
17 martin@martinpaljak.net 13.14 %
18 pcsclite-muscle-request@lists.alioth.debian.org 12.68 %
19 dirkx@webweaving.org 12.58 %
20 pcsc@wulf.eu.org 12.24 %
21 janprunk@gmail.com 10.30 %
22 stephan@matrixstorm.com 10.25 %
23 amacias@solutia-it.es 9.82 %
24 ivo.raisr@oracle.com 7.84 %
25 nmav@redhat.com 4.82 %
26 godfreyhkchung@gmail.com 3.32 %
27 ludovic.rousseau@gmail.com 3.25 %
28 richardhackers@gmail.com 2.79 %
29 my.nl.abos@gmail.com 1.48 %
30 dwmw2@infradead.org 0.99 %
average 6.90 %

Graph showing number of messages written during hours of day:


msgs 2
|
1
|
1
|
0
|
0
|
1
|
1
|
0
|
5
|
10
|
9
|
8
|
11
|
10
|
13
|
10
|
11
|
5
|
8
|
5
|
7
|
5
|
1
|
1
|
hour 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

Graph showing number of messages written during days of month:


msgs 4
|
7
|
7
|
2
|
3
|
3
|
0
|
4
|
3
|
2
|
6
|
1
|
3
|
2
|
3
|
6
|
5
|
14
|
4
|
7
|
1
|
6
|
12
|
3
|
2
|
3
|
1
|
2
|
3
|
6
|
0
|
day 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Graph showing number of messages written during days of week:


msgs 18
|
22
|
27
|
16
|
27
|
7
|
8
|

Mon Tue Wed Thu Fri Sat Sun

Maximal quoting:


Author : plomba@net.hr
Subject : [Pcsclite-muscle] SCardEstablishContext method call ret
Date : Wed, 16 Nov 2016 15:26:47 +0100
Quote ratio: 87.43% / 8852 bytes

Longest message:


Author : ludovic.rousseau@gmail.com
Subject : [Pcsclite-muscle] ReinerSCT Cyberjack e-com: readerfactory.c:1097:RFInitializeReader()
Date : Wed, 16 Nov 2016 09:12:45 +0100
Size : 813477 bytes

Most successful subject:


Subject : [Pcsclite-muscle] ccid 1.3.13 IFD require manual smart card
No. of msgs: 9
Total size : 83742 bytes

Final summary:


Total number of messages: 125
Total number of different authors: 32
Total number of different subjects: 62
Total size of messages (w/o headers): 3189502 bytes
Average size of a message: 25516 bytes



Input file last updated: Sat Jan 7 20:35:57 2017 Generated by MailListStat v1.3