starred/1Remote

Fork 0

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

[GH-ISSUE #921] If you can create a password card first and select the card to replace password input when configuring the server #3665

New issue

Closed

opened 2026-03-13 12:32:11 +03:00 by kerem · 9 comments

kerem commented

2026-03-13 12:32:11 +03:00

Owner

Originally created by @hshsdxx on GitHub (Apr 25, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/921

Originally assigned to: @VShawn on GitHub.

I want to add a function: If you can create a password card first and select a card to replace the password input when configuring the server, you can reduce duplicate password input, when the password changes, you can reset the server with the same password by just modifying the password card, which greatly reduces duplicate operations.

Originally created by @hshsdxx on GitHub (Apr 25, 2025). Original GitHub issue: https://github.com/1Remote/1Remote/issues/921 Originally assigned to: @VShawn on GitHub. I want to add a function: If you can create a password card first and select a card to replace the password input when configuring the server, you can reduce duplicate password input, when the password changes, you can reset the server with the same password by just modifying the password card, which greatly reduces duplicate operations.

kerem

2026-03-13 12:32:11 +03:00

closed this issue
added the
meta-enhancement

stale
labels

kerem commented

2026-03-13 12:32:27 +03:00

Author

Owner

@itagagaki commented on GitHub (Apr 25, 2025):

What about using an external password manager?

@itagagaki commented on GitHub (Apr 25, 2025): What about using an external password manager?

kerem commented

2026-03-13 12:32:32 +03:00

Author

Owner

@hshsdxx commented on GitHub (Apr 25, 2025):

How to use an external password manager

@hshsdxx commented on GitHub (Apr 25, 2025): How to use an external password manager

kerem commented

2026-03-13 12:32:37 +03:00

Author

Owner

@VShawn commented on GitHub (Apr 25, 2025):

How to use an external password manager

mobaxterm can do, though I think external password manager is overkill for 1Remote.

I have been hesitating whether to develop a standalone password vault feature for long, as it requires a lot of UI modifications and would make exporting sessions to JSON more complex.

@VShawn commented on GitHub (Apr 25, 2025): > How to use an external password manager ![Image](https://github.com/user-attachments/assets/bea62b29-f777-4d5f-8665-dfd68432aee9) mobaxterm can do, though I think `external password manager` is overkill for 1Remote. I have been hesitating whether to develop a standalone password vault feature for long, as it requires a lot of UI modifications and would make exporting sessions to JSON more complex.

kerem commented

2026-03-13 12:32:42 +03:00

Author

Owner

@hshsdxx commented on GitHub (Apr 27, 2025):

I think from the perspective of users, this function will be very practical. In most cases, server passwords are very difficult to remember, especially for company servers

@hshsdxx commented on GitHub (Apr 27, 2025): I think from the perspective of users, this function will be very practical. In most cases, server passwords are very difficult to remember, especially for company servers

kerem commented

2026-03-13 12:32:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 27, 2025):

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

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

kerem commented

2026-03-13 12:32:53 +03:00

Author

Owner

@VShawn commented on GitHub (May 27, 2025):

I still don't want to create a password vault, but the "inherited" mode can work.

This means server A can inheried and use server B's password, and when B changes the password, A's password will be updated.

There are many details to consider in this solution, such as whether it is allowed to create a new server C inheriting A, and how A and C should handle the situation after B is deleted.

@VShawn commented on GitHub (May 27, 2025): I still don't want to create a password vault, but the "inherited" mode can work. This means server A can inheried and use server B's password, and when B changes the password, A's password will be updated. There are many details to consider in this solution, such as whether it is allowed to create a new server C inheriting A, and how A and C should handle the situation after B is deleted. ![Image](https://github.com/user-attachments/assets/2f82a6fe-e927-4968-9059-a509fd8ece70)

kerem commented

2026-03-13 12:32:58 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 27, 2025):

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

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

kerem commented

2026-03-13 12:33:03 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 2, 2025):

done by #948

@VShawn commented on GitHub (Jul 2, 2025): done by #948

kerem commented

2026-03-13 12:33:08 +03:00

Author

Owner

@hshsdxx commented on GitHub (Jul 2, 2025):

done by #948

thank you very much for your support

@hshsdxx commented on GitHub (Jul 2, 2025): > done by [#948](https://github.com/1Remote/1Remote/issues/948) thank you very much for your support

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#3665

No description provided.

Rows
Columns