> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/passwordless-for-linux-ssh/ssh-login-for-linux-release-notes.md).

# SSH Login for Linux Release Notes

***

### 1.10.03

*January 2026*

#### New Features

**Edge component log forwarding to New Relic.** 1Kosmos now supports automatic log forwarding from edge components on Linux through the `1k-system-logger` service. The service automatically detects installed components and securely forwards their logs to the New Relic platform alongside the Credential Provider component, with no user-visible activity.

* Supported Linux platforms include RHEL 7–9 / CentOS and Ubuntu Server (20, 22, 24) / Desktop.
* The service supports standard operations: start, stop, restart, and status checks.

### 1.10.02

*November 28, 2025*

#### New Features

**Username displayed in UWL2 session.** Previously, when a user logged in via SSH using Linux PAM with QR-code authentication, the mobile app could display a persona different from the Linux username being authenticated — because the SSH flow did not share the requested username with the app. This could cause confusion: for example, a login attempt as `user1` might display `user2` in the app (if `user2` was the active persona), giving the false impression that authentication had been granted to the wrong user.

With this release, the UWL2 session now includes the actual username being authenticated and explicitly tags the session as an authentication request. As a result, the mobile app displays the correct persona — matching the Linux account (for example, `user1`) — ensuring a consistent and transparent login experience for users who have multiple personas enrolled.

### 1.10.00

*July 31, 2025*

#### New Features

**QR login support for Linux PAM.** Added QR login support for Linux PAM, allowing users to authenticate by scanning a QR code with the mobile app and approving the request. This method complements existing authentication flows (Push, BlockID Password), providing a more intuitive and secure login experience. For more information, see [Login with QR.](/authentication/windows-workstation-mfa/authentication-methods/qr-code.md)

### 1.09.11

*May 31, 2025*

#### New Features

* Implemented security enforcements to prevent replay attacks, strengthening authentication integrity.

### 1.09.10

*March 25, 2025*

#### Bug Fixes

* Minor bug fixes.

### 1.09.09

*February 2, 2025*

#### New Features

* Added device information logging to login events to enhance auditing and user activity tracking.

#### Enhancements

* Improved compile-time and runtime security measures to strengthen overall platform resilience.
* Updated session response handling to treat non-mandatory fields as optional, ensuring better compatibility and flexibility.

### 1.09.08

*November 29, 2024*

#### New Features

* Added **Number Challenge** as an additional security layer for Push login.
* Introduced an **Events Emitter** to capture `SUCCESS` and `FAILED` login events.
* Implemented log rotation to support more effective and manageable logging.

#### Enhancements

* Enhanced the Push consent screen on mobile to display additional information about the login request.
* Enforced a limit of 3 reattempts for incorrect user inputs to improve security.

### 1.09.06

*September 30, 2024*

#### New Features

* Added compatibility with Ubuntu Workstation and Server.
* Introduced a customizable API request timeout, giving administrators more control over connection behavior.

#### Enhancements

* Updated default authentication for Push to **Fingerprint OR PIN**.

#### Bug Fixes

* Resolved an issue with PAM to ensure correct usage of CaaS configurations.

### 1.09.05

*September 4, 2024*

#### New Features

* Introduced SSH login support using **Adaptive Authentication Journey v2** for enhanced security and flexibility.

#### Enhancements

* Each BlockID PAM installation now includes a unique **Application Instance ID** for improved tracking and integration.
* Username case-insensitivity is now supported, allowing users to log in regardless of letter casing.

### 1.09.04

*July 5, 2024*

#### Enhancements

* Login is now supported for user aliases.

### 1.09.03

*June 17, 2024*

#### New Features

* Introduced **Adaptive Authentication Journey** for Linux SSH.

#### Enhancements

* Updated the `appId` to be compatible with Linux Credential Provider.
* Removed deprecated configurations associated with CaaS.
* Enhanced the logger by adding a `WARN` logging level.

### 1.09.02

*April 5, 2024*

#### New Features

* Added OTP delivery via voice call.

#### Enhancements

* Updated messaging and the 2FA menu on the terminal.
* Linux SSH now supports authentication through the Workstation OTP from the BlockID App.
* Enhanced the SSH BlockID login interface and menu.

### 1.09.01

*February 9, 2024*

#### New Features

**OTP delivery via SMS and email.** Users can now receive one-time passwords (OTPs) through SMS and email, providing additional options for secure authentication.

{% hint style="info" %}
&#x20;This feature requires the addition of two new configurations to CaaS (Configuration-as-a-Service).&#x20;
{% endhint %}

#### Enhancements

**Removed automatic modifications performed by the installer.** The installer will no longer make generic changes to the system configuration files. The server administrator is now required to make the configuration file changes highlighted in the installation and configuration section.

### 1.08.02

*November 2, 2023*

#### New Features

**Configuration option for local user 2FA bypass.** Introduced a new configuration option that allows local users to bypass Multi-Factor Authentication (MFA). This option is essential for local accounts on the Linux server, since 2FA/MFA does not work for accounts that are not part of any central directory linked to the 1Kosmos tenant.

**Menu-driven UX for 2FA mechanism selection.** BlockID Linux PAM now offers configuration settings to enable or disable a menu-driven user experience for selecting 2FA mechanisms.

#### Enhancements

* BlockID Linux PAM can now be configured to handle only 2FA/MFA, while the primary authentication factor is handled natively by the Linux server.

### 1.08.01

*September 21, 2023*

#### Enhancements

* Added support for RHEL 6 and RHEL 7.

### 1.08.00

*August 30, 2023*

#### New Features

**BlockID PAM for Linux.** Initial release of BlockID PAM for Linux.

* Users can now use BlockID passwordless authentication and MFA to connect to their Linux host via SSH.
* Supports multiple multi-factor authentication login options: password, OTP, and Push notification.
* Supports RHEL 8. Additional versions will be supported in an upcoming release.
* Administrators have the flexibility to customize which authentication options to enable, allowing for various combinations such as password, OTP, and Push notification.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/authentication/passwordless-for-linux-ssh/ssh-login-for-linux-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
