Bug 2048457

Summary:	Using trusted for NFS client and server
Product:	Red Hat Enterprise Linux 9	Reporter:	Pierguido Lambri <plambri>
Component:	gssproxy	Assignee:	Julien Rische <jrische>
Status:	CLOSED MIGRATED	QA Contact:	anuja <amore>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.4	CC:	abokovoy, bdm, fs-qe, xzhou, yoyang
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 18:58:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pierguido Lambri 2022-01-31 09:55:33 UTC

Description of problem:
The current defaults NFS settings use "trusted = yes" for both client and server.
However, the NFS workflow (at least for the NFS client) should make it possible to have gssproxy working without trusted enabled.

Version-Release number of selected component (if applicable):
All

How reproducible:
Always

Steps to Reproduce:
1. Check NFS server and client default settings

Actual results:
Trusted is used.


Expected results:
Trusted may not be used.

Additional info:
The example given in the upstream documentation shows that trusted is not used (https://pagure.io/gssproxy/blob/master/f/docs/NFS.md) for the NFS client.

Comment 11 RHEL Program Management 2023-09-18 18:55:50 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 12 RHEL Program Management 2023-09-18 18:58:09 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.