From: Herbert Xu <herbert@gondor.apana.org.au>
To: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Cc: smfrench@gmail.com, linux-cifs@vger.kernel.org,
samba-technical@samba.org, linux-crypto@vger.kernel.org
Subject: Re: [linux-cifs-client][PATCH] Enable signing for ntlmv2 within NTLMSSP using kernel crypto APIs
Date: Tue, 3 Aug 2010 16:33:30 +0800 [thread overview]
Message-ID: <20100803083330.GA15074@gondor.apana.org.au> (raw)
In-Reply-To: <AANLkTimtgejfxW8P_GvGqD3muu2Wh6BfC-xPTpNtJb9+@mail.gmail.com>
On Mon, Aug 02, 2010 at 11:46:07PM -0500, Shirish Pargaonkar wrote:
>
> I have compile issues with crypto_shash interfaces, no such issues
> with crypto_hash_ APIs,
> everything works fine.
>
> When I have code like this, I have errors and warning and when I cast
> them as (char *), module
> oopses.
>
> struct session_key {
> unsigned int len;
> union {
> char ntlm[CIFS_SESS_KEY_SIZE + 16];
> char krb5[CIFS_SESS_KEY_SIZE + 16]; /* BB: length correct? */
> struct {
> char key[16];
> struct ntlmv2_resp resp;
> } ntlmv2;
> } data;
> };
> if (server->secType == RawNTLMSSP)
> crypto_shash_update(&desc, server->session_key.data.ntlmv2.key,
> CIFS_NTLMV2_SESSKEY_SIZE);
> else
> crypto_shash_update(&desc, server->session_key.data,
> <----
> server->session_key.len);
>
>
> And
> len = cifs_strtoUCS((__le16 *)user, ses->userName, len, nls_cp);
> UniStrupr(user);
>
> crypto_shash_update(&desc, user, 2 * len);
> <----
>
> No such issues and oops with crypto_hash_APIs.
Please post your entire patch with shash and the oops.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2010-08-03 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 19:34 [linux-cifs-client][PATCH] Enable signing for ntlmv2 within NTLMSSP using kernel crypto APIs shirishpargaonkar
2010-08-02 6:55 ` Herbert Xu
[not found] ` <20100802065508.GA8431-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org>
2010-08-03 4:46 ` Shirish Pargaonkar
2010-08-03 8:33 ` Herbert Xu [this message]
[not found] ` <AANLkTimE0CgvYtrTSxsL5Z-kg5C9k9Lf3pDmW8gkRg7S@mail.gmail.com>
2010-08-04 6:58 ` Herbert Xu
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=20100803083330.GA15074@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=samba-technical@samba.org \
--cc=shirishpargaonkar@gmail.com \
--cc=smfrench@gmail.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