-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Password Security #716
Password Security #716
Conversation
// We're already using mui, why are we reinventing the wheel? https://mui.com/material-ui/react-text-field/ | ||
// if it's a matter of className control on the underlying components, that still works with the mui textfield with the InputLabelProps prop and other componentProps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://mui.com/material-ui/react-text-field/
I forgot about us recreating the TextField manually
I still hate it, but this time around I'm gonna make an issue out of that and solve it myself
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why just pandora?
key={field.name} | ||
name={field.name} | ||
desc={field.desc} | ||
type="password" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you just toggle this field on & off instead of duplicating this many lines of code and having a conditional return value?
Not just pandora, pandora is just the only one I know of that has a password and so I named the branch after that, it still works with all parts labeled "password" on the stream create and edit modal |
switch (field.type) { | ||
case "text": | ||
let type = "text"; | ||
if(field.name == "password"){ | ||
type = "password"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think i'd probably prefer to change the type
of the password fields, instead of behaving magically with specifically named text
fields. this also creates a new component - it's perhaps somewhat more LOC, but more maintainable, and you don't have to change the interface of some underlying component.
fef0f07
to
060aeba
Compare
4ce433a
to
fbf38e0
Compare
Update CHANGELOG.md Streamline password redacting Add default option for StreamModal boxes Remove required tag, add default value to type on custom TextField element Explicitly handle input types
fbf38e0
to
8f18f29
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks~ pardon it was so much back & forth
What does this change intend to accomplish?
Minor security improvement
The password is still plaintext in the backend, but it is now not copyable from the textbox and the textbox converts it into dots as password fields should
Checklist
./scripts/test