Why are Flash Cookies Harmful?
- they are never expiring – staying on your computer for an unlimited time.
- by default they offer a storage of 100 KB (compare: Usual cookies 4 KB).
- browsers are not aware of those cookies, LSO’s usually cannot be removed by browsers.
- via Flash they can access and store highly specific personal and technical information (system, user name, .).
- ability to send the stored information to the appropriate server, without user’s permission.
- flash applications do not need to be visible to the user
- there is no easy way to tell which flash-cookie sites are tracking you.
- shared folders allow cross-browser tracking, all browsers use the same LSO folder
- the company doesn’t provide a user-friendly way to manage LSO’s, in fact it’s incredible cumbersome.
- many domains and tracking companies make extensive use of flash-cookies.
- flash-cookies are used to re-create data of deleted traditional cookies.
Read more about LSO’s on wikipedia and Download Better Privacy firefox extension to keep track of those who keep track of you!
I deleted all instances of ‘amarok’ in
$HOME/.kde4/share, and dropped the ‘amarokdb’ database, and dropped ‘amarokuser’, and re-created everything, but it still wouldn’t connect.
It turns out the solution is simple. Just change the password in the Amarok settings page from ‘password’ to something else (e.g. ‘password123’). Change the ‘amarokuser’ password, too, in mysql. Restart Amarok, and they can connect.
This is a bug in Amarok, as it doesn’t have a default password configured, one must be explicitly set. Source
Iwl3945 is the new driver for the Intel PRO/Wireless 3945ABG wireless chipset. It includes new features like:
- Managed and monitor mode support in one driver
- Enhanced injection support
- Multiple interfaces on one device – use the aircrack suite on a monitor interface while remaining associated on a managed interface
- Full radiotap support, for both incoming and outgoing packets
- No more binary regulatory daemon needed, regulatory enforcement is done by the firmware
The driver is based on the mac80211 stack, so the usual requirements apply (aircrack-ng 1.0-rc1, a recent version of libnl, a fairly new kernel, etc.)
I’m quite excited about this, because previously my chip wasn’t able to do packet injection. Now, I can force WEP client to dissassociate from their WAPs, and I can potentially break WEP! My Core2Duo 1.8GHz machine may not have the horsepower, but my AMD 6400+ X2 can certainly handle it.
Aircrack-NG and Intel iwl3945 Driver