Proxmox Mail Gateway Cipher Suite

Discussion in 'Mail Gateway: Installation and configuration' started by V.E.L, Sep 26, 2018.

  1. V.E.L

    V.E.L New Member

    Joined:
    Sep 26, 2018
    Messages:
    1
    Likes Received:
    0
    Hello,

    How do I modify cipher suite for proxmox mail gateway?

    In zimbra I always did this:

    zmprov mcf zimbraMtaSmtpdTlsExcludeCiphers 'aNULL,MD5,DES,TLS_ECDH_anon_WITH_AES_256_CBC_SHA'
     
  2. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,399
    Likes Received:
    132
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. A2IT

    A2IT New Member

    Joined:
    Jul 15, 2019
    Messages:
    2
    Likes Received:
    0
    Hello,

    We are currently setting up a pmg cluster and are trying to meet all the requirements of en.internet.nl

    Technical details:
    Mail server (MX) First found insecure cipher suite
    XXX.XXX.XXX. ADH-AES256-GCM-SHA384
    XXX.XXX.XXX. ADH-AES256-GCM-SHA384

    pmg still uses unsafe chipher, I changed this a few times in main.cf, but this is overwritten every time by the system to the default.
    Does anyone know how to put the chipher on high security?

    Thank you in advance :)
     
  4. sb-jw

    sb-jw Active Member

    Joined:
    Jan 23, 2018
    Messages:
    551
    Likes Received:
    49
  5. heutger

    heutger Active Member

    Joined:
    Apr 25, 2018
    Messages:
    643
    Likes Received:
    159
    I believe, he is also looking for something like this: #132

    Oh, and a) you should read the post with all information in it, b) you should use some more informal tests like hardenize.com or ssllabs.com (last only for websites), c) you should also consider (as well only for websites) observatory.mozilla.org and gtmetrix.com, e.g. DNSSEC is broken by design (as well) but more worse, it's also an threat vector as DNSSEC could be misused to multiple DNS DDoS amplitudes. DANE the same, broken by design and depends on DNSSEC. BREACH attack stated for my website shouldn't work as I have HSTS enabled and be on the preload list, IPv6 for mail server is currently no good idea, as there is less protection against spam with IPv6. I play around also with other broken by design techniques like SPF, DKIM and DMARC on my private test setup, so that are the results currently.
     
    #5 heutger, Jul 19, 2019
    Last edited: Jul 19, 2019
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice