Linux wireless drivers development
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	libertas-dev@lists.infradead.org
Subject: Re: [PATCH] libertas: implement new scanning logic
Date: Fri, 07 Dec 2007 18:33:32 +0000	[thread overview]
Message-ID: <1197052412.13978.620.camel@pmac.infradead.org> (raw)
In-Reply-To: <1197051857.30465.30.camel@localhost.localdomain>


On Fri, 2007-12-07 at 13:24 -0500, Dan Williams wrote:
> You can really just take that NOKEY line out completely, you don't need
> anything else in this patch.

Well, there's no point in setting/clearing IW_ENCODE_DISABLED twice,
which is why I removed that bit...

> > -	if (   adapter->secinfo.wep_enabled
> > -	    || adapter->secinfo.WPAenabled
> > -	    || adapter->secinfo.WPA2enabled) {
> > -		dwrq->flags &= ~IW_ENCODE_DISABLED;
> > -	} else {
> > -		dwrq->flags |= IW_ENCODE_DISABLED;
> > -	}
> > -
> >  	memset(extra, 0, 16);
> >  
> >  	mutex_lock(&adapter->lock);


And since I don't see anywhere that we'd copy a WPA key into the
response, I figured it made sense to keep IW_ENCODE_NOKEY in this bit
too: 

> > @@ -1150,14 +1142,13 @@ static int lbs_get_encode(struct net_device *dev,
> >  		   || (adapter->secinfo.WPA2enabled)) {
> >  		/* return WPA enabled */
> >  		dwrq->flags &= ~IW_ENCODE_DISABLED;
> > +		dwrq->flags |= IW_ENCODE_NOKEY;
> >  	} else {
> >  		dwrq->flags |= IW_ENCODE_DISABLED;
> >  	}

I'd want to set up an AP with WPA and test it if I was going to actually
make it find and return the WPA key.

-- 
dwmw2


  reply	other threads:[~2007-12-07 18:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  8:27 [PATCH] libertas: implement new scanning logic Holger Schurig
2007-11-29 19:38 ` Dan Williams
2007-12-04 16:52 ` Dan Williams
2007-12-04 20:34   ` Holger Schurig
2007-12-07 14:47   ` Holger Schurig
2007-12-07 17:57     ` Dan Williams
2007-12-07 18:05       ` David Woodhouse
2007-12-07 18:09         ` Dan Williams
2007-12-07 18:19           ` David Woodhouse
2007-12-07 18:24             ` Dan Williams
2007-12-07 18:33               ` David Woodhouse [this message]
2007-12-07 19:14                 ` Dan Williams
2007-12-07 19:34                   ` David Woodhouse
2007-12-07 18:12         ` Dan Williams

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=1197052412.13978.620.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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