Hmm. Really needs a way to save and resume editing a "shred" I was in the middle of selecting some different portions of a bunch of videos and accidentally quit. Seems like an app with potential though.
Sort of related to this post; I recently read Atomic Accidents: A History of Nuclear Meltdowns and Disasters: From the Ozark Mountains to Fukushima [0]. I was not expecting much from the book, but it turned out to be FANTASTIC, would highly recommend if you have any interest in nuclear accidents or nuclear energy in general; I learned a lot from reading it.
Interesting, glanced through your paper. How do you find real devices behave at constrained channel widths (<20Mhz in 2.4, <40Mhz in 5)? I have a feeling those are not well tested scenarios :)
Hmm, I have not read his paper, but based on the article's mention of "divided into 13 channels" this is clearly speaking of the 2.4Ghz spectrum. Rather than try to distribute that evenly, you are FAR better off upgrading your AP and switching to a 5Ghz channel. First, there are far more potential channels in 5Ghz. Second, they are wider bandwidth (40Mhz, 80Mhz if 80211ac). And third, 5Ghz does not propagate through walls as well (a _feature_ when you have neighbors also using the spectrum).
My other thoughts: if he is using 8 channels instead of the standard 3 (1,6,11) then there will be some overlap; 80211 devices tends to better handle in-channel interference. http://en.wikipedia.org/wiki/List_of_WLAN_channels
This only occurs for 'hidden' networks. If you do not have any hidden networks in your known network list than you will not be broadcasting SSIDs. This is yet another reason to avoid setting your AP to hidden.
I stuck with lynx for the longest time. Somewhere around 2007 the web became COMPLETELY unusable, even on the subset of sites I would visit. Sad times we're living in. :)
On iOS 7 you have to explicitly trust a computer from the device before data is allowed over USB; before that it is in a charge only mode. To trust a computer you must unlock the device.
I think cbhl's point is perfectly valid, in the presentation of the feature, Apple states that about half of people leave their phones w/o a PIN. Touch ID is for these people and in general will make unauthorized access to iPhones more difficult.
Touch ID is optional, if a user feels particularly concerned, about legal implications of this, it is perfectly valid to revert to a passcode. I am glad that this article/discussion exists though, it is good to know what risks may exists using new security systems.
[Edited to add: just read somewhere else that after 48 hours of inactivity or a reboot, user must re-enter passcode before fingerprint will unlock the device. This would seem to protect from the case stated in the article.]
I haven't been in touch with Aaron for several years, but I had a brief encounter with him in 2008. I was between jobs and decided to help out with his watchdog.net project of the time. He was always incredibly kinda and once tracked down my number and called to check that I was OK after I was unexpectedly offline for a several days.
I was thinking the same thing. The key to a vibrant app ecosystem is making profit for developers. Possibly these apps are making ad money, but yet to be seen.
Maybe for an individual user "3g" is sufficient, but my understanding is that it is a poor use of spectrum. One big motivator to move to LTE will be in congested areas where everyone simply cannot be served sufficient bandwidth with the legacy technology.
For instance, my willingness to put up with an initial learning curve vs working with an "intuitive" interface. You may call these "design decisions" and that a well designed UI/UX could be a part of any point on that spectrum, but they are design decisions made by the people in charge of UI/UX and impact the final UI/UX.
It is why I become frustrated using a many GUI programs when all I really want is to write a damn awk script :)
I wish they shot something with motion in low light... From pictures my friends post online, my biggest complaint about most point and shoot (and phone) cameras in low light is not digital noise, but motion blur. I would prefer manufactures to bump the gain and take faster exposures.
It would be more interesting to check ngrames to see how frequently you must hit a key on the same hand twice. Qwerty was designed to prevent jamming typewriters, IIRC.
1. The attack is to brute force the shared secret (password). This can be done offline because by capturing the exchange you have the ANonce and SNonce and all other information required to generate the same key -- except the shared secret. Try lots of passwords and check if you generate the same PTK as the two stations do.
2. Encrypted with what? This is the key exchange stage that is attacked here.
802.11w adds signing to management frames which eliminates the deauth attack -- makes it harder to capture the EAPOL frames. Also, IIRC, WPA2-enterprise would not be susceptible to this sort of attack; you've pre-shared a key rather than a (short) password for generating one.
I recently picked up an ESP8266 for a project, but yet to start farting around with it. Excited to find some spare time.