An open-source, self-hostable solution providing 80% of common Google Analytics functionality seems doable to me.
Is there anything out there in this realm? If not, why not?
Is there anything out there in this realm? If not, why not?
https://github.com/piwik/piwik/blob/7f375924db9328f20a0b7cb1...
https://github.com/piwik/piwik/blob/6846145992278b52a2a35a8f...
There's an open ticket for it, but it looks like it hasn't been addressed in a while since they don't want to break all existing passwords.
I'll write an exploit for it (the general case, not just Piwik in particular) and drop it on OSS Sec some day, but here's a theoretical attack:
1. Guess a username somehow. Maybe "admin"? Whatever, we're interested in the security of the hash function. Let's assume we have the username for our target.
2. Calculate a bunch of guess passwords, such that we have one hash output for each possible value for the first N hexits.
e.g.
substr(md5($string), 0, 2) === "00"
substr(md5($string), 0, 2) === "01"
substr(md5($string), 0, 2) === "02"
// ...
substr(md5($string), 0, 2) === "ff"
4. Iterate steps 2 and 3 until you have the first N bytes of the MD5 hash for the password.
5. Use offline methods to generate password guesses against a partial hash.
The end result: A timing attack that consequently allows an optimized offline guess. So even if their entire codebase is immune to SQL injection, you can still launch a semi-blind cracking attempt against them.
Any centralized solution, at any scale, can possibly violate someone's privacy. Period. If we want to really fix things, we should stop circle jerking ourselves and do something about it.