PFS / Letsencrypt for Postfix/Dovecot/PureFTPd/mariadb

Discussion in 'Tips/Tricks/Mods' started by, Oct 5, 2017.

  1. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Note that ssl=on will force ssl for mysql connections, which is very useful for multi-server installs to implement ssl to the master server, but it will break any multi-server installs unless you're running the latest 3.1dev, which added back support for mysql connection flags. I believe, though as yet untested, that requires adding these settings to
    # uncomment if local mysql db uses ssl (If so, use '', not 'localhost')
    # $conf['db_client_flags'] = MYSQL_CLIENT_SSL;
    $conf['dbmaster_client_flags']  = MYSQL_CLIENT_SSL;
    That should be done on all slave servers (the settings are also in files, though I don't know if changes persist through updates, so is safer.)

    I was actually just working on a tutorial that includes this very configuration setup, and should have the above tested/verified pretty soon.
    Last edited: Aug 2, 2018
    ahrasis and like this.
  2. ISPConfig Developer ISPConfig Developer

    hmm so what do I miss?
    old php 5.6 mysql_connect works from localhost using ssl=on
    shouldnt have any special client settings. Or does it actually force the rusty php extension to use tls 1.2?
  3. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    I'll need to test it again to refresh my memory, but I tried using letsencrypt certificates with mysql some time ago and found everything worked or could be configured to work except the php connections from slave servers. Maybe it wasn't "ssl=on" that made it required, but something did ( sounds like it should be 'require_secure_transport', though I don't remember setting that). If you don't see it as required, maybe it's just a difference in mariadb versions? (I was probably on debian 8 when I set that up originally.)
  4. ISPConfig Developer ISPConfig Developer

    I never had any issue with the connection needed to be ssl when the server supported it. Must've been too much coffee and too few sleep issue maybe?
    I have used ssl using mysql 5.<dontremember> or something but granted the current version I setup was maria 10.3
  5. ISPConfig Developer ISPConfig Developer

    moved to post #1
    Last edited: Jul 20, 2018
    ahrasis likes this.
  6. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    you might include:
    openssl dhparam -out /var/lib/dovecot/ssl-parameters.tmp 2048 && \
            mv /var/lib/dovecot/ssl-parameters.tmp /var/lib/dovecot/ssl-parameters.dat
    Last edited: Jul 27, 2018
  7. ISPConfig Developer ISPConfig Developer

    and most of the stuff should be done on file changes like / / dovecot.conf ... hmm lots of stuff to post together.
    I prefer ssl_dh_parameters_length ssl_dh for dovecot

    edit: what do you know xD I forgot to specify the dh file omg thank you ... will fix it asap
  8. ISPConfig Developer ISPConfig Developer

    ah I see, debian 9 doesn't have ssl_dh yet...
    edit: I don't trust what the ssl-params thing does with my copied dh-file, so I stay with setting the keysize in dovecot config and...
    rm /var/lib/dovecot/ssl-parameters.dat
    restart dovecot
    some service issue while generating the key... I can live with that.
    Last edited: Jul 20, 2018
  9. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    I've been working on/testing ssl in mariadb on debian 9, and found the following as of right now:
    • as relates to my previous comments, I think my memory was off, and I did not have ssl required, but rather I wanted to make it required and could not because slave server connections wouldn't work with ssl
    • if you need ssl for slave server connections (a good idea if you have them), it should work in git master branch right now, but does not in 3.1.12 nor in git stable-3.1 branch; there is a merge request to correct that, so hopefully will be available soon
    • ssl=on should not be needed, that's the default when you specify certificates
    • you cannot use ssl-cipher=TLSv1.2 on mariadb 10.1.26 which comes with debian 9 as it's linked to YaSSL, not OpenSSL; likely when you recompiled 10.3 it linked with openssl, which is why it worked for you,
    • 'require_secure_transport' (mentioned above) appears to be mysql-only, in mariadb you must update the mysql.users table to require ssl
    • my above notes about the settings for are accurate, and found the settings will not be preserved in through an ispconfig update currently, though there's a WIP merge request that should fix that soon
    • note that db_client_flags (in is for the connection to the local server and dbmaster_client_flags is for the connection to the master (so eg. on my test setup I had mysql ssl on the master but not the slave dns servers, so I left $conf['db_client_flags'] = 0; but set $conf['dbmaster_client_flags'] = MYSQL_CLIENT_SSL; so those connections used ssl)
    Last edited: Jul 26, 2018
    ahrasis and like this.
  10. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    I already confirmed this when suggested it in my thread's post. So we should be good with this part left out.
    Last edited: Aug 13, 2018
  11. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    This is inaccurate, and I corrected it in my above comment - that setting works with OpenSSL, but not with YaSSL. The version difference I confused that with was in how you make ssl required for users; starting in mariadb 10.2.0 you can use create/alter/grant to make it easy (eg. ALTER USER foo REQUIRE SSL), where in 10.1.26 I had to edit mysql.users directly.
    ahrasis likes this.
  12. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    And just a little more info I found for ssl on mysql connections:
    • on one system MYSQL_CLIENT_SSL was not defined, I had to use MYSQLI_CLIENT_SSL instead, which is probably more correct anyways
    • at least on the mariadb I'm using, you can't use SSL on a unix socket connection so if you set $conf['db_client_flags'] you must change the db)host from localhost to '' (and I don't recommend ssl over tcp, just use the unix socket...)
    • do NOT set $conf['db_client_flags']=MYSQLI_CLIENT_SSL in /usr/local/ispconfig/interface/lib/ on the master, as it's not supported in "interface" currently, only in "server" (I removed that instruction from my above comment)

Share This Page