#1072165 ftpmasters: please decide on sunrpc in dietlibc

#1072165#5
Date:
2024-05-29 13:54:22 UTC
From:
To:
Dear ftpmasters,

in #1067946 it was reported that some consider the sunrpc code as
included in dietlibc nōn-free.

Given that the actual wording is…

… and that we receive dietlibc as “a product or program developed by”
Fefe (upstream author) under GPL, I think differently, and this *has*
passed review in the past.

Ultimately, *our* options are closing this as not a problem, removing
dietlibc (not very favourable), and excising the code in question
hoping not to break any downstream users. The reporter has also sent
this to upstream, which is the correct place where to apply the fix
suggested (replace with a different implementation), but there hasn’t
yet been any response or decision either way.

Now I don’t just want to close it or play bug pingpong, so I’d prefer
there to be an official decision either way, so that we can decide
what to do. (And then, I can invest some time to look at the other RC
reported and try to reproduce it on a porterbox etc. but I prefer to
do this when there’s not a sword of possible removal hanging over us.)

Thanks in advance!

#1072165#16
Date:
2025-01-30 18:05:06 UTC
From:
To:
retitle 1072165 ftpmasters: please decide on sunrpc in dietlibc, openafs
block 1072708 1072165
severity 1072708 important
thanks

Hi ftpmasters,

It seems that (#1072708) openafs is in a similar situation as dietlibc in
that the Sun RPC code is included in openafs and the freeness of this usage
hinges on this clause:

In openafs we have patched the rpcgen sources somewhat heavily and
distribute it as "rxgen", which would seem to me to make this a program
developed by the OpenAFS project (i.e., not Sun RPC).

I believe that the process of making a decision for dietlibc's case will
have very high overlap with the process of making a decision for openafs's
case, and am retitling this bug accordingly; please feel free to revert
and/or let me know if you prefer a separate ticket.

I'm also downgrading the bug against openafs to important pending the
decision, since AFAICT it has not been established that the code in
question is in violation of policy (and this bug is how that will be
established or not).

Thanks,

Ben Kaduk