From Lauren, a new "feature" in Windows 10 I think this community probably
wants to know about, to the extent you don't already.
I *knew* I didn't like W10. 
Cheers,
-- jra
There is a reason why my family loves open source. My kid is learning Linux and she doesn't even know it. Mommy has an Android...
It gives it to one degree of friends on <insert social media here>. So those friends can't share it again.
I'm still changing my networks to EAP, though.
Does that happen with 802.1x logins, too?
Andrew
This isn't really an open source issue -- anybody can make foolish product
design decisions regardless of licensing model. This is more about a vendor
producing a feature that deliberately and shortsightedly creates a slew of
problems impacting almost all existing networks anywhere. It's highly
convenient feature for a specific, limited use case (home users hosting a
party with a bunch of people that they don't want to have to worry about
how to give them a network password). However, gat ignores all of the other
security and user impact issues. Can you imagine how the user experience
will change when you change your SSID to include the _optout tag and then
try to verbally tell someone what the new SSID is? Bonus points for dealing
with users in a context where you've had the same SSID for years.
Bonus-bonus points for throwing in language barriers.
Triple-bonus points if your SSID is called “Underscore”
-jav
Time to teach home-routers WPA Enterprise auth? Then at least you know
whom to blame 
and just one user to disconnect instead of everybody
who previously had the key.
Well, but if "friends" were to share your wifi-key through other ways
the end-result would be the same. Just hand your key to "clueful"
people. I think the point here is that we might assume people have a lot
of good friends who don't know what they are doing (have things like
this enabled by default)? Hmm ... yeah might be 
Kind regards,
Stefan
Bonus points for telling 40,000 users what the new campus SSID is....
Was Microsoft *trying* to make sure they weren't welcome in enterprise
environments?
ObNANOG: How does this interact with Comcast/Xfinity's wireless hotspot
thing, where it *used* to be that customers could get on anyplace, but now
it's "customers and anybody they happen to know?"
Yeah that's scary!
I have seen similar feature across multiple apps on Android and iOS. To
deal with them I do mac filtering along with WPA + separate guest network
where I can share password.
We've been had! This is all just a giant ploy by Microsoft to push EAP adoption on WLANs! Expect to see some turn-key RADIUS solution from Microsoft in Windows 10. Marketing headline:
"Prevent unauthorized access to your corporate WLANs! For the low price of $OH-MY-GOD-YOU-MUST-BE-JOKING!, get Windows Systems Center WLAN Defender today!"
Those sly devils... 
Does that happen with 802.1x logins, too?
No.
Yes and no.
It’s not about licensing, but it is about the fundamental difference between open
and closed development models.
When you make a stupid product design decision in a vacuum (closed model),
and only the people drinking the same kool-aid ever see your decision on a source
code level, it’s a lot easier to ship that bad decision out into widespread use. Further,
the people now afflicted with your bad decision are beholden to you in order to get
a fix for the problem(s) it has created.
OTOH, when you try to do something stupid like this in the open source world, there
are far to many eyeballs looking at what gets submitted for it to last long. Anyone and
everyone can contribute a fix. Any victim has access to everything they need in order
to fix it themselves.
Owen
Android shares your wifi password with Google. Including the password of everyone's wifi you've ever logged into.
I long for the days of a good old fashion, bar, that made calls and received them.
The smart phones are "smarter" than I am, but that is not much of a challenege either!
Terrible idea. These are the kind of features that should be opt in, and
Microsoft could have done that instead.
Does the 802.11 beacon support TLV data, like setting some opt-out flag
without changing the SSID? (Even if the the flag name hasn't been yet
agreed on?) Would this be a bad idea?
Best regards.
Terrible idea. These are the kind of features that should be opt in, and
Microsoft could have done that instead.
It *is* an option. When you're setting up Windows 10, it asks you two
screens of configuration questions, but most people will hit the
"Use express settings" option and just blow past the choice. I don't
know, most of the express settings seem to be craptacular to me, so I
always go through all the "defaults" and usually find myself flipping
many/most of them. But that's probably because I am not in search of
automated Cortana and Bing magic page prediction goodness that auto-
matically shares my name, location, and advertising ID with every
random website that it possibly can (hyperbole?? maybe??)
Anyways, if you look on the first page of "Customize settings", yes
there's an option for "Automatically connect to networks shared by my
contacts" and it CAN be turned off, but it defaults to on.
I didn't spend a lot of time trying to figure out exactly how that'd
work. I don't really want my "contacts" or any other data being sent
to Microsoft's servers. I have my own servers that I'm reasonably
happy with. I have an uneasy feeling that if set I'd find it to be
slurping a lot of data over to Microsoft's servers and I guess I would
not be shocked to find that 50 of my best friends on NANOG are suddenly
(and unexpectedly) populating WiFi passwords at me.
I suppose I could be wrong, but it's amazing how many LinkedIn invites
I get from people I've never heard of, who seem to only have a mailing
list in common, etc.
... JG
Defaults matter. Every configuration parameter has a default setting, whether intentional or not.
This is on by default in the beta like all the reporting in MS.
Will probably be either a prompt in the RTM version.
"Sean Donelan" <sean@donelan.com> writes:
> Anyways, if you look on the first page of "Customize settings", yes
> there's an option for "Automatically connect to networks shared by my
> contacts" and it CAN be turned off, but it defaults to on.Defaults matter. Every configuration parameter has a default setting,
whether intentional or not.
Well of course defaults matter. We work in an industry where the
defaults supplied by most tech companies for the average user are quite
depressing to me. People want easy and many don't bother to understand
or (even worse) care about privacy. Just look at web advertising and
tracking. As bad as that is on the general Internet, even I was a bit
shocked to find yesterday while training NoScript on a new VM that a
certain wireless carrier's customer portal was reaching out to maybe as
many as twenty different ad and tracking networks, including Bing,
Yahoo, and Google, in order for you to log in and pay your bill.
This stuff is frickin' pervasive. The default is "track the hell out
of everyone" and "share everything you can."
I remember first seeing the Windows 10 "share networks to contacts" and
trying to imagine that it meant anything other than wifi access creds.
That's part of the problem. They don't even tell you what the words
are actually saying, or why it matters one way or another. For those
There's a subtle but important difference between that and "Allow this
device to send sharing info to contacts".....