3 ms·
> Nice job, holding franchisees responsible. Dickey's won't have to answer for the actual breach because the franchisees also had poor security. I think this i
by hn_throwaway_99 6y ago
> Nice job, holding franchisees responsible. Dickey's won't have to answer for the actual breach because the franchisees also had poor security.
I think this is blaming the wrong people. I mean, do we really think some small fry BBQ restaurant franchisee can do adequate IT security now?
The issue is that credit card numbers are fundamentally insecure. We must move financial systems to a signed transactions model where private keys only live on secure hardware modules. This idea that we can have credit card numbers floating between consumers and merchants and payment processors and banks is nonsense.
- minitoar 6y agoHow does automatic bill pay work in this system?
- hn_throwaway_99 6y agoIn that case, you wouldn't sign a single transaction, you would sign a subscription plan, e.g. "I authorize merchant X to debit my account Y dollars every month."
- JoshTriplett 6y agoOr even "I authorize merchant X to debit up to Y dollars once per month", for bills that can vary.
- treeman79 6y agoI was shocked to find out that canceling a card isn’t enough. a merchant can obtain the new card info directly from bank. I had to cancel my bank account to stop payments.
- eganist 6y ago> do we really think some small fry BBQ restaurant franchisee can do adequate IT security now? They can certainly follow instructions from their payment processor.
- jessaustin 6y agoIn this case, they would have had to buy new, chip-compatible card readers. In that case the breach wouldn't have produced anything usable. Security costs money. If not now, then later. However, it seems that Dickey's corporate must also be to blame. Lots of small businesses in USA have old swipe-style readers, but rarely are they lumped together in a single giant hack like this.
- MeinBlutIstBlau 6y agoSomething something the cost of doing business.