From: Hans de Goede <hdegoede@redhat.com>
To: Prasanth KSR <kosigiprasanth@gmail.com>, dvhart@infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Prasanth KSR <prasanth.ksr@dell.com>,
Divya Bharathi <divya.bharathi@dell.com>
Subject: Re: [PATCH] platform/x86: dell-wmi-sysman: Change user experience when Admin/System Password is modified
Date: Mon, 28 Jun 2021 11:01:41 +0200 [thread overview]
Message-ID: <e9818bf6-13fb-dec1-c2ee-87ecb2b2cc20@redhat.com> (raw)
In-Reply-To: <20210628084906.4233-1-prasanth.ksr@dell.com>
Hi,
On 6/28/21 10:49 AM, Prasanth KSR wrote:
> Whenever user has changed an Admin/System Password using the sysfs,
> then we are automatically copying the new password to existing
> password field.
>
> Co-developed-by: Divya Bharathi <divya.bharathi@dell.com>
> Signed-off-by: Divya Bharathi <divya.bharathi@dell.com>
> Signed-off-by: Prasanth KSR <prasanth.ksr@dell.com>
Thank you.
I assume this was tested? The reason I'm asking because in the
Lenovo Think* case it turned out that the modified password only
becomes active after a reboot, so the right thing to do there was
to just keep current_password as is.
Regards,
Hans
> ---
> .../x86/dell/dell-wmi-sysman/passwordattr-interface.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/dell/dell-wmi-sysman/passwordattr-interface.c b/drivers/platform/x86/dell/dell-wmi-sysman/passwordattr-interface.c
> index 339a082d6c18..86ec962aace9 100644
> --- a/drivers/platform/x86/dell/dell-wmi-sysman/passwordattr-interface.c
> +++ b/drivers/platform/x86/dell/dell-wmi-sysman/passwordattr-interface.c
> @@ -95,9 +95,9 @@ int set_new_password(const char *password_type, const char *new)
>
> print_hex_dump_bytes("set new password data: ", DUMP_PREFIX_NONE, buffer, buffer_size);
> ret = call_password_interface(wmi_priv.password_attr_wdev, buffer, buffer_size);
> - /* clear current_password here and use user input from wmi_priv.current_password */
> + /* on success copy the new password to current password */
> if (!ret)
> - memset(current_password, 0, MAX_BUFF);
> + strscpy(current_password, new, MAX_BUFF);
> /* explain to user the detailed failure reason */
> else if (ret == -EOPNOTSUPP)
> dev_err(&wmi_priv.password_attr_wdev->dev, "admin password must be configured\n");
>
next prev parent reply other threads:[~2021-06-28 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 8:49 Prasanth KSR
2021-06-28 9:01 ` Hans de Goede [this message]
2021-06-28 9:05 ` Ksr, Prasanth
2021-06-28 9:15 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e9818bf6-13fb-dec1-c2ee-87ecb2b2cc20@redhat.com \
--to=hdegoede@redhat.com \
--cc=divya.bharathi@dell.com \
--cc=dvhart@infradead.org \
--cc=kosigiprasanth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prasanth.ksr@dell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®