LYC: tech geek stuff inside -- (edited)
Posted by
oblique (aka kkuphal)
Jul 18 '19, 13:52
|
We run a Barracuda Message Archiver which consumes all our email in the company for legal searches, etc. We also use Office 365 so the two talk.
Microsoft is ending support for TLS 1.0 and 1.1 in their email system soon and I keep getting alerts that our connector to our archiver isn't using TLS 1.2 despite being configured for it. I've kinda ignored this but the deadline is coming up so I decided to investigate.
I open a ticket with Barracuda just to have them check on it after confirming my end is set up right from what I can see. Their first response, is "Sure, TLS 1.2 is supported the box is supposed to negotiate up to it. Lemme take a quick look"
After I give them remote access, the email I got back now is "Um, yeah, we were totally wrong. The appliance is not auto-negotiating and we've reproduced this on our internal test units. Here's the bug number, we'll update you when it is fixed"
Seriously? What kind of shoddy internal testing do you have that you don't even realize that your product isn't negotiating TLS 1.2 in today's email world where pretty much everything is forcing that down on you? Now I want to know if they have a bug finding bounty program :)
I can't believe that I'm the first customer that reported this either.
EDIT: lol. They just replied now that they have a patch they are going to apply and retest. Have to at least give them credit for being fast :)
|
Responses:
|