Hide Forgot
Description of problem: On the control panel, if the user uses the same key name as found in their .ssh/ dir (libra_id_rsa), and add their public key, they get an error: "Invalid key name: libra_id_rsa". But a key named "libra" works. This is building a bit of frustration for our users while trying to work around permission denied issues on git/ssh commands. A question I get from our users is "Why can't we allow underscores (or any chars for that matter)? Its the same name as you assign it on my client". And "Why isn't the error message clearer if its alphanumeric chars only?" Ideally, we should accept any name, especially one that we assign on key creation. Please help them out.
Note to triage team: There is a separate bug (Bug 794506) that deals with lifting some of these restrictions in the name of the keys. This particular bug would be addressed once we fix that one and as such could even be marked as a duplicate.
*** This bug has been marked as a duplicate of bug 794506 ***