Please note: This documentation describes a pilot, experimental setup. DO NOT USE ON PRODUCTION SYSTEMS

Smart Cards revisited - in 2012

The goal is to integrate CERN Smartcards with the system and different applications.

So far following has been implemented:

  • authentication with smartcard, including obtaining Kerberos ticket and AFS token, with fallback to password authentication.
  • using smartcard as security device in Firefox/Thunderbird.
  • using smartcard in krb5-auth-dialog (hmm .not very useful since kerberos ticket is refreshed with every login and screen unlock ... also buggy , may lock up your smartcard with too many PIN entry attempts, requiring its PUK)
  • using smartcard with esc (Enterprise Security Client): does not work, esc supports only coolkey library, no possibility of pluggin-in replacement one.

To be investigated:

  • rdesktop: rdesktop -r scard cerntsnew works (1.6.0-8.slc5/6.*2* with scard patch) (cernts does not .... but is it configured ?)
  • freerdp: xfreerdp --no-nla --plugin rdpdr --data scard:scard -- works (1.0.1-2c049c6 with a patch) (cernts does not .... but is it configured ?) and smart card forwarding within a Microsoft Virtual machine works too.
  • esc - 'Enterprise Smart Cards' - will not work since esc supports only a small subset of cards: in addtion it interferes with proper operation of SafeSign cards - uninstall
  • ?


  • A 2012 CERN Smart Card with your certificate (not distributed to public yet)
  • A card reader (SCR3311 - the default CERN one or universal USB reader)
  • System running fully updated Scientific Linux CERN 6 (SLC6)
  • and on CERN internal network.

Software installation

Following steps are to be performed as root on your system

  • run: yum --enablerepo=slc6-cernonly install cern-smartcard krb5-pkinit-openssl (to add basic smartcard and pkinit support to your system, including NSS db modifications)
  • run: yum --enablerepo=slc6-cernonly install firefox-aetssic thunderbird-aetssic (to add smartcard support to Firefox and Thunderbird)
  • run: yum remove esc (to remove esc - Enterprise Smart Cards manager which interferes with proper SafeSign cards operation)
  • run: yum remove openct (removes openct including pcscd driver which interferes with SafeSign smart cards one)

(note: Fedora 16: need to install krb5-pkinit-openssl package too !)


Following steps are to be performed as root on your system

  • run: /sbin/service openct stop
  • run: /sbin/chkconfig --del openct
  • Edit /etc/reader.conf.d/openct.conf, comment out all the content
  • run: /sbin/chkconfig --levels 345 pcscd on
  • run: /sbin/service pcscd restart

and as user:

  • restart Firefox (if installed firefox-aetssic)
  • restart Thunderbird (if installed thunderbird-aetssic)

Kerberos - pkinit - configuration

Edit /etc/krb5.conf to contain:
 default_realm = CERN.CH
 ticket_lifetime = 25h
 renew_lifetime = 120h
 forwardable = true
 proxiable = true
 pkinit_anchors = FILE:/etc/pki/tls/certs/CERN-bundle.pem
 pkinit_identities =
 pkinit_eku_checking = kpServerAuth
 pkinit_kdc_hostname =
 pkinit_cert_match =&&<EKU>msScLogin,<KU>digitalSignature

 CERN.CH = {
  default_domain =
  kdc =

[domain_realm] = CERN.CH

; options for Red Hat pam_krb5-2 - ARE THESE REALLY NEEDED ?
 pam = { 
   external = true 
   ticket_lifetime = 25h
(above configuration is a minimum one: make sure that your configuration does not contain any other lines defining pkinit settings , nor allow_weak_crypto or default_tkt_enctypes).

pam_pkcs11 configuration

Edit /etc/pam_pkcs11/pam_pkcs11.conf to contain:

pam_pkcs11  {
   nullok = true;
   debug = false;
   card_only = true;
   use_first_pass = false;
   try_first_pass = false;
   use_authtok = false;
   use_pkcs11_module = safesignic;
   screen_savers = "gnome-screensaver", xscreensaver, kscreensaver;
   #enable_ocsp=true; #### NO: we do not use OCSP at present - enabing it causes gnome screensaver smart card unlock 'hang' for 3 minutes then restarting auth. dialog (once every 5-10 tries)

          pkcs11_module safesignic {
                module =;
                desription = "SafeSign IC";
                slot_num = 0;
                nss_dir = /etc/pki/nssdb;
                #crl_dir = /etc/pki/tls/crls;  #### same comment as above, to be investigated further
                #crl_policy = ca,crl_auto;  #### same comment as above, to be investigated further
                crl_policy=none; #### NOT for production !

   use_mappers = cn; #pwent;

   mapper pwent {
                debug = false;
                ignorecase = false;
                module = internal;
                # module = /usr/$LIB/pam_pkcs11/;

   mapper cn {
                debug = false;
                module = internal;
                # module = /usr/$LIB/pam_pkcs11/;
                ignorecase = false;
                #mapfile = "file:///etc/pam_pkcs11/cn_map";

(WARNING: pwent pklcs11 mapper is .... er ... not too strict about mapping - matches on shortest string ... so if you have accounts allike 'user' 'userone' 'usertwo' .. etc and certificate on smart card is for 'user' and 'user', 'userone' 'usertwo' accounts do exist on system ... 'user' could get access to 'userone' and/or 'usertwo' account - but not his kerberos credentials) (again - this is minimal configuration, this config file contains other sections, which are not interfering with setup)

Configure PAM

Edit /etc/pam.d/system-auth-ac to contain:
auth        required
auth        sufficient
auth        [success=1 default=ignore] service notin login:gdm:xdm:kdm:xscreensaver:gnome-screensaver:kscreensaver quiet use_uid
auth        [success=ok authinfo_unavail=ignore ignore=ignore default=die]
auth        sufficient nullok try_first_pass
auth        sufficient no_initial_prompt no_subsequent_prompt tokens
auth        requisite uid >= 500 quiet
auth        sufficient use_first_pass
auth        required

account     required broken_shadow
account     sufficient
account     sufficient
account     sufficient uid < 500 quiet
account     [default=bad success=ok user_unknown=ignore]
account     required

password    optional
password    requisite try_first_pass retry=3 type=
password    sufficient sha512 shadow nullok try_first_pass use_authtok
password    sufficient
password    sufficient use_authtok
password    required

session     optional revoke
session     required
session     [success=1 default=ignore] service in crond quiet use_uid
session     required
session     required
session     optional

(WARNING: not very well tested so far ... check ALL scenarios ... login with/without password , with/without smartcard , as root, sudo , su ... etc ... etc)

Configuring krb5-auth-dialog

Note: slc6 uses a patched krb5-auth-dialog 0.17 (RHEL6 - 0.16) which acquires afs token automagically via afs plugin)

right click on 'keys' icon in desktop panel, choose 'Preferences', then 'Kerberos' tab. Click 'Use Smartcard' and close preferences window. open 'Preferences' again: fill in Kerberos principal yourloginid@CERN.CH , uncheck 'Use Smartcard', fill in 'Userid' to contain fill in 'X509 trust anchors' to contain FILE:/etc/pki/tls/certs/CERN-bundle.pem then close preferences window and kill the application killall -9 krb5-auth-dialog , next restart it again (Alt-F2, krb5-auth-dialog). Now you should be able to renew your kerberos ticket by left-clicking on 'keys' icon.

YES - IT IS buggy .... and be warned: if you 'left-click' multiple times on it and then choose cancel without entering PIN it still sends an empty PIN to smartcard and since the smartcard has limited count of PIN failures before it locks and requests PUK .... you may find yourself locked out...

Since this method of getting Kerberos credentials is not really necessary (as every screen unlock will refresh your ticket anyway) ... maybe it would be better to not even advertise it ...


  • Reboot your system first ... (avoid clearing some issues with some libraries already preloaded in memory and gnome components as screensaver not being able to reconfigure themselves on the fly .. sometimes)
  • Be aware that lcm may reconfigure your /etc/krb5.conf and /etc/pam.d/system-auth-ac files ... (while running lcm --update_ or when new lcm-profile is deployed).
  • verify NSS db modules list: /usr/bin/modutil -list -dbdir /etc/pki/nssdb should show SafeSign PKCS#11 module installed:
3. SafeSign IC PKCS#11 Module=
    library name:
    slots: 5 slots attached
    status: loaded
  • verify NSS db trusted certificates: /usr/bin/certutil -L -d /etc/pki/nssdb should show CERN Root CA and CERN Trusted Certification Authority certificates:
    CERN Root CA                                                 CT,C,C
    CERN Trusted Certification Authority                         CT,C,C
  • verify card functionality, start /usr/bin/tokenadm (or select 'SafeSign Identity Client Token Manager' from menu 'Applications' , submenu 'System Tools')
  • verify that the PKCS#11 module is loaded in firefox/thunderbird (select 'Edit' - 'Preferences' - 'Advanced' - 'Encryption' - 'Security Devices') - you should see 'A.E.T. SafeSign IC PKCS#11 Module' loaded.
  • verify pam_pkcs11 mapper with pkcs11_inspect:
PIN for token: 
Printing data for mapper cn:
Jarek Polok
  • verify if you can obtain a Kerberos ticket/AFS token: run kinit , you should see a prompt:
Firstname Name PIN:
enter your smartcard PIN, and check: Kerberos tickets: klist
Ticket cache: FILE:/tmp/krb5cc_14213
Default principal: jpolok@CERN.CH

Valid starting     Expires            Service principal
03/22/12 16:57:54  03/23/12 17:57:54  krbtgt/CERN.CH@CERN.CH
   renew until 03/27/12 17:57:54
03/22/12 16:57:58  03/23/12 17:57:54  afs/
   renew until 03/27/12 17:57:54
AFS tokens:_tokens_
Tokens held by the Cache Manager:

User's (AFS ID 14213) tokens for [Expires Mar 23 17:57]
   --End of list--


All problems listed below (except kinit one ?) seem to be related to crash/hang in ... *to be rechecked after we get official RHEL6 SafeSign IC packages , Q2 2012* Got these ... (3.0.77) in .. November 2012.
  • sometimes Gnome screen saver (or rather pcscd) does not observe card removal correctly (or immediately) - as a result the screen is not locked automatically. (use Ctrl-Alt-Del as workaround) (seems solved with SafeSign 3.0.77 library update in November)
  • sometimes Gnome screen saver unlock dialog hangs for 3 minutes or so , then restarts ... (remove card, switch to different virtual console , login with password and killall -9 gnome-screensaver-dialog then switch back to X .. or wait 3 minutes) (seems solved with SafeSign 3.0.77 library update in November)
  • on system boot pcscd dies: switch to console, login as root, execute service pcscd restart, logout, switch back to X, kill GDM (Ctrl-Alt-Backspace) to get 'smartcard authentication' option. (not needed if openct removed from system)
  • kinit hangs segfaults when called without username by different user, than the certificate is for and there is no krb5 cache:
# whoami && kinit
Jarek Polok PIN: 
kinit: Client name mismatch while getting initial credentials
Segmentation fault (core dumped)
(the certificate is for jpolok) Use:
# whoami && kinit jpolok
Jarek Polok PIN: 
  • git https crashes:
    xenophile kernel: git-remote-http[28390]: segfault at 27ba000 ip 00007f1325c3cb8b sp 00007fffd06ec978 error 4 in[7f1325adc000+205000]
git clone
Initialized empty Git repository in /tmp/FreeRDP/.git/
error: child process died of signal 11
fatal: ref parsing thread failed
(does not happen after complete removal of openct) -- JaroslawPolok - 23-Nov-2012
Edit | Attach | Watch | Print version | History: r20 < r19 < r18 < r17 < r16 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r20 - 2012-11-23 - JaroslawPolok
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LinuxSupport All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback