Skip to content
This repository was archived by the owner on Apr 11, 2024. It is now read-only.

Commit 2f2bf94

Browse files
committed
fixup! feat: Add user configuration for all providers
Explain why we do not validate hashed password input
1 parent 915fb78 commit 2f2bf94

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

api/v1alpha1/clusterconfig_types.go

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -395,8 +395,14 @@ func (User) VariableSchema() clusterv1.VariableSchema {
395395
Type: "string",
396396
},
397397
"hashedPassword": {
398-
Description: "The hashed password for the user",
398+
Description: "The hashed password for the user. Must be in the format of some hash function supported by the OS.",
399399
Type: "string",
400+
// The crypt (5) man page lists regexes for supported hash
401+
// functions. We could validate input against a set of
402+
// regexes, but because the set may be different from the
403+
// set supported by the chosen OS, we might return a false
404+
// negative or positive. For this reason, we do not validate
405+
// the input.
400406
},
401407
"sshAuthorizedKeys": {
402408
Description: "A list of SSH authorized keys for this user",

0 commit comments

Comments
 (0)