starred/1Remote

Fork 0

mirror of https://github.com/1Remote/1Remote.git synced 2026-04-25 13:36:03 +03:00

[GH-ISSUE #611] 1.0.0 BETA: Custom SSH Runners not working #1455

New issue

Closed

opened 2026-02-28 12:04:31 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 12:04:31 +03:00

Owner

Originally created by @t-ru on GitHub (Feb 17, 2024).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/611

Originally assigned to: @VShawn on GitHub.

Password and Private Key are not correctly passed to exe on SSH runners.

Configured SSH Runner

Exe path: wt.exe

Login with password: -w 1 new-tab --title "%1RM_HOSTNAME%" --suppressApplicationTitle plink -ssh %1RM_HOSTNAME% -P %1RM_PORT% -%SSH_VERSION% -C -X -no-antispoof -l %1RM_USERNAME% -pw %1RM_PASSWORD%

Login with PK: -w 1 new-tab --title "%1RM_HOSTNAME%" --suppressApplicationTitle plink -ssh %1RM_HOSTNAME% -P %1RM_PORT% -%SSH_VERSION% -C -X -no-antispoof -l %1RM_USERNAME% -i %1RM_PRIVATE_KEY_PATH%

To Reproduce

Create 2 connections. One with use of password and one with use of private key.
Test both connections... all is working fine.
Close 1Remote
Exit the 1Remote tray icon
Open 1 Remote
Test both connections... ERROR... Password and PK will not be passed correctly
Edit both connection. Do not make any changes. Exit edit mode with cancel.
Test both connections... all is working fine

Multi account has the same bug

Affected versions
All versions since switch from PRemote to 1Remote

Originally created by @t-ru on GitHub (Feb 17, 2024). Original GitHub issue: https://github.com/1Remote/1Remote/issues/611 Originally assigned to: @VShawn on GitHub. Password and Private Key are not correctly passed to exe on SSH runners. **Configured SSH Runner** Exe path: wt.exe Login with password: -w 1 new-tab --title "%1RM_HOSTNAME%" --suppressApplicationTitle plink -ssh %1RM_HOSTNAME% -P %1RM_PORT% -%SSH_VERSION% -C -X -no-antispoof -l %1RM_USERNAME% -pw %1RM_PASSWORD% Login with PK: -w 1 new-tab --title "%1RM_HOSTNAME%" --suppressApplicationTitle plink -ssh %1RM_HOSTNAME% -P %1RM_PORT% -%SSH_VERSION% -C -X -no-antispoof -l %1RM_USERNAME% -i %1RM_PRIVATE_KEY_PATH% **To Reproduce** 1. Create 2 connections. One with use of password and one with use of private key. 2. Test both connections... all is working fine. 3. Close 1Remote 4. Exit the 1Remote tray icon 5. Open 1 Remote 6. Test both connections... ERROR... Password and PK will not be passed correctly 7. Edit both connection. Do not make any changes. Exit edit mode with cancel. 8. Test both connections... all is working fine Multi account has the same bug **Affected versions** All versions since switch from PRemote to 1Remote

kerem

2026-02-28 12:04:31 +03:00

closed this issue
added the
bug

area-ct-ssh

stale
labels

kerem commented

2026-02-28 12:04:33 +03:00

Author

Owner

@VShawn commented on GitHub (Jun 8, 2024):

with password

with private key

https://github.com/1Remote/1Remote/assets/10143738/80b99e9e-0459-4efb-a5ee-86489f0a5faf

in all

Hi, @t-ru sorry for delay.

I have tested and things are going smoothly. I have only recorded the connection based on private key , but password do work too.

I'mn not sure what errors have occurred on you, but I need to point out:

Previous versions do not support passwords with special characters, which was fixed in #673

Special characters (like @ in username, see example below) have to be encoded using %XX syntax, where XX is hexadecimal UTF-8 code.[5](https://winscp.net/eng/docs/session_url#fn5)

I have only tested private keys in ppk format. I am not sure if other formats of private keys are supported.

@VShawn commented on GitHub (Jun 8, 2024): ## with password ![image](https://github.com/1Remote/1Remote/assets/10143738/875a14f7-6bc0-4c1d-8260-bdbbd9493b96) ## with private key https://github.com/1Remote/1Remote/assets/10143738/80b99e9e-0459-4efb-a5ee-86489f0a5faf ## in all Hi, @t-ru sorry for delay. I have tested and things are going smoothly. I have only recorded the connection based on private key , but password do work too. I'mn not sure what errors have occurred on you, but I need to point out: - Previous versions do not support passwords with special characters, which was fixed in #673 ``` Special characters (like @ in username, see example below) have to be encoded using %XX syntax, where XX is hexadecimal UTF-8 code.[5](https://winscp.net/eng/docs/session_url#fn5) ``` - I have only tested private keys in ppk format. I am not sure if other formats of private keys are supported.

kerem commented

2026-02-28 12:04:33 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 19, 2024):

This issue is stale because it has been open for 30 days with no activity.

@github-actions[bot] commented on GitHub (Dec 19, 2024): This issue is stale because it has been open for 30 days with no activity.

kerem commented

2026-02-28 12:04:33 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 3, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jan 3, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/1Remote#1455

No description provided.

Rows
Columns