If you've registered already, and you're still logged in there's a chance i've lost your password. If so you should see a message telling you so in your account page. If you don't see the message, don't worry about it.
You can't use a "random" salt (such as one generated from the rand function) because then you can't calculate the hash later to verify they entered the correct password, unless of course you store that "random" salt in the database, which would defeat the purpose if your database is compromised.
Typically hash's are calculated using something like:
$hash = sha1($password."secretcode".$username); - none of which are random.
If you were to add a random number into that like this:
$rand = rand(1,99);
$hash = sha1($password.$rand);
Now you can't do if($hash1 = $hash2) { loginSuccess(); } because you will never know what random salt was generated for the original hash.
>unless of course you store that "random" salt in the database, which would defeat the purpose if your database is compromised.
Not true, a plain hash can be compromised with a brute force attack. To do this all the entries in the dictionary(used in the attack) must be hashed using the same hash algorithm.
If each password entry is hashed with a random salt(with the salt being kept for password comparison) the attacker must rehash the entire dictionary(not a computationally cheap thing to do) including the random salt, for each and every password.
This doesn't make it impossible to brute force a hash+salt, but makes it a LOT more expensive and time consuming.
At least this is my understanding of the whole point of random salted hash.
this is my understanding too, even if someone breaks into the db and gets the list of salts and passwords, they can't use rainbow tables because of the "random" salts, so finding the plain text passwords becomes computationally too expensive to accomplish.
The map on the home page shows all the registered users, currently just the two of us lol, it groups them in to hot spots, but it's hard to see until there's more users.
The registration form is geocoded, it just wasn't working correctly, fixed now.
I run www.trackmycv.com and www.finddjs.co.uk on it as well as several company intranets. I've been using it for about 18 months, in my opinion it's the quickest, cleanest PHP framework out there. It's got loads of features, it's well documented, sanely laid out and fully extendible, can't recommend it highly enough
Wouldn't it be better to tie a phone number to an email address? An email address is still much more memorable than a phone number but the crowded namespace issue has already been solved. You could add something similar to an MX record to your domain's DNS that specifies where your "phone number server" is. The phone number server would be a simple database of username/alias and "real" phone number (although it could be expanded to do redirects, voicemail, 404s etc). The client making the call then consults this server which returns the number that it should dial.
"This is pretty cool because it means that anything that can speak DNS (pretty much everything) could have programmatic access to this data."
I don't think this offers an advantage over my solution, as any application that needs to use this will have to be modified anyway, the protocol I'm proposing would be equally trivial (or not) to implement.
Using an e-mail address as your identifier kind of defeats the purpose.
Google's webfinger takes this approach, using TXT records to map your email address to an XRD document. But this adds a lot more complexity and means doing an extra HTTP request - so now it's much slower than a single DNS query and there's probably a SPoF.
it wouldn't have to be a SPoF, you'd just replicate your server and add an additional record, if the client can't reach the first server it failovers (failsover? fails over?) to the next one.
I don't think it adds to the complexity too much and it's hardly going to be slow - it'd be much faster than the time it takes to send even the smallest email message.
Well, if you're looking up a name, for example from a dialer on a mobile device, or navigating through some kind of directory service; are you going to be happy hanging around for a HTTP request (or several)?
DNS was born to do this; it's lightweight, super fast and wonderfully distributed. :)
A fraction of a second delay probably wouldn't be noticeable to the end user - you'd only ever lookup the number when actually making the call. DNS may be distributed but that's part of the problem - you can't just set your address to redirect to another number when you're out on lunch - it'd take too long for the changes to propagate through the system. You wouldn't put email addresses at the DNS level, so why do this?
>A fraction of a second delay probably wouldn't be noticeable to the end user
It is (try it), and retries/outages would be very noticeable. One of the applications I'm particularly interested in is directory services, and as you can imagine browsing through trees is extremely sensitive to responsiveness. Dialing a name should also be near instantaneous.
>DNS may be distributed but that's part of the problem - you can't just set your address to redirect to another number when you're out on lunch
You can (.tel allows you to switch between "profiles").
>it'd take too long for the changes to propagate through the system.
You can set TTLs to whatever you like (60 by default).
FTA:
"...about one third of the companies that had laid people off subsequently rehired some of them as contractors because they still needed their skills."
This happened to me a few months ago, I was made redundant by my employer only to be immediately rehired as a contractor because they need my skills. Now they have to pay me more than before and I get to work from home and use the saved commuting time on bootstrapping my startup. I'd never go back as an employee now. So it was a pretty inefficient cost cutting scheme on their part.
You might be surprised at the amount of money they save by not having you as an employee.
They save a few thousand a year on your desk; thousands on unemployment taxes in many states; SS and income tax contributions; healthcare benefits, stock awards, and bonus schemes; etc.
Regardless, it's not necessarily intended to be a pure cost-cutting scheme: switching you to being a contractor essentially improves their liquidity.
It's a little like someone with lots of cash getting a mortgage to buy a house: they could afford it, but they'd rather pay a little more over time to get additional flexibility.