Received-SPF: pass (google.com: domain of linux-nfs+bounces-2738-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Precedence: bulk
MIME-Version: 1.0
From: =?UTF-8?Q?Z=C3=A9_Geraldo?= <zgcarvalho@gmail.com>
Date: Tue, 9 Apr 2024 17:50:04 -0300
Message-ID: <CABJN9r6n1mxLNqFo2nsM9gBz6LDku9kk_V6c-85pMeH=CGzEaw@mail.gmail.com>
Subject: Configuring NFS with UID/GID Offset (sec=sys approach)
To: linux-nfs@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,

I'm seeking advice on configuring NFS to handle a specific scenario
where the server and client have an offset in their UID/GID values. On
the server, a UID/GID translates to a UID/GID + 10000 on the client
side.

Ideally, I'd like to avoid modifying server configurations or changing
client UIDs at this time.

My current approach involves utilizing the sec=3Dsys option with an
offset to bridge this UID/GID gap. However, I'm unsure about the
effectiveness of this method and would appreciate any insights from
the community about how I could do this.

Here's a summary of the situation:

Problem: Server and client have a UID/GID offset (server UID/GID =3D
client UID/GID + 10000)
Goal: Configure NFS to handle this offset without server config
changes or client UID modifications.
Possible Solution (under consideration): Using sec=3Dsys with an offset
in the mount options.

While alternative configurations like sec=3Dkrb5 functioned in a test
environment, modifying the server configuration is not preferred.

If anyone has experience with similar scenarios or can offer guidance
on using sec=3Dsys with offsets for NFS, your expertise would be greatly
appreciated.

Thanks,

Jos=C3=A9 Geraldo