3 ms·

Wow a whole blog post on the presumption that not allowing some special characters means they are vulnerable to an sql injection attack. How about.. testing th

• mcantor 14y ago
  Who cares if they're not actually vulnerable? It's 2012. These password restrictions are arbitrary and anachronistic.
  • Jare 14y ago
    They are also the kind of policies that will make enterprisey minds feel safe and secure. Not worth reading too much into them.
• larrys 14y ago
  "a whole blog post on the presumption" There are always these blog posts that follow the same format: "this happened to me, it means this, let me post, discuss on HN, I'm doing this to warn others" I'm a little bothered in this particular post with the "private" email. Where is communication with a rep ever private and why should it be? You can disclose the exact email text w/o disclosing the rep name and email if you want. Many of these posts also share another thing in common. Nobody ever takes the time to even verify any of the info given. I'm certainly not claiming it's (entirely) made up. But everybody seems to assume for the sake of discussion that it is entirely correct as long as nobody is able to refute it on HN. I also never see most of the people that make these complaints ever raise their complaints to a higher level. Not that they have to. But why not spend $5 and send a certified postal letter to Lew Moorman of Rackspace and then at least you can show some verification that you tried real hard to correct the problem.