Dropbox has been removed from the ClearCenter Marketplace for ClearOS as of today. We'd like to add it back in. ClearOS makes it easy to implement Dropbox on Linux (on a flavor of Linux similar to CentOS and RHEL) by making Dropbox as easy to install as apps on a mobile device. We have had support for Dropbox for several years now.
We have been aware that the glibc requirement was coming down the pipe for about a month now. But we cannot change the version of our glibc without breaking things. We already backport security fixes so our glibc is not vulnerable to any CVE against this version (that we are aware). We were hopeful that the glibc requirement, which does not affect functionality from what we can tell, would be exempted for the glibc library for CentOS and RHEL due to its pervasive usage in the world. As it stands, because of this change, no version of CentOS, RHEL, Scientific Linux, Oracle Enterprise, or SME is compatible with Dropbox due to this change.
As you may know, RHEL and CentOS backport fixes in order to maintain security while keeping version numbers static. If the concern about security bugs with glibc is the problem here, the dropbox application should do a better job at identifying the glibc. This can easily be done by looking at the RPM involved and then looking at the signer of the RPM. If the RPM is signed by Redhat or CentOS, then security can be assumed to be ok. Feel free to reference the Redhat CVE database for confirmation.
We are looking for a way to move forward here and have discussed using docker as a way to isolate the glibc requirement but have been unable to find an official docker image. Please advise on what we can do to fix this for our userbase. -DaveLoper, CTO, ClearCenter
Just second-ing the OP. Our CentOS and RHEL users (running the latest fully patched versions) are cut off. We're scrambling to make a docker container, but no luck yet. Will there be a containerized version?