RTEMS | Re-import libcrypt as a proper 3rd-party library (#5332)

[Wayne Thornton (@wmthornton-dev)]

Wayne Thornton commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5332#note_130499


@opticron and @joel - I gotta be honest here, running a diff on the 'crypt.h' from the FreeBSD source tree and the RTEMS source tree basically reveals that with the exception (excluding license header) of a couple function names (not the function params, just the names) the RTEMS 'crypt.h' is essentially new work without any real link back to FreeBSD. I'm almost thinking our version of 'crypt.h' could be simply relicensed to Sebastian's company (he was the commit author back in 2014) without running afoul of the license. Thoughts?

![Screenshot_From_2025-09-05_14-34-44](/uploads/9be619ddcc0df348b098d41b2dbbb7f5/Screenshot_From_2025-09-05_14-34-44.png)

![Screenshot_From_2025-09-05_14-35-04](/uploads/710a7d33ba5fde96d55d837ba970a81d/Screenshot_From_2025-09-05_14-35-04.png)

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5332#note_130499
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250905/97b17bfd/attachment.htm>