Differences between revisions 7 and 35 (spanning 28 versions)
Revision 7 as of 2017-12-24 17:05:27
Size: 892
Comment:
Revision 35 as of 2017-12-24 20:34:55
Size: 1529
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
== Keys == The default GlusterFS setup does not encrypt its communication. Use the method below enable encryption.
Line 5: Line 5:
On each of the Glusterfs servers and clients run. == Keys and Certificates ==
Make an encryption key and make sure to set the `CN` to match the name of the client/server. Repeat this on all the servers and the client.

=== Server ===
Line 7: Line 10:
mkdir /etc/ssl/glusterfs
cd /etc/ssl/glusterfs
cd /etc/ssl
Line 10: Line 12:
}}}

== Certificates ==
Now sign certificates using those keys. Replace the `CN` so it matches the host you are siging the certificate for.
{{{
Line 18: Line 15:
== Compile == === Client ===
{{{
cd /etc/ssl
openssl genrsa -out glusterfs.key 2048
openssl req -new -x509 -key glusterfs.key -subj "/CN=glusterclient01" -out glusterfs.pem
}}}
Line 20: Line 22:
Compile all the certificates into one large file == Certificate Authorities ==

Compile all the certificates in one place and concatenate them into `/etc/ssl/glusterfs.ca`. Notice that this will also include the certificates from the client.
Line 22: Line 26:
scp gluster01:/etc/ssl/glusterfs/gluster.pem gluster01.pem
scp gluster02:/etc/ssl/glusterfs/gluster.pem gluster02.pem
scp gluster03:/etc/ssl/glusterfs/gluster.pem gluster03.pem
scp gluster04:/etc/ssl/glusterfs/gluster.pem gluster04.pem
scp glusterclient01:/etc/ssl/glusterfs/gluster.pem glusterclient01.pem
cat gluster01.pem gluster02.pem gluster03.pem gluster04.pem > glusterfs.ca
cat gluster01.pem gluster02.pem gluster03.pem gluster04.pem glusterclient01.pem > glusterfs.ca
Line 29: Line 28:

Copy the certificate authority to all the servers and place it in `/etc/ssl/glusterfs.ca`

== Activate Encryption ==
When this file exists the glusterfs server will use the new certificates
{{{
touch /var/lib/glusterd/secure-access
}}}

== Enable Encryption ==
On one of the servers encryption is enabled
{{{
gluster volume set www client.ssl on
gluster volume set www server.ssl on
}}}

== Allow Only Specific Hosts ==
We allow only access from known hosts
{{{
gluster volume set www auth.ssl-allow 'gluster01,gluster02,gluster03,gluster04,glusterclient01'
}}}

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 client/server. Repeat this on all the servers and the client.

Server

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

Client

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

Certificate Authorities

Compile all the certificates in one place and concatenate them into /etc/ssl/glusterfs.ca. Notice that this will also include the certificates from the client.

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

Copy the certificate authority to all the servers and place it in /etc/ssl/glusterfs.ca

Activate Encryption

When this file exists the glusterfs server will use the new certificates

touch /var/lib/glusterd/secure-access

Enable Encryption

On one of the servers encryption is enabled

gluster volume set www client.ssl on
gluster volume set www server.ssl on

Allow Only Specific Hosts

We allow only access from known hosts

gluster volume set www auth.ssl-allow 'gluster01,gluster02,gluster03,gluster04,glusterclient01'

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