* This handler debunks a quite bad example of how to "protect" your site from Firesheep's sidejacking ability. * Details on the supposed "fix": http://akfpartners.com/techblog/2010/11/20/slaying-firesheep/
* This will make Firesheep requests of Facebook, Twitter, and Google encrypted, as to prevent the additional leaking of information. * Should also break how Firesheperd and Blacksheep currently detect Firesheep based on Facebook requests (though it's still certainly possible to detect and mess with it)
As far as I know, these sites are no longer insecure.
… use info.product from HAL
…lter is set but let's be safe) * Silence compiler (init ip and ipv6 structs to NULL)
…(that means radiotap header + 802.11 header + LLC + data) * Added __packed__ atribute on all structs that we map directly to the packet buffer (headers mostly). Without it compiler aligns their elements based on cpu/os etc to optimize performance and this can result bad mapping. On visual studio we use te __pragma(pack()) attribute (but haven't tested it, it should work).
* Needs policykit installed (no need to manualy set permissions on backend)