librpcsecgss conflicts with clnt libc symbols
Subsystems (2)
the librpcsecgss duplicates some functions that the system libc normally provides ... in this case:clnt_createclnt_pcreateerrorclnt_perrnoclnt_perrorclntraw_createclnt_spcreateerrorclnt_sperrnoclnt_sperrorclnttcp_createclntudp_bufcreateclntudp_create
is there a reason for this ? i went through the ChangeLog and couldnt find anything ... this stuff was added like between 0.7 and 0.8 but there doesnt appear to be any mention of why ...
-mike
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
They were added in 0.8:
Quoted 8 lines
Changes since librpcsecgss-0.7:
-- From Olga Kornievskaia: add new
prep_refreshfunction to clean up
context information before trying to refresh a context
-- From Olga Kornievskaia: add new function to access retry count
for a context.
-- Adds backclnt_files which have the necessary calls needed for
privacy.
The libc versions of the clnt*_call functions do not call the AUTH_WRAP and AUTH_UNWRAP functions needed for privacy.
Quoted 26 lines · Mike Frysinger
the librpcsecgss duplicates some functions that the system libc normally provides ... in this case:
clnt_createclnt_pcreateerrorclnt_perrnoclnt_perrorclntraw_createclnt_spcreateerrorclnt_sperrnoclnt_sperrorclnttcp_createclntudp_bufcreateclntudp_createis there a reason for this ? i went through the ChangeLog and couldnt find anything ... this stuff was added like between 0.7 and 0.8 but there doesnt appear to be any mention of why ...
-mike-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Quoted 7 lines
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 10 lines · Kevin Coffman
They were added in 0.8:
Quoted 8 lines
Changes since librpcsecgss-0.7:
-- From Olga Kornievskaia: add new
prep_refreshfunction to clean up
context information before trying to refresh a context
-- From Olga Kornievskaia: add new function to access retry count
for a context.
-- Adds backclnt_files which have the necessary calls needed for
privacy.
Quoted 2 lines
The libc versions of the clnt*_call functions do not call the
AUTH_WRAPandAUTH_UNWRAPfunctions needed for privacy.
ok, so that answers the first question (should they be there) ...
next is, should they be hidden for internal use only ? or all consumers of librpcsecgss supposed to call the clnt_* funcs in there ?
the problem i'm trying to deal with is glibc may call the clnt funcs in some auth scenarios and the versions in librpcsecgss are used instead of the ones in libc (like when libnsl enters the picture)
i'll prob have to go through this user's bug report and try to reproduce it myself ... last time i tried to use nfs4 it just totally didnt work ;) -mike
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 19 lines · Mike Frysinger
Quoted 10 lines · Kevin Coffman
They were added in 0.8:
Quoted 8 lines
Changes since librpcsecgss-0.7:
-- From Olga Kornievskaia: add new
prep_refreshfunction to clean up
context information before trying to refresh a context
-- From Olga Kornievskaia: add new function to access retry count
for a context.
-- Adds backclnt_files which have the necessary calls needed for
privacy.Quoted 2 lines
The libc versions of the clnt*_call functions do not call the
AUTH_WRAPandAUTH_UNWRAPfunctions needed for privacy.ok, so that answers the first question (should they be there) ...
next is, should they be hidden for internal use only ? or all consumers of librpcsecgss supposed to call the clnt_* funcs in there ?
Quoted 7 lines
the problem i'm trying to deal with is glibc may call the clnt funcs in some auth scenarios and the versions in librpcsecgss are used instead of the ones in libc (like when libnsl enters the picture)
i'll prob have to go through this user's bug report and try to reproduce it myself ... last time i tried to use nfs4 it just totally didnt work ;) -mike
I've seen this with authenticated NIS. Can you point me at the bug report?
I'm working on a patch right now for librpcsecgss that hides our versions of these functions by renaming them to rpcsecgss_*. It may require some configure changes to the nfs-utils code to make it happy with the new names...
K.C.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 1 line · Kevin Coffman
I've seen this with authenticated NIS. Can you point me at the bug report?
Quoted 4 lines
I'm working on a patch right now for librpcsecgss that hides our versions of these functions by renaming them to rpcsecgss_*. It may require some configure changes to the nfs-utils code to make it happy with the new names...
thanks !
-mike
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs