Thread Info
  • Locked Locked
  • Replies 51 replies
  • Subscribers 25 subscribers
  • Views 78133 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Version 9.508 - report on experience

Alexander Busch

Version 9.508 is released:

https://community.sophos.com/products/unified-threat-management/b/utm-blog/posts/utm-up2date-9-508-released

Maybe we could collect some reports about problems or hopefully no problems. Maybe please tell us about the modules (Network, Web, WAF, Mail, WLAN..) you use if you successful updated to 9.508.

Best
Alex

P.S. With the production system, I'll wait a little bit ;-)



This thread was automatically locked due to age.
Parents

  • Really strange...

    I've also problems with email encryption.

    I'm using official S/MIME certificates since the 9.5MR8 I'm affected of KB131727

    • If I'm sending signed Mails via UTM 2 Office365 I'll getting a "certificate not valide" inside outlook.
    • If I'm sending encrypted Mails via UTM 2 Office365 I'm unable to decrypt the message inside outlook.

    But now the interesting thing...

    • If I'm sending signed and / or encrypted Mails via UTM 2 UTM (Both v9.5MR8 -> thanks Bob 4 testing and help) everything seems fine!

    According 2 KB131727 I've opened a support call @ my RootCA and the answer was really unsatisfied...

    Das Sophos Gateway hat uns da ausgeschlossen und ist aktuell mit den S/MIME Zertifikaten nicht mehr kompatibel. Wir als CA werden im Moment unsere Infrastruktur nicht derart umwerfen, da die Nutzung des Sophos Gateways zu gering auftaucht.
     
    Eventuell kann die Bundesdruckerei oder D-Trust Ihrem Kunden da helfen. Was das bereits bestehende Zertifikat angeht sehe ich die Schuld bei Sophos, da keine Kompatibilität mehr zu bieten.

    Quick translation:

    Sophos ist the bad guy. We are not willing 2 rebuild our CA infrastructure because there are not enough customers using Sophos UTM.

    Use another CA!

     

     

    Nope, I'm not using any kind of Comodo cheap CAs I'm using one of the better expensive once...

     

    ...Sophos are U kidding? 

    I'm not willig 2 accept that my customers won't be able 2 encrypt there Mails because the recipients won't be able 2 decrypt them. U tolled us this special S/MIME encryption isn't secure enough but in my opinion it's better than without encryption.

Reply

  • Really strange...

    I've also problems with email encryption.

    I'm using official S/MIME certificates since the 9.5MR8 I'm affected of KB131727

    • If I'm sending signed Mails via UTM 2 Office365 I'll getting a "certificate not valide" inside outlook.
    • If I'm sending encrypted Mails via UTM 2 Office365 I'm unable to decrypt the message inside outlook.

    But now the interesting thing...

    • If I'm sending signed and / or encrypted Mails via UTM 2 UTM (Both v9.5MR8 -> thanks Bob 4 testing and help) everything seems fine!

    According 2 KB131727 I've opened a support call @ my RootCA and the answer was really unsatisfied...

    Das Sophos Gateway hat uns da ausgeschlossen und ist aktuell mit den S/MIME Zertifikaten nicht mehr kompatibel. Wir als CA werden im Moment unsere Infrastruktur nicht derart umwerfen, da die Nutzung des Sophos Gateways zu gering auftaucht.
     
    Eventuell kann die Bundesdruckerei oder D-Trust Ihrem Kunden da helfen. Was das bereits bestehende Zertifikat angeht sehe ich die Schuld bei Sophos, da keine Kompatibilität mehr zu bieten.

    Quick translation:

    Sophos ist the bad guy. We are not willing 2 rebuild our CA infrastructure because there are not enough customers using Sophos UTM.

    Use another CA!

     

     

    Nope, I'm not using any kind of Comodo cheap CAs I'm using one of the better expensive once...

     

    ...Sophos are U kidding? 

    I'm not willig 2 accept that my customers won't be able 2 encrypt there Mails because the recipients won't be able 2 decrypt them. U tolled us this special S/MIME encryption isn't secure enough but in my opinion it's better than without encryption.

Children
No Data
Unfiltered HTML