News for hackers. Stuff that matters.
Re:Equifax linked customers to my fake phishing version of t... by tyingq on Wednesday September 20, 2017 @01:07PM (#15296014)
Probably because they wanted to farm it out to some agency with zero dependencies on their known-incompetent internal IT team?

You're right of course, but I'm betting that was the motivation.

Re:Equifax linked customers to my fake phishing version of t... by panarky on Wednesday September 20, 2017 @02:05PM (#15296606)
They could always farm out the new site and point a subdomain to it.

Something like https://breach.equifax.com

Re:Equifax linked customers to my fake phishing version of t... by phamilton on Wednesday September 20, 2017 @04:29PM (#15297928)
That would require ssl certs to be shared to the agency.

Agreeing with everyone though, it's a wrong reason, but I can fathom why someone would do it.

Re:Equifax linked customers to my fake phishing version of t... by tonyztan on Wednesday September 20, 2017 @06:43PM (#15299031)
No, the outside agency can obtain a new cert for just that subdomain. They can even use letsencrypt! (Although they really should use EV for this type of site.)
Re:Equifax linked customers to my fake phishing version of t... by Kluny on Wednesday September 20, 2017 @01:21PM (#15296141)
You'd think even the world's most incompetent IT team could manage to point a subdomain at a remote server, but apparently not.
Re:Equifax linked customers to my fake phishing version of t... by tyingq on Wednesday September 20, 2017 @01:25PM (#15296172)
I have contracted places where that would be a very formal request with tons of meetings and approval flows across purchasing, it security, website ops, the design/branding team, etc. Weeks of lead time required.

Basically, the request signals all the little fiefdoms that it's their chance to weigh in.

Re:Equifax linked customers to my fake phishing version of t... by mdavidn on Wednesday September 20, 2017 @01:24PM (#15296162)
Not without sending every user's equifax.com cookies to that outside agency's servers.
Re:Equifax linked customers to my fake phishing version of t... by Kluny on Wednesday September 20, 2017 @01:27PM (#15296189)
Hmm, point. Of course, there are tons of ways to get around that problem.
Re:Equifax linked customers to my fake phishing version of t... by wutwutwutwut on Wednesday September 20, 2017 @04:15PM (#15297805)
Can you share the best?
Re:Equifax linked customers to my fake phishing version of t... by Kluny on Wednesday September 20, 2017 @08:56PM (#15299736)
The first one that comes to mind would be to invalidate all existing cookies so that the ones accessible to the other server aren't useful. I wouldn't call that the "best" since invalidating cookies can be annoying for users, but I'm sure there are other ways.
Re:Equifax linked customers to my fake phishing version of t... by wutwutwutwut on Thursday September 21, 2017 @09:20AM (#15303032)
If a user has a cookie for example.com (your domain) and type in vendor.example.com in the web browser how would you invalidate these cookies before they are sent to the vendor? Or even after they are sent? I struggle a bit with seeing how this could be done in a secure manner.
Re:Equifax linked customers to my fake phishing version of t... by Semaphor on Thursday September 21, 2017 @01:39AM (#15300836)
Never underestimate how incompetent people can be. When I was waiting for my South African Visa application to go through, I had to check the status at a scammy-looking url. The form would reload if you pressed enter and pressing tab after the ID field would set the focus to the logo above it instead to the password field below.
Re:Equifax linked customers to my fake phishing version of t... by mjcl on Wednesday September 20, 2017 @01:14PM (#15296072)
My guess was that they wanted to reduce the chance of news leaking before they announced it. If they're like other large companies I've seen from the inside, changes to the main website involve lots of meetings and lots of people/stakeholders.