Termix-SSH / Termix-SSH/Support

[BUG]

Open
#1,216 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug host-metrics platform-desktop platform-windows ssh
Dominant language
No language data
Stars
28
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Title

Status check triggers a full SSH authentication attempt even when metricsEnabled is false

Platform

Desktop App - Windows

Server Installation Method

N/A

Version

2.7.1

CLI Installation Method

None

CLI Version

No response

Troubleshooting
  • I have examined logs and tried to find the issue
  • I have reviewed opened and closed issues
  • I have tried restarting the application
  • I have checked open issues and ensured this is not a duplicate
The Problem

Status check on an SSH host with metrics disabled is supposed to just be a TCP ping. Instead it's doing a full SSH auth attempt on every status check interval. On a RADIUS/Duo backed switch this means a live Duo push every interval, for every host, with zero tabs or sessions open.

How to Reproduce
  1. Install Termix 2.6.0 (or earlier), add SSH hosts with statusCheckEnabled: true and metricsEnabled: false, confirm status checks are just TCP pings (no auth attempts on the target).
  2. Upgrade to 2.7.1 via the MSI installer
  3. Open the app
  4. Watch the auth logs on an SSH host that has statusCheckEnabled: true and metricsEnabled: false a full SSH login attempt fires on that host, with no tabs open.
  5. To rule out a stale config: uninstall, delete the app data folder, reinstall fresh.
  6. Import hosts from a JSON export (statsConfig included, metricsEnabled: false on each host).
  7. As soon as the import finishes, the same behavior happens. SSH login attempts fire against every imported host on the next status check interval, still with no tabs open.
Additional Context

Easier to see with switches where radius auth 2fa enabled. Otherwise you'll have to look through local appdata to see session logs.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified in the report. Reproduce the issue with imported hosts where statusCheckEnabled is true and metricsEnabled is false, then inspect the status-check and authentication logs. Done means status checks use only TCP and do not trigger SSH authentication when metrics are disabled.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.