Bug 496024 - Allow pasting key with spaces in it
Summary: Allow pasting key with spaces in it
Status: REPORTED
Alias: None
Product: Keysmith
Classification: Applications
Component: General (other bugs)
Version First Reported In: 24.08.2
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Bhushan Shah
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-09 20:53 UTC by Grósz Dániel
Modified: 2025-04-07 16:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grósz Dániel 2024-11-09 20:53:19 UTC
SUMMARY
Gitlab displays the secret key with letters/numbers grouped in groups of 4 with spaces between the groups. When adding an account in Keysmith, it doesn't allow pasting a string with spaces in it at all, I assume because spaces are not allowed in keys (typing space does nothing). This is confusing and inconvenient, especially to someone unfamiliar with 2FA key formats. I suggest allowing pasting keys with spaces (and perhaps other invalid characters such as punctuation, in case some site puts e.g. hyphens in them, Idk if that's common), and remove them when pasting.

STEPS TO REPRODUCE
1. Click Add
2. In the Secret key field, paste something like AAAA AAAA AAAA AAAA AAAA AAAA AAAA AAAA.

OBSERVED RESULT
Nothing is pasted.

EXPECTED RESULT
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA is pasted.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20241107
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-1-default (64-bit)
Graphics Platform: X11
Comment 1 Karl Robillard 2025-04-07 15:57:51 UTC
I ran into this problem adding an account for a financial services company which also uses the 4 character grouping.

It was indeed confusing when pasting was unresponsive, and I assumed it was because the key was too long and/or the wrong type of key.

Typing such a long key manually was difficult because the characters are hidden as dot characters.  There needs to be an option on the "Secret key" field to show the characters.  Should I open another issue for that?
Comment 2 Grósz Dániel 2025-04-07 16:05:46 UTC
(In reply to Karl Robillard from comment #1)
> Typing such a long key manually was difficult because the characters are
> hidden as dot characters.

A workaround here is to replace spaces with nothing in a text editor, so you don't have to type it manually.

> There needs to be an option on the "Secret key"
> field to show the characters.  Should I open another issue for that?

I guess so.