bugTransport Sample Protocol - Bugs: bug #20936, RPC: Authentication error; why =...


bug #20936: RPC: Authentication error; why = Client credential too weak

Submitted by:  Eric NOULARD <erk>
Submitted on:  Thu 30 Aug 2007 11:56:36 AM UTC  
Category: CoreSeverity: 3 - Normal
Status: ConfirmedPrivacy: Public
Assigned to: NoneOpen/Closed: Open
Release: 0.8.3Fixed Release: Unknown

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

Please log in, so followups can be emailed to you.


Tue 24 Jun 2008 08:08:09 PM UTC, comment #4:

The problem is no longer there on Fedora 9.
It still uses the TI-RPC libs.
I guess there was a bug in the rpcbind that did not allow requests to be made through the loopback interface.

See also RedHat bug 358621

Robert de Vries <rhdv>
Project Member
Tue 25 Mar 2008 03:56:41 PM UTC, comment #3:

I do add a temporary fix
which is to start rpcbind service in "insecure mode"
if you want to do that you may cp
the attached rpcbind file to


this works on Fedora 7

(file #15332)

Eric NOULARD <erk>
Project Administrator
Thu 30 Aug 2007 01:39:34 PM UTC, comment #2:

Heres comes some more links about TI-RPC and RPCBind:


Eric NOULARD <erk>
Project Administrator
Thu 30 Aug 2007 01:34:03 PM UTC, comment #1:

Ok I think I will understand to myself.
The fact is Fedora 7 in the first linux distro
I've crossed which use

rpcbind is a drop-in replacement for
"classical" rpc portmapper.

It may be worth detecting if we are on a system
which use TI-RPC or "classical ONC-RPC"
and effectively use TI-RPC API instead of older SunRPC/ONCRPC.

but in the meantime the only acceptable solution
is to start rpcbind with the "-i" insecure option.

I "unassign" the bug since I'm not sure to have time to handle it.

Eric NOULARD <erk>
Project Administrator
Thu 30 Aug 2007 11:56:36 AM UTC, original submission:

On a Fedora 7 box
I am unable to start the properly compiled stub server
and I get the following error:

I am able to start stub server when logged as root.
And I am able to start it if the rpcbind daemon/service
is started using the "Insecure" mode.

As far as I understand, this would mean that we try
to use the rpc portmapper service through an @IP which
is not

Eric NOULARD <erk>
Project Administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):

Attached Files
file #15332:  rpcbind added by erk (16B - application/octet-stream - rpcbind sysconfig options file)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by rhdv (Posted a comment)
  • -unavailable- added by erk (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 25 Mar 2008 03:56:41 PM UTCerkAttached File-=>Added rpcbind, #15332
    Thu 30 Aug 2007 01:34:03 PM UTCerkStatusNone=>Confirmed
      Assigned toerk=>None

    Back to the top

    Powered by Savane 3.1-cleanup