===== git log ====
commit 07d8cc04c451f25961eaf5a8ad9ae767800eb2db
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Apr 24 10:01:30 2018 -0400

    doc: Added release notes for 4.0.2
    
    fixes: bz#1559547
    
    Change-Id: Iab5f0dee7c90c3906226b41eb2ce9ea191f495e0
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 92cc124298c068942ba049c2ccaa95b8c5b5294d
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#1570432
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit fa8e792ac3ee4b30768a3b4b1e303d8fb083eb7a
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/v4.0.2
