crypt and POSIX

[Chris Johns]

On 13/8/20 11:47 pm, Joel Sherrill wrote:
> On Thu, Aug 13, 2020 at 7:52 AM Sebastian Huber
> <sebastian.huber at embedded-brains.de <mailto:sebastian.huber at embedded-brains.de>>
> wrote:
> 
>     On 13/08/2020 14:49, Joel Sherrill wrote:
> 
>     > Why was crypt() removed? It is in the FreeBSD version at the bottom of
>     > the file.
>     >
>     > https://github.com/freebsd/freebsd/blob/master/lib/libcrypt/crypt.c
>     It is not thread-safe.
> 

> But it is standards compliant.

Could it be added and just return NULL or even generate an internal error? The
lack of crypt stopped me from using and it made me consider the issues. It is
easy to forget these things when adding passwords to the console or telnet
server and really hard to see an issue.

> And this would seem to violate the rules of source transparency in the 
> way the code was removed. If you wanted to disable it, it should have
> been wrapped in ifndef __rtems__.

I am confused, the code in cpukit/libcrypt is not from FreeBSD?

Chris