Tiny Core Base > Alpha Releases
Tiny Core 14.0 Alpha 1 Testing
curaga:
The busybox build is not static, old glibc CVEs are not affecting anything. It's simply dynamic linking to code that still exists in the current glibc, but is just not allowed to be linked against anymore.
adb014:
Reading a bit, it seems that removing CONFIG_FEATURE_MOUNT_NFS won't stop NFS from working with kernels move recent than 2.6.23. See http://lists.busybox.net/pipermail/busybox/2017-September/085848.html where the busybox developer seem to have MOUNT_NFS desactivated by default
CNK:
--- Quote ---Reading a bit, it seems that removing CONFIG_FEATURE_MOUNT_NFS won't stop NFS from working with kernels move recent than 2.6.23. See http://lists.busybox.net/pipermail/busybox/2017-September/085848.html where the busybox developer seem to have MOUNT_NFS desactivated by default
--- End quote ---
The "If im reading the docs correctly" bit of the post at that link makes one wonder where those docs are. After some searching it turns out the CONFIG_FEATURE_MOUNT_NFS has been depreciated and removed from the BusyBox config docs. You can see the old description in this git commit:
--- Quote ---- Enable mounting of NFS file systems.
+ Enable mounting of NFS file systems on Linux kernels prior
+ to version 2.6.23. Note that in this case mounting of NFS
+ over IPv6 will not be possible.
+
+ Note that this option links in RPC support from libc,
+ which is rather large (~10 kbytes on uclibc).
--- End quote ---
But in the same year someone on the Debian mailing list described it here as if it were more of a behaviour changing option, and suggested turning it on (without anyone raising objections):
--- Quote ---- # CONFIG_FEATURE_MOUNT_NFS is not set
+ CONFIG_FEATURE_MOUNT_NFS=y
this enables mounting of nfs filesystems just like
old mount from util-linux did (now it all is moved
to nfs-common with a helper mount.nfs). This is to
support nfs root. NFS mount needs rpc library, which
is not very large. RFC.
--- End quote ---
The BusyBox mailing list thread also mentions a solution for building with newer glibc versions when CONFIG_FEATURE_MOUNT_NFS is set:
--- Quote ---The cause of this is that rpc.h is no longer included in glibc-2.26. See
the announcement and release notes here:
https://sourceware.org/ml/libc-alpha/2017-08/msg00010.html
* Sun RPC is deprecated. The rpcgen program, librpcsvc, and Sun RPC
headers will only be built and installed when the GNU C Library is
configured with --enable-obsolete-rpc. This allows alternative RPC
implementations, such as TIRPC or rpcsvc-proto, to be used.
So there are workarounds that work (enable obsolete-rpc).
--- End quote ---
That seems like the safest/easiest option if it still works, but my aim is just to clarify the facts for the TC developers.
Rich:
Hi CNK
I think --enable-obsolete-rpc may have been removed:
--- Quote ---Deprecated and removed features, and other changes affecting compatibility:
* Remove configure option --enable-obsolete-rpc. Sun RPC is removed
from glibc. This includes the rpcgen program, librpcsvc, and the Sun
RPC header files. Backward compatibility for old programs is kept
only for architectures and ABIs that have been added in or before
glibc 2.31. New programs need to use TI-RPC
< http://git.linux-nfs.org/?p=steved/libtirpc.git;a=summary > and
rpcsvc-proto < https://github.com/thkukuk/rpcsvc-proto >.
--- End quote ---
Dated 6 Aug 2020 for GNU C Library version 2.32 found here:
https://lwn.net/Articles/828210/
Similar information plus a little history:
https://stackoverflow.com/a/71976359
curaga:
If the option were disabled, NFS mounting would require the nfs-utils mount.nfs and helpers. Having minimal NFS support (nolock and ipv4) without bloat is good.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version