===== git log ====
commit c420ef1251b6958c9602e5c8a47c7b614daedf24
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Apr 24 09:43:34 2018 -0400

    doc: Added release notes for 3.10.12
    
    fixes: bz#1553989
    
    Change-Id: Iae1aa9ba71d1425a7797a84c937f2c4e760a4816
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 420577300f1f8f28e5c4784f291f2c14e7311fb1
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Apr 2 12:20:47 2018 +0530

    server/auth: add option for strict authentication
    
    When this option is enabled, we will check for a matching
    username and password, if not found then the connection will
    be rejected. This also does a checksum validation of volfile
    
    The option is invalid when SSL/TLS is in use, at which point
    the SSL/TLS certificate user name is used to validate and
    hence authorize the right user. This expects TLS allow rules
    to be setup correctly rather than the default *.
    
    This option is not settable, as a result this cannot be enabled
    for volumes using the CLI. This is used with the shared storage
    volume, to restrict access to the same in non-SSL/TLS environments
    to the gluster peers only.
    
    Tested:
      ./tests/bugs/protocol/bug-1321578.t
      ./tests/features/ssl-authz.t
      - Ran tests on volumes with and without strict auth
        checking (as brick vol file needed to be edited to test,
        or rather to enable the option)
      - Ran tests on volumes to ensure existing mounts are
        disconnected when we enable strict checking
    
    Change-Id: I2ac4f0cfa5b59cc789cc5a265358389b04556b59
    fixes: bz#1570428
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 961883e065f80125e5db648e7c214677b2390736
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Mar 26 20:27:34 2018 +0530


More commit messages for this ChangeLog can be found at
https://forge.gluster.org/glusterfs-core/glusterfs/commits/v3.10.12
