From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT] [CIFS] Allow user names longer than 32 bytes
Date: Mon, 28 Feb 2011 14:04:51 -0500 [thread overview]
Message-ID: <20110228140451.056ee6ea@corrin.poochiereds.net> (raw)
In-Reply-To: <20110228135935.1486b3dc-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
On Mon, 28 Feb 2011 13:59:35 -0500
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> On Fri, 25 Feb 2011 12:24:17 -0600
> Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > commit 355e57ca063338eb00ea067a7570bb5f136cc513
> > Author: Steve French <sfrench-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> > Date: Fri Feb 25 01:11:56 2011 -0600
> >
> > [CIFS] Allow user names longer than 32 bytes
> >
> > We artificially limited the user name to 32 bytes, but modern servers handle
> > larger. Set the maximum length to a reasonable 256, and make the user name
> > string dynamically allocated rather than a fixed size in session structure.
> > Also clean up old checkpatch warning.
> >
> > Signed-off-by: Steve French <sfrench-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
>
> [...]
>
> > diff --git a/fs/cifs/cifsencrypt.c b/fs/cifs/cifsencrypt.c
> > index a51585f..e307a28 100644
> > --- a/fs/cifs/cifsencrypt.c
> > +++ b/fs/cifs/cifsencrypt.c
> > @@ -469,15 +469,15 @@ static int calc_ntlmv2_hash(struct cifsSesInfo
> > *ses, char *ntlmv2_hash,
> > return rc;
> > }
> >
> > - /* convert ses->userName to unicode and uppercase */
> > - len = strlen(ses->userName);
> > + /* convert ses->user_name to unicode and uppercase */
> > + len = strlen(ses->user_name);
> > user = kmalloc(2 + (len * 2), GFP_KERNEL);
> > if (user == NULL) {
> > cERROR(1, "calc_ntlmv2_hash: user mem alloc failure\n");
> > rc = -ENOMEM;
> > goto calc_exit_2;
> > }
> > - len = cifs_strtoUCS((__le16 *)user, ses->userName, len, nls_cp);
> > + len = cifs_strtoUCS((__le16 *)user, ses->user_name, len, nls_cp);
> > UniStrupr(user);
> >
>
> Now that user_name can be a NULL pointer, what prevents the code above
> from oopsing if no one passes in a user= parm?
>
Oh, and another problem too...
cifs_construct_tcon does a stack allocation for a temporary username field:
char username[MAX_USERNAME_SIZE + 1];
That was probably ok when this was 33 bytes, but now that it's 257 it's
a little more scary. That should probably be switched to a kzalloc'ed
buffer too.
--
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
next prev parent reply other threads:[~2011-02-28 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 18:24 [GIT] [CIFS] Allow user names longer than 32 bytes Steve French
[not found] ` <AANLkTimMxszw620jHORHYQ_jj-fhQiXUe=AiAFRAtMLU-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-28 18:59 ` Jeff Layton
[not found] ` <20110228135935.1486b3dc-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-02-28 18:58 ` Steve French
2011-02-28 19:04 ` Jeff Layton [this message]
[not found] ` <20110228140451.056ee6ea-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-02-28 19:43 ` Steve French
2011-02-28 21:09 ` Steve French
[not found] ` <AANLkTi=8CvigLkhK3V4Tf1=HgiYsKi7C6gUoLKTZc-My-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-28 22:39 ` Jeff Layton
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=20110228140451.056ee6ea@corrin.poochiereds.net \
--to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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