This is the gssapi implementation file for using NFSv4 securely. It implements the rpcsec_gss protocol for NFSv4 to have secure rpc communication. This requires libgssapi, which I've submitted separately. A basic ebuild and license will be attached.
Created attachment 81000 [details] ebuild for librpcsecgss
Created attachment 81001 [details] license for librpcsecgss
Created attachment 88321 [details] librpcsecgss-0.12.ebuild Update for the ebuild
Created attachment 88644 [details] librpcsecgss-0.12.ebuild
Created attachment 88646 [details, diff] librpcsecgss-0.12-heimdal.patch
wondering who should take this ... or if we should do a dual herd thing ...
(In reply to comment #6) > wondering who should take this ... or if we should do a dual herd thing ... > i think this is a package for nfs4@gentoo.org
(In reply to comment #5) > Created an attachment (id=88646) [edit] > librpcsecgss-0.12-heimdal.patch > the reason for this patch ist a dependency tree: libgssapi --> mit-krb5 --> librpcsecgss --> nfs-utils or heimdal --> librpcsecgss --> nfs-utils
This ebuild should depend on libgssapi, since it doesn't compile without it.
(In reply to comment #9) > This ebuild should depend on libgssapi, since it doesn't compile without it. > this ebuild depends on bug 136039 mit-krb5 doesn't provide libgssapi only his own libgssapi_krb5 (spezial krb5 version) so mit-krb5 should depend on libgssapi. if you use heimdal then you already have libgssapi.so.4 so no need to install libgssapi.so.2 and i think there should not be 2 libs with same functionality on the system.
Ah ok. I only installed the bugzilla version of librpcsecgss and not the mit-krb5 version from here. In this situation I wondered why it didn't depend on gssapi, but I think now it's clear. :)
Created attachment 89146 [details] librpcsecgss-0.13.ebuild version bump
now in portage, shall we close/reassign bug ?
(In reply to comment #13) > now in portage, shall we close/reassign bug ? > close the bug
in cvs