Differences between revisions 2 and 28 (spanning 26 versions)
Revision 2 as of 2017-12-24 16:50:20
Size: 843
Comment:
Revision 28 as of 2017-12-24 18:02:06
Size: 899
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
The default GlusterFS setup does not encrypt its communication. Use the method below enable encryption.
Line 3: Line 4:
== Servers ==

Once all this works we will continue by adding TLS encryption to the setup.

=== Keys ===
On each of the Glusterfs servers run.
== Keys and Certificates ==
Make an encryption key and make sure to set the `CN` to match the name of the host. Repeat this on the client and on each of the servers.
Line 10: Line 7:
mkdir /etc/ssl/glusterfs
cd /etc/ssl/glusterfs
cd /etc/ssl
Line 13: Line 9:
openssl req -new -x509 -key glusterfs.key -subj "/CN=gluster01" -out glusterfs.pem
Line 15: Line 12:
=== Certificates ===
Now sign a certificate using that key.
== Certificate Authorities ==
Compile all the certificates in one place and concatenate them into two files. `glusterfs.ca` and `glusterfs-client.ca`.
Line 18: Line 15:
root@gluster01:/etc/ssl/glusterfs# openssl req -new -x509 -key glusterfs.key -subj "/CN=gluster01" -out glusterfs.pem
root@gluster02:/etc/ssl/glusterfs# openssl req -new -x509 -key glusterfs.key -subj "/CN=gluster02" -out glusterfs.pem
root@gluster03:/etc/ssl/glusterfs# openssl req -new -x509 -key glusterfs.key -subj "/CN=gluster03" -out glusterfs.pem
root@gluster04:/etc/ssl/glusterfs# openssl req -new -x509 -key glusterfs.key -subj "/CN=gluster04" -out glusterfs.pem
cat gluster01.pem gluster02.pem gluster03.pem gluster04.pem glusterclient01.pem > glusterfs.ca
cat gluster01.pem gluster02.pem gluster03.pem gluster04.pem > glusterfs-client.ca
Line 23: Line 18:

== Clients ==
Copy `glusterfs.ca` to `/etc/ssl` on all servers. Copy `glusterfs-client.ca` to `/etc/ssl` on the client.

GlusterFS Encryption

The default GlusterFS setup does not encrypt its communication. Use the method below enable encryption.

Keys and Certificates

Make an encryption key and make sure to set the CN to match the name of the host. Repeat this on the client and on each of the servers.

cd /etc/ssl
openssl genrsa -out glusterfs.key 2048
openssl req -new -x509 -key glusterfs.key -subj "/CN=gluster01" -out glusterfs.pem

Certificate Authorities

Compile all the certificates in one place and concatenate them into two files. glusterfs.ca and glusterfs-client.ca.

cat gluster01.pem gluster02.pem gluster03.pem gluster04.pem glusterclient01.pem > glusterfs.ca
cat gluster01.pem gluster02.pem gluster03.pem gluster04.pem > glusterfs-client.ca

Copy glusterfs.ca to /etc/ssl on all servers. Copy glusterfs-client.ca to /etc/ssl on the client.

None: GlusterFS Encryption (last edited 2021-03-26 21:25:57 by Kristian Kallenberg)