84
Linux
10d

This fucking customer...
I've told that person so many times that they need to FIX THEIR CODE, because it get's pwned all the time.
To make stuff worse - they are still using Debian 5, and we are unable to upgrade because all their shit will break.

I found his fix today - he installed an old version of NGINX because it is "better".

No fuck you.

Comments
  • 23
    You better isolate that server from your network cuz I'm sure it's full of security holes thanks to them
  • 19
    Mate, that’s a shitty thing to have to cope with.

    That brain numbing dense attitude gets very tiresome.

    One of our clients hasn’t upgraded a critical machine on the network from win7 yet.

    We’ve brought it up and we’re told that “it’s not very high priority as it’s old”. That is very flawed logic.
  • 11
    @oudalally

    The most frustrating part is that the customer BLAMES ME PERSONALLY for not having a good security on any of our systems. Only because their site gets killed once every month.
  • 10
    @Linux How senior is the client? In cases like that, I go straight to the highest ranking member I can.

    In some cases (whenever possible in fact), I open up a line of communication to the CEO.

    Put a document together outlining each security risk, email it to every senior member of the team you deal with (make sure to CC them, they must know who it's been sent to), and put the subject as something like "Urgent Resolution of critical security issues in the core system".

    It doesn't mean much, but you get some middle managers looking at it, they will kick up the fuss for you.
  • 8
    @Linux The other one you need to do in a case like that is to make sure any replies sent just to you are also CC'd to the rest of them when you reply to their response.

    The paper trail needs to be large, wide, and unstoppable - essentially like the Mississippi river.

    If they're blaming you, they're making this your responsibility. So take the responsibility, and throw it back at them.

    A few feathers will be ruffled, but only of the incompetent people who are passing the buck.

    If they try to add more responsibility to you for fixing it, reply with "Certainly, we can fix it for you. I'll draw up a quote for the work involved and if you're happy to do that, we'll proceed.".

    Worst case scenario, they stop blaming you. Best case scenario, you take the problem out of their hands, fix it properly, and get paid for it.
  • 7
    @oudalally

    The problem is, that this dude is the senior in that company.

    They just wont fix it, because it costs money and time.

    I started talking to them about this issue over two years ago, and despite several outages and much downtime - the wont bother.

    This rant is about same customer:

    https://devrant.com/rants/1437397/...
  • 1
    @Linux seems like he's WAAAAY older than a senior. Must be a lumping humping dinosaur. 😂
  • 5
    @oudalally Come now, everyone knows the only “good” version of Windows ever produced was XP Pro SP2...
  • 3
    @Kaji Hahahah. Yeah, true, but it took a good 6 years of patches before they got it right!
  • 1
    sounds awesome! such fun, much exploit, very wow
  • 5
    I'd just end up closing that customer's servers to be honest. Call it something like "willful damage conducted to our IP range's reputation in RBL" or similar. Spam mail would probably qualify for that and you probably don't want to get your IP's tainted like that anyway. And if customer's server getting downed by the hoster makes them wake up and fix it, double win :3
Your Job Suck?
Get a Better Job
Add Comment