11–20 of 28 posts
This has nothing to do with the language and could just have easily been accomplished in any other language.
Also, then if I were you, I would try to keep my dev and personal computer more secure. I know that I am a freak that way. :)
- Did you delete db from your local computer? If not, do it now. - Inform your client about the problem and how you can fix it. - Fix it.
There are free utilities out there that delete securely. If you already deleted the file, which I think you posted is the case, there are also utilities that will overwrite the slack space on your drive, which will also make the file unrecoverable.
I agree with all the other responses in her (delete it, tell the client, etc). But, the fact you mention this is based on PHP - maybe you were trying to hint at the system, but it sounds like you are blaming the language. This has nothing to do with the language and could just have easily been accomplished in any other language.
I'll shift my blame to the developer for not completing their due diligence before writing software.
Obviously, just delete the file, tell your client exactly what happened and explain how you can help them secure their data better. Turn this accident into an opportunity. Why are these things always so hard? Why bring a lawyer (who will charge money fo his services) in own it?
This is an awfully embarrassing situation for the company he's working for. They could decide to cut their losses and turn him into the police, betting that public outrage will focus on the malevolent thief instead of on their innocent security mistakes.
Or, if they're more worried about their liability (possibly including liability for theft already committed by less scrupulous employees or consultants,) then one way to sweep it under the rug would be:
1. Produce a serious and viable legal threat against the poster.
2. Use the threat to make him sign an agreement never to speak another word about their credit card problem.
3. End his contract.
4. Go on with whatever they want to do (fix the problem, or not) with much greater confidence that this will never publicly surface and bite them in the ass.
That wouldn't be a catastrophic outcome for the poster, but even in that situation I'd rather have a lawyer advising me.
Obviously, just delete the file, tell your client exactly what happened and explain how you can help them secure their data better. Turn this accident into an opportunity. Why are these things always so hard? Why bring a lawyer (who will charge money fo his services) in own it?
They are hard because there is always risk that an "obvious" decision will create civil or criminal liability. A lawyer can help you assess and mitigate that risk.
Obviously, just delete the file, tell your client exactly what happened and explain how you can help them secure their data better. Turn this accident into an opportunity. Why are these things always so hard? Why bring a lawyer (who will charge money fo his services) in own it?
Obviously, just delete the file, tell your client exactly what happened and explain how you can help them secure their data better. Turn this accident into an opportunity. Why are these things always so hard? Why bring a lawyer (who will charge money fo his services) in own it?
Why are these things always so hard? Why bring a lawyer (who will charge money fo his services) in own it? This is an awfully embarrassing situation for the company he's working for. They could decide to cut their losses and turn him into the police, betting that public outrage will focus on the malevolent thief instead of on their innocent security mistakes. Or, if they're more worried about their liability (possibl…
Simply by posting this story, you may have opened yourself up to a lawsuit because an enterprising mind could follow your HN history and what you've posted here, put together enough clues, and find out the vulnerable system. They could hack it. No, you weren't directly responsible for it, but civil law is an entirely different beast than criminal law.
Is this a custom store or a package out there somewhere? The latter would be pretty scary. When I purchased a business I found a DB with all customers CC info in it while doing my due diligence (it was a crappy cart system written by some guy overseas). The seller was surprised they were there, but didn't seem to grasp the gravity of the situation ($150,000 fine for example). I had my purchase contract written to exp…
Thanks for the advice! It's a service - like shopify - but definitely NOT shopify :) I'm just starting out, in college, so lawyers aren't in the budget...