The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
The easiest way is to use the binary keyword in your query use:
ReplyDeleteSELECT /*fields*/ FROM table WHERE /* where clause */ BINARY password = "userpassword"
OR
use the strcmp in your PHP code:
You can use this also if you store hashed or encrypted password which I recommend.
I guess you are storing passwords in clear. That's not only pretty insecure, it's also unnecessary in most situations. My advice is to store passwords in two columns, e.g.:
ReplyDeletepassword_salt VARCHAR(16)
password_hash VARCHAR(40)
Before storing a new password, take the password provided by the user ($clear_password), create a random string ($salt) and use both to create a hash (sha1sum($salt . $clear_password). Store both the salt and the hash and discard the clear password.
To validate a password, retrieve the stored salt for the given user, generate the hash and see if it matches with the hash in DB.
This technique is called salted passwords.