We've been quiet, but we are here, getting things ready for ya. And you know what this tweet also means: is up. Go register your creds for the 802.1X / Enterprise network and get your devices ready before you get here.
#defcon30
#defcon
#roadtoDEFCON
Thanks to our NOC team for another year of hard work and making things just work. You are awesome. Thanks to everyone else who made a point of not breaking our stuff and also those who attended our panel.
No cables to be pulled, no pineapples messing with the WiFiz, no vlans to be configured, not seeing you all in Vegas, this is weird. We are sad not setting up DC’s infrastructure this year. But we're going to be on Discord helping w/ other stuff to make DC SM a success.
For a question we got about using username/ password defcon/ defcon. Is it safe? despite the same username and password, every users get dynamic/ rotating keys. So yes, as secure as any enterprise level eap-peap 802.1x network can be. Pick your uname/pass though.
#defcon
So, after some hacking and digging deep on figuring out how chrome books work,
@c7five
and
@ajohntitor
figured out how to make it work. Check wifireg for instructions and download the CB profile
It looks like the cert format acceptance still varies depending on the flavor of Android being used. Couple of devices we tested with the original instructions worked just fine. So here is a good tip: convert to DER. Thank you
@dakacki
What if it would have been a PSK secure network? Oh wait, never mind, same as open … you’re still invited for a NOC handshake at DC31.
@JeppsonsMalort
and some eye drops
@dakacki
Yeah. No. It’s the open network, no hunting, just Malört drinking. From the program: And the original, unencrypted, stick-shift, no ABS, wildest-westest of the wireless networks: DefCon-Open
@boblord
@c7five
@ErrataRob
@alexhutton
It looks like chrome books still don’t like verifying server side certificate for 802.1X, making then the connection insecure and defeating the point of having such type of authentication. If anyone has successfully implemented CBs and 802.1X, we are all ears