<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=367682) </details> <!--IssueSummary end--> In contrast to the comment https://gitlab.com/gitlab-org/gitlab/-/issues/213259#note_827207788 given in another issue, I want to point out that even a `no-touch-required` security key backed ssh key is still a major improvement over using a "normal" ssh key. The `no-touch-required` can not be simply copied/"stolen", i.e. only works if the corresponding key is present in the machine. I do not object that it would be way more secure to require an interaction. However, requiring an interaction for each remote action can be a major showbreaker imho. Therefore, it would be nice to have the additional option of no-touch-required keys. (Allowing to have keys which require interaction and others which do not) This option would not distrubt the current user flow and also allow some batch/automation on the user machine as long as the security key is connected.