Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ofarchades

  • Rank
  1. I'm guessing the reCAPTCHA code should come before the mail is sent - and that you need to check the result to make sure it validated before sending the email. As for the error, there could be so many reasons. Maybe your server is configured to not allow URLs to be passed to file_get_contents? Maybe $_POST["g-recaptcha-response"] isn't set (did you add it to your form?). Maybe there's some reason file_get_contents is taking too long to load the URL (bad connection to the server, the server is blocking the request, etc) and the script is timing out? That last one will be easy to rule out depending on whether you get the error quickly or if the page loads for ~30 seconds or so.
  2. His proposed schema would not be scalable, but it's by no means "incorrect" or broken. In any case, in the previous two replies we already discussed the addition of a pivot table as you subsequently suggested in your post.
  3. I could be wrong, but I think you need to change if (($username == $db_username) && (password_verify($db_password, $hash))) { to if (($username == $db_username) && (password_verify($password, $db_password))) { Where $password is the plain text password as posted from the login form - and $db_password is the hash stored in the database.
  4. More RAM would be redundant because any decent text editor/searcher(?) will load the file in chunks. Glad you found one that does so. Out of pure curiosity, what are these files that are so large? Especially source code files. That seems unusual.
  5. I've only skimmed the code as I'm exhausted and about to go to bed, but is it possible that the code which updates the quantity comes after the code where the quantity is displayed? Try moving the update logic to the top of the script.
  6. The comparison is weird because it evaluates as true despite the hashes being different. This actually works for any string beginning with "0e" due to the fact that PHP will convert them to 0 internally. There's also the fact that the integer 0 will return true when compared to most* strings (e.g. 'test' == 0) because PHP turns this into an integer comparison and typecasts the string to an integer (which results in 0). * I say "most" strings because some strings will be typecast to different ints e.g. '2test' would become 2 and therefore '2test' == 2. I'll use == myself in cases where security isn't a concern or I can be certain of what the values can and can't be, but otherwise it's probably better to just not gamble with PHP's bizarre internal magic.
  7. You're right about the foreach - and as I mentioned in my reply, he shouldn't be doing any sort of string comparison between two hashes. However, you can never trust PHP's == string comparison to work as you'd expect; there are plenty of documented cases where it will return crazy results (such as the famous "md5('240610708') == md5('QNKCDZO')" scenario).
  8. Are you sure? I can't see any obvious reason why it would do that. Would you be able to post all of the code for that file, in case there's a problem elsewhere? Other than that, I have a couple of advisory notes regarding how you've approached password hashing. 1) Your salt isn't very strong. Check the PHP documentation on how to create a bcrypt salt, for example. 2) "$cryptPass === $db_password" is vulnerable to a timing attack. If you're able, it may be better to check out the password_hash and password_verify functions added in PHP 5.5. Otherwise, strengthen the salt and look for a time-constant method of comparing the hashes (e.g. hash_equals).
  9. You probably won't have much of a career if you refuse to change with the times. Of course it's important to know the difference between trends that are practical and those that are just fashionable and corrosive, but frameworks and CMS and code reuse are all pretty important if you want to be an effective programmer. Laravel has definitely become quite bloated, but you don't need to use the whole framework; you can pick and choose which components you want to use in your project, much like Symfony. There's even now a Laravel-based microframework called Lumen. Maybe give it a try.
  10. Using military time is a nice idea. You could have a pivot table linking the users to their groups instead of having the group_id column on the user table. It might look like: pkid (unsigned int, primary key, auto increment), user_id (unsigned int), group_id (unsigned int) Index user_id and/or group_id depending on what sort of lookups you'll be doing. So far this is a fairly standard relational database design. The idea of these databases is to link related information. As long as you don't make any crazy mistakes with the queries, it should be fine.
  11. I just tested it. Like I said, change if (file_get_contents($site_a) !== FALSE) $image = $site_a; else if (file_get_contents($site_b) !== FALSE) $image = $site_b; to if (@file_get_contents($site_a) !== FALSE) $image = $site_a; else if (@file_get_contents($site_b) !== FALSE) $image = $site_b; and it works. Also the code I posted earlier would have worked, but it was missing an opening brace that I wasn't able to see because I wrote it in this site's edit box. You should have easily seen it in your code editor, though. You are using a code editor... aren't you? Anyway, as mentioned before, you don't really want to call both file_get_contents and imagecreatefrompng because that means the image will be downloaded twice from the remote server. Instead, try: <?php //// BEGIN CONSTANTS //// // coordinates for the skin's face $face_x = 8; $face_y = 8; $face_width = 8; $face_height = 8; // coordinates for the skin's "mask", i.e. the layer that is overlaid // on top of the face $mask_x = 40; $mask_y = 8; $mask_width = 8; $mask_height = 8; // size of the output image $avatar_width = 96; $avatar_height = 96; // The default skin. All hail Steve! $default_skin_url = 'http://halcyon-pvp.fr/dl/img/char.png'; //// END CONSTANTS //// if (isset($_GET['user'])) { $user = $_GET['user']; $skin = @imagecreatefrompng("http://halcyon-pvp.fr/skins/$user.png"); if (!$skin) { $skin = @imagecreatefrompng("http://skins.minecraft.net/MinecraftSkins/$user.png"); } } if (!isset($skin) || !$skin) { // If skin could not be retrieved, display Steve $skin = imagecreatefrompng($default_skin_url); } // Set up a blank image to write to $avatar = imagecreatetruecolor($avatar_width, $avatar_height); // Resize and overlay the face region, as defined by the constants above imagecopyresized($avatar, $skin, 0, 0, $face_x, $face_y, $avatar_width, $avatar_height, $face_width, $face_height); // Resize and overlay the mask region imagecopyresized($avatar, $skin, 0, 0, $mask_x, $mask_y, $avatar_width, $avatar_height, $mask_width, $mask_height); // Finally, return the processed image as a png header('Content-Type: image/png'); imagepng($avatar); imagedestroy($avatar); ?> Alternatively, you could keep the existing file_get_contents code, but save the result to a variable and pass it to imagecreatefromstring. The only problem with that is that imagecreatefromstring uses more memory.
  12. If you're able to install it on your server, I find wkhtmltopdf to be a good solution.
  13. Would you be able to post all the code you currently have? I can't see any reason why the code we've posted here wouldn't work; there has to be something else going on.
  14. Ideally once we've established what he's trying to achieve, we'd want to get him to change it so that the image doesn't need to be downloaded twice (once for the file_get_contents/whatever and then again for the imagecreatefrompng) i.e. store the result in a variable and pass it to imagecreatefromstring. At this stage, I fear that may just cause more confusion than there is already.
  15. What do you mean by this? With the other code, the warning is being thrown by the first file_get_contents not finding the file. Try adding @ before the function calls, I guess.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.