[Dextrose] [Sugar-devel] [sugar 0.96, NM 0.9 PATCH] sl#3727: Return cached secrets, present in 'settings' themselves.

[Ajay Garg]

Yep..
Sorry Peter, Anish.

So, as far as the current patch is concerned, this patch should be tested
WITHOUT thinking about the WPA-Enterprise Networks scenario.



That should bring us back on the track (for this particular patch) :P


Regards,
Ajay


On Mon, Jun 25, 2012 at 8:31 PM, Anish Mangal <anish at activitycentral.com>wrote:

> Not to take the discussion in a different direction, but IMO, would be
> great if Enterprise network support made it to upstream sugar. :-)
>
> On Mon, Jun 25, 2012 at 8:22 PM, Ajay Garg <ajay at activitycentral.com>
> wrote:
> > Peter,
> >
> > Is WPA-Enterprise Networks supported in Sugar 0.96, yet? (I don't think
> it
> > is).
> > As a result, the current patch has not been tested with WPA Enterprise
> > Networks.
> >
> > There is a patch for WPA-Enterprise Networks (fully integrated in
> dextrose3)
> > available at
> > http://patchwork.sugarlabs.org/patch/1096/
> >
> > with specs at
> >
> http://wiki.sugarlabs.org/go/Features/WPA-WPA2-Enterprise-Network-Connections
> >
> > Would upstream be interested :P :P (I would be more than willing to port
> > it).
> >
> >
> >
> > Adding Anish in the loop.
> >
> >
> > Regards,
> > Ajay
> >
> >
> >
> >
> > On Mon, Jun 25, 2012 at 8:07 PM, Peter Robinson <pbrobinson at gmail.com>
> > wrote:
> >>
> >> On Sun, Jun 24, 2012 at 12:00 PM, Ajay Garg <ajay at activitycentral.com>
> >> wrote:
> >> >
> >> > NM may request the secrets in the following cases ::
> >> >
> >> > a)
> >> > Wifi connection is lost.
> >> >
> >> > b)
> >> > After being lost, the wifi connection is again within the range.
> >> >
> >> > c)
> >> > When the credentials for the wifi network change.
> >> >
> >> >
> >> > In every case, secrets were being requested via the popup dialog.
> >> >
> >> > However, case c) is rare (and when it does happens, usually the
> >> > system-administrator, or the like,
> >> > has the responsibility for issuing the changes publically).
> >> >
> >> > Thus, due to case c) (which is rare), cases a) and b) were suffering
> >> > (these cases are generally
> >> > very plausible cases in everyday life).
> >> >
> >> >
> >> > So now, the intended solution is :::
> >> >
> >> >
> >> > 1.
> >> > Always return the cached secrets (present in 'settings' themselves).
> >> > This would make the irritating dialog-box go away, for cases a) and
> b).
> >> >
> >> >
> >> > 2.
> >> > For case c), the user would ::
> >> >
> >> >    (i)   "Discard Network History".
> >> >    (ii)  Click on the wifi icon (in the neighborhood-view).
> >> >    (iii) Enter the new (publically broadcasted) credentials.
> >>
> >> This biggest time for C is when it's WPA-Enterprise and the enterprise
> >> user authenication has a lifetime on the password. Our corp wifi is AD
> >> authenticated and the password expires every 60 days.
> >>
> >> Peter
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/dextrose/attachments/20120625/44a69098/attachment.html>