Skip to main content
  1. Blog
  2. Article

Alex Cattle
29 March 2020

Smart cards login on Ubuntu


Smart cards have proliferated and are now everywhere, from work ID badges to credit cards and passports. For example, the United States Federal Government uses smart cards to control access to federal facilities and information systems because they offer an extra layer of security and respond to strict government guidelines. If used in a company, these will provide identity confirmation, verification that data has not been changed, and confidentiality via encryption.

This whitepaper will provide information on how to configure Ubuntu 18.04 LTS to operate with a smart card to provide multi-factor authentication when logging into the system both locally and remotely. For the purposes of this whitepaper, a PIVKey smart card is used as an example since they are readily accessible and contain a few basic credentials.

Read our documentation or download the whitepaper to learn more including:

  • The software and hardware prerequisites needed for smart card configuration.
  • How to set up your smart card and configure it to support smart card logins.
  • How to configure SSH smart card login.

Download the whitepaper by filling in the form below:


Related posts

Accelerating delivery of CVE fixes with a new Kernel release strategy

When it comes to fixing security vulnerabilities, speed is crucial. Canonical is officially outlining a transition from its current 4-week regular and 2-week security kernel...

Canonical joins the Open Secure AI Alliance

Canonical is now part of the Open Secure AI Alliance, announced by NVIDIA with partners across cloud computing, cybersecurity, enterprise software, open source foundations, and...

Januscape vulnerability CVE-2026-53359 mitigations available

Introduction A local privilege escalation (LPE) vulnerability affecting the Linux kernel was publicly disclosed on July 6, 2026. The vulnerability was assigned CVE ID...

DirtyClone Linux kernel local privilege escalation vulnerability fixes available

On June 25, 2026, JFrog published their research into CVE-2026-43503, referring to the vulnerability as DirtyClone. The vulnerability had previously been responsibly disclosed...