Project

General

Profile

Actions
Copy link

Bug #6601

open

[API] Do not accept an empty SSH key as valid

Added by Brett Smith almost 9 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
Future
Story points:
0.5
Release:
Postponed
Release relationship:
Auto

Description

When a user creates a new AuthorizedKey, the API server validates that the key represents real key material, to help avoid problems where a typo or mis-paste prevents the key from working.

The validation currently allows an empty public key as valid. This should be prohibited: it makes no more sense than having a malformed public key.

Actions
Copy link
 #1

Updated by Ward Vandewege almost 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions
Copy link
 #2

Updated by Peter Amstutz about 1 year ago

  • Release set to 60
Actions
Copy link
 #3

Updated by Peter Amstutz about 2 months ago

  • Target version set to Future
Actions
Copy link

Also available in: Atom PDF