LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » MailMarshal (SEG) » HOWTO: Configuring SSL Options for "unsafe legacy...

HOWTO: Configuring SSL Options for "unsafe legacy renegotiation"

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • MailMarshal 10.1 and above
  • Advanced SSL options for Sender TLS
  • Allowing "Unsafe Legacy Renegotiation" for TLS

Question:

  • How do I allow "unsafe legacy renegotiation" for Sender TLS?
  • Need to negotiate TLS with legacy servers 

Background:

Some older email servers still use TLS renegotiation methods that have been deprecated for many years. Current MailMarshal versions (10.0.7 and above) disallow these methods by default.

Procedure:

To allow "unsafe legacy renegotiation":

  1. In the MailMarshal 10.1 Management Console, navigate to Configuration > Advanced Settings.
  2. Add the following setting as required:
    • Sender.SSLContextOptions (Integer)
      • Value: 262148
  3. Apply configuration, and then restart the MailMarshal Sender service on each processing server.

Upgrade from 10.0.7 to later versions

Some customers applied a Sender hotfix to release 10.0.7 for "unsafe legacy renegotiation". These customers must still apply the Advanced Setting to maintain the behavior in any later version.
  • To ensure continuity, customers can create the Advanced Setting in 10.0.7 before upgrading. It is not necessary to restart the Sender. The Advanced Setting will take effect immediately on upgrade.

Notes:

The setting takes a generic integer value to allow for any future requirements. However, only values specifically provided by Trustwave are supported. 

To contact Trustwave about this article or to request support:

Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster.


Execution: 0.031. 9 queries. Compression Disabled.
Powered by InstantKB.NET