10 ms·
This is just GCHQ's way of saying that they already know how to reverse bcrypt. On a more serious note http://www.gchq-careers.co.uk http://www.gchq-careers.co
by jgrahamc 14y ago
This is just GCHQ's way of saying that they already know how to reverse bcrypt.
On a more serious note http://www.gchq-careers.co.uk http://www.gchq-careers.co.uk does not appear to be run by GCHQ. The Terms page says that it's run by TMP Worldwide (http://www.gchq-careers.co.uk/terms-and-conditions/ http://www.gchq-careers.co.uk/terms-and-conditions/).
- scoot 14y agoThat doesn't make it any less egregious. GCHQ (of all organisations!) have failed to carry out even a minimum standard of due diligence in selecting a supplier that handles sensitive personal information of prospective employees.
- Ntrails 14y agoThe real question is why anyone would sign up to such things using a "real" password. I've lost count of the number of jobsites and so on that I registered for with a random string knowing that a) Firefox would remember it and b) On the off chance it doesn't, and I get through to a stage where I ever need the password I can just recover/reset Signing up for websites that have limited/no repeat value is part of everyday life and I don't have high expectations of them
- jiggy2011 14y agoThey have finite resources so there is an opportunity cost to everything. More time auditing their public website means less time auditing military systems etc.
- jiggy2011 14y agoMaybe it's on purpose and it's question #1 of the interview, "what did you think of our recruitment website?"
- acdha 14y ago“We took the liberty of trying your email and password on some popular websites and have rejected your application”
- keithpeter 14y ago"This is just GCHQ's way of saying that they already know how to reverse bcrypt." That comment made my morning. Surely this is a case of http://xkcd.com/932/ http://xkcd.com/932/ Embarrassing but surely those nice people in Cheltenham are about more serious work.
- deleted 14y ago[deleted]
- redmattred 14y agoThis is a microsite run by TMP. Since most Applicant Tracking Systems (the software used to list/fill jobs) do not list jobs in an SEO friendly way, companies like Jobs2Web, Optijob, and TMP built microsite products like the one being used here by the GCHQ. TMP is an ad agency, not a technology company - can't say I'm too surprised they missed the ball on this one. There are lots of US gov't agencies who use TMP also.
- blhack 14y agoBecause you mentioned bcrypt, it might be a good time for everybody to read this: http://yorickpeterse.com/articles/use-bcrypt-fool/ http://yorickpeterse.com/articles/use-bcrypt-fool/ (sidenote: GCHQ cannot reverse bcrypt. Jgrahamc was making a joke.)
- tryeng 14y agoThat's not a good article to make people read. I find it strange that it doesn't mention lack of salting among the most common mistakes. Also, I didn't think SHA1 broken in any way that makes breaking password hashes easier than e.g. the SHA2 family? I might be wrong, though. PS: I'm not advocating using anything other than a good PBKDF for hashing passwords.) Edit: Re-reading the article it seems like lots of BS in there: Example 1, regarding hashing something several times: "In order to retrieve the original password a hacker has to crack multiple hashes instead of only one." Nah, guessing is only more time-consuming. Example 2, regarding the same thing: "The first reason is pretty easy to bust: simply add more hardware (or better hardware) and you're good to go." This applies for bcrypt as well. And for his "attack" on "Hashing a password N times in the form of hash( hash(password) ) * N" you would need a working preimage attack for the hashing function used. EditN: Rewrite
- jiggy2011 14y agoBcrypt has a tuneable "cost function", so you get to decide how hard to make it. It's effectively designed to be slow and hard to do in parallel. The SHA family on the other hand are designed to be fast, (for checksums etc) so it's possible that later SHA algorithms are actually worse than earlier ones for password hashing. Modern computers can do a lot of MD5/SHA1 every second so even with a salt, one round of SHA1 is likely to be not very good at all. You can probably find a significantly large X and do SHA1 enough times to make it slow enough today, but for future-proofing you are better off just using an algorithm that is actually designed for such purposes.
- tryeng 14y agoI'm not saying that that bcrypt isn't a better choice, it is, but some of the "flaws" he is pointing out in that article are just ridiculous. If he's going to argue for something, he should be using correct arguments.