<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#444646">
<div class="moz-cite-prefix"><font face="Helvetica, Arial,
sans-serif">I already have a hosts.allow in place, but have a
requirement to export the volume read-only on servers side for
some clients. <br>
The data must not be tampered with, so I must restrict it server
side as I am not in control of the client.</font><br>
<br>
On 03-10-14 06:39, James wrote:<br>
</div>
<blockquote
cite="mid:CADCaTgq=-_aKGXn==iBxyekaFXW+fN-+f-EbH1XcixKfXELhVQ@mail.gmail.com"
type="cite">
<pre wrap="">On 3 October 2014 00:30, Tom van Leeuwen <a class="moz-txt-link-rfc2396E" href="mailto:tom.van.leeuwen@saasplaza.com"><tom.van.leeuwen@saasplaza.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm running gluster 3.4.2 and have the requirement to export a glusterfs
volume read-only to some hosts, but definitely not all.
Is there any way to achieve this without having to introduce a frontend nfs
server?
</pre>
</blockquote>
<pre wrap="">
You should only allow hosts access to your GlusterFS servers that you
trust. Firewall off the rest, and use auth.allow and auth.reject for
the others.
This is needed because GlusterFS doesn't have built in authentication.
So the answer is that you must mount the volume readonly with standard
mount 'ro' vs. 'rw' options.
If there is a better solution than this, I don't know it, and maybe
someone will let me know.
Cheers,
James
</pre>
</blockquote>
<br>
</body>
</html>