We deleted the production database by accident

Re:We deleted the production database by accident by xtracto on Sunday October 18, 2020 @12:39PM (#24819084)

This. The person that erased the database in my case came forward to me as soon as we realized what had happened. At that moment I was very happy it was an "inside job", it meant I could discard hacking.

As its said before: he made a mistake. The error was allowing the prod database to to be port forwarded from a non prod environment. As head of eng that was MY error. So I owned to it and we changed policies.

[ Parent | on HN ]

Re:We deleted the production database by accident by cutemonster on Sunday October 18, 2020 @01:33PM (#24819565)

How do you prevent forwarding ports? Then one needs to disable ssh access?

Nice that you were a person he felt ok with sharing the mistake with, I suppose that's an important part of being head of eng.

[ Parent | on HN ]

Re:We deleted the production database by accident by fogihujy on Sunday October 18, 2020 @03:46PM (#24820516)

`AllowTcpForwarding No`

There are ways around it, of course, but it prevents the scenario described above.

[ Parent | on HN ]

Re:We deleted the production database by accident by cutemonster on Monday October 19, 2020 @02:02AM (#24823682)

Thanks

[ Parent | on HN ]

Re:We deleted the production database by accident by xtracto on Sunday October 18, 2020 @05:58PM (#24821456)

Nope . The solution is to password protect and not give the pass to developers. Or only give read only access.

[ Parent | on HN ]