Bug 2188797 - default configuration file 99-network-fs-clients.conf allows more than nfs
Summary: default configuration file 99-network-fs-clients.conf allows more than nfs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gssproxy
Version: 39
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/gssapi/gssproxy/bl...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-22 11:23 UTC by François Rigault
Modified: 2024-11-27 21:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:11:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description François Rigault 2023-04-22 11:23:21 UTC
gssproxy (0.9.1-5.fc38) is bundled with a default "99-network-fs-clients.conf" config file
There is no restriction of "program" in that file, so any program is able to use the gssproxy, not only rpc.gssd.

(moreover the program only checks for the executable realpath, so having program=/usr/sbin/rpc.gssd can still be bypassed if the user crafts its own LD_PRELOAD or LD_LIBRARY_PATH I believe).

I am trying to have gssproxy create tickets for nfs client, and nothing else.



Reproducible: Always

Steps to Reproduce:
1. configure gssproxy
2. configure ssh server for gssapi authentication
3. GSS_USE_PROXY=yes ssh -K -o PreferredAuthentications=gssapi-with-mic vagrant.test
Actual Results:  
ssh connection just works

Expected Results:  
ssh connection should fail as we only have configuration for nfs server and client

I am looking for a way to transparently activate krb5p on my NFS volumes, without granting users any extra right.

Comment 1 Fedora Release Engineering 2023-08-16 08:09:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Aoife Moloney 2024-11-08 10:51:41 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2024-11-27 21:11:11 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.