linuxmint / linuxmint/nemo

SFTP connect don't use correctly ProxyJump in .ssh/config

Open
#3,814 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.6k
Forks
368
Avg merge
4d 4h
Merged PRs (30d)
2

Description

Distribution

Mint 22.3

Package version

6.6.3

Frequency

Always

Bug description

When typing sftp://<alias> in explorer bar, and that alias being a ~/.ssh/config entry with a ProxyJump field, the username used in always the same as the proxy one despite having a different configuration for final host's User.
You are prompted for proxy's password with proxy's User, then prompted for final host's password with proxy's User.

Steps to reproduce
  1. Setup ~/.ssh/config to have 2 hosts with 2 different User field, one proxying the other, exemple:
Host h1
  HostName foo
  User u1
Host h2
  HostName bar
  User u2
  ProxyJump h1 # or u1@foo
  1. Validate your conf in cli with sftp h2
  2. Type sftp://h2 in nemo's address bar, hit Enter
  3. A prompt dialog ask for h1's User's password on h1's Host, type it in
  4. A 2nd prompt ask for h1's User's password on h2's Host, instead of h2's User's password
Expected behavior

Expect each hop's step to use each Host's User in config.

Additional information

No response

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

Start by reproducing the issue in Nemo with the two-host ~/.ssh/config example, then compare its SFTP connection path with the validated sftp h2 command. Trace how Nemo handles the proxy and final host credentials; done means each hop uses its own configured User, with both password prompts showing the correct username.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.