warpdotdev / warpdotdev/warp

After using ssh to server and enter the password, this error:flag provided but not defined: -c

Open
#5,037 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:ssh bug needs-info ready-to-implement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Dupe Check
Describe the bug

I used ssh to log in to the server, but I found that there was a problem with this. And I asked my colleague to use warp as well, so they can log in. And my own terminal is also possible. So I turned off the SSH wrapper and this one was fine.I SSH this will enter a GUI interface

To reproduce

ssh pilot@192.x.x.x
pilot@192.x.x.x's password:
flag provided but not defined: -c
Usage of console:
-m string
mode: full, vpn, radius, server, db, storage
-p check pilot pwd: true/false (default true)
-r root: true/false
-s sudo: true/false (default true)
Connection to 192.x.x.x closed.

When I turn off the SSH wrapper, I can enter the gui page normally.

Expected behavior

No response

Screenshots

No response

Operating system

MacOS

Operating system and version

Debian 11.2

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Contributor guide

Open the contributing guide

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

Start by reproducing ssh pilot@192.x.x.x with the SSH wrapper enabled, then compare it with the wrapper-disabled behavior. Inspect the SSH wrapper's console argument handling around the reported -c error; done means the connection reaches the GUI without the undefined-flag failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, macos
Domain
cli, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.