mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #884] Mysterious string is pre-filled in the password field of the dialog #718
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#718
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @itagagaki on GitHub (Mar 8, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/884
Originally assigned to: @VShawn on GitHub.
If "Ask for password when open connect" is checked in the FTP server settings, a very long, mysterious string (garbage?) is pre-filled in the password field of the pre-connect dialog.
@VShawn commented on GitHub (Mar 8, 2025):
I will investigate this.
@itagagaki commented on GitHub (Mar 8, 2025):
Often empty, but it seems that garbage may be the initial value due to some factor.
@VShawn commented on GitHub (Mar 8, 2025):
SO If I keep trying to open this dialog, mysterious string will appear?
@itagagaki commented on GitHub (Mar 8, 2025):
Yes. I experienced ●●●●●●●●●●●●●●●●●●●●●●●●●●●●● in that dialog.
When I tried it again now, it was fine in a normal run (it was always empty), but when I ran the Release build on Visual Studio, it reproduced the problem. Either with “Start Debugging” or “Start without Debugging”.
This may not be an issue, as it is not reproduced in normal execution, but it is worrisome.
@VShawn commented on GitHub (Mar 8, 2025):
ok I will run test on both debug and release build on Visual Studio
@VShawn commented on GitHub (Mar 9, 2025):
I believe I have fixed the bug, but since it does not reproduce consistently, not 100% for sure. feel free to reopen the issue if it occurs again.
@itagagaki commented on GitHub (Mar 9, 2025):
verified that it has been fixed 👍