Page Comparison

Summary

Passwords alone are no longer sufficient. To address this RIT has moved to Duo's MFA service for the majority of services. Admins and developers, however, have access to large amounts of information and have privileges on servers that can cause significant damage if their credentials are compromised. Because of those risks, stronger and more efficient MFA is required for certain accounts. To achieve this, ITS has historically used OATH (One Time Passwords) for SSH and sudo access on Linux servers and recently started requiring either certificates + PIN or Duo for Windows logons.

OATH is deprecated and all OATH users are being moved to certificate-based authentication. ITS is issuing YubiKeys that will be used to securely generate and store these certificates.

Requirements

• YubiKey 4 or newer (needs to mention PIV or smartcard)
  • Security keys will not work. These are generally FIDO only keys.
    • Yubico Security Keys (blue)
    • GitHub-branded security keys
• Latest version of OS
• YubiKey Manager
  • Download direct from Yubico: YubiKey-Manager
  • Windows

    • 
      

      Expand
      title SCCM Software Center (Preferred Method)

      
      

    • YubiKey-Manager - Windows x64 latest
  • Mac
    • YubiKey-Manager - MacOS pkg latest
  • Linux
    • AppImage - YubiKey-Manager - Linux AppImage latest
    • Src - YubiKey-Manager - Linux src latest

Requesting a YubiKey

• Fill out the following Google form
  round 2 Yubikey singnup sheet - Google Sheets
  • Pick up at INS-1130

Considerations

• These docs are not the only way to accomplish the goal nor are YubiKeys the only way to accomplish password-less authentication however the further you deviate from these docs the less knowledge ITS has to assist you.
• The OS requires a lock on the YubiKey. If using multiple computers, even if a computer is virtual, multiple devices will be needed – one device per instance of the OS.
  • A YubiKey can be passed through RDP session(s) (Windows only)
• Each device will have a different certificate. A certificate can, however, be used for access to both Linux and Windows servers.
• Expert mode: While a YubiKey (i.e. a Yubico device) is not required, the docs and process are assuming a YubiKey is being used. Any device that can securely generate and store keys in a way that can be cryptographically verified will work.

Process Overview

I. Initialize/Configure YubiKey
II. Certificate Enrollment
III. Submit certificate for verification
IV. Configure clients to use certificates
V. Next steps

I. Initialize/Configure YubiKey

II. Certificate Enrollment

III. Submit certificate for verification

IV. Configure clients to use certificates

Windows: IV. YubiKey Windows SSH Client Configuration

Mac: IV. YubiKey Mac SSH Client Configuration

Linux: IV. YubiKey Linux SSH Client Configuration

V. Next steps

YubiKey Duo Setup - start.rit.edu/Duo

• Security Keys and Duo

Other uses for certificates

• Sign and encrypt emails
  • Main benefit comes from a chained certificate
    • Trust follows the chain 
      • via Windows CA-issued certificate - valid for all RIT Windows domain-bound machines
      • via publicly signed certificate - valid for everyone
  • Using Your YubiKey for Email Signing/Encrypting with Outlook on Windows
  • Using Your YubiKey for Email Signing/Encrypting with Outlook on Mac
• Signing Gitlab commits and tags
  
  • Sign commits and tags with X.509 certificates
• Code signing
  • Request a code signing certificate
  • Code Signing with the YubiKey on Windows

Other uses of YubiKeys

• Register the YubiKey as a security key for various services.
  • 2FA Directory
• Configure the YubiKey as a safe place to store OTP (one time passcodes) for non-RIT services instead of using a phone app
  • Using Your YubiKey with Authenticator Codes
• Register the YubiKey to provide password-less authentication in Azure/M365 services

Troubleshooting

• YubiKey Windows SmartCard Troubleshooting