Linux DuoConnect v2.0.7 issue on Red Hat 8

[dfouch]

Tried to update DuoConnect 2.0.4 to the latest 2.0.7 and get the following error: duoconnect: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by duoconnect).

[DuoMario]

Hi @dfouch, appreciate you reaching out!

I am on the engineering team; we haven't seen this issue yet but it's likely due to our team updating the builder images which are linked to a later version of glibc. It looks like at the moment, RHEL 8 (and CentOS Stream 8 ) only support up to glibc-2.28. RHEL 9+ support glibc-2.34+ (if the data on distrowatch is correct).

At the moment, downgrading duoconnect to v2.0.4 (link: https://dl.duosecurity.com/DuoConnect-2.0.4.tar.gz) should unblock your system and ignore the update that the Duo Network Gateway advises when connecting to an SSH server.

We are going to internally investigate if we can remove the dependency on glibc for DuoConnect on Linux. If we are able to successfully remove the dependency, we can provide a preview 2.0.8 release for you to test. Would that be helpful? We will begin investigation today and hope to have more information early next week!

We'll also make a note on our release notes page about this glibc deprecation as well.

[dfouch]

I will look at using the other version and update the post.

[DuoMario]

Hi @dfouch! We should have a preview release of DuoConnect with a glibc fix soon. How did downgrading work for you?

[dfouch]

I apologize for not updating the post. The issue is the site we were trying to connect with wants v2.0.8 and we are still using v2.0.4. We were attempting to comply with their request, by upgrading to v2.0.8 when we discovered the glibc dependency issue. So we were unable to upgrade. So we rolled back to v2.0.4. Our users, are still able to gain access to the site but they are presented with a warning box asking them to upgrade. The concern is they will loose connectivity when the remote site says v2.0.4 is no longer accepted. Thank you for the update.

[DuoMario]

Absolutely no worries. I'll make sure to ping this thread once the beta release is publicly available. Your users will be OK for now, as the Duo Network Gateway in conjunction with Duo handles deprecating older DuoConnect versions and 2.0.4 is not considered deprecated at this time, and definitely not before we have a release in place for Linux to resolve the glibc issue.

[dfouch]

Curious, if there is an expected update sometime in the near future?

[DuoKristina]

@dfouch The 2.0.8 release went to GA back in September 2025. Do you find it has an issue?

[dfouch]

Your response makes me suspect you didn't see the original inquiry. So here it is.
Tried to update DuoConnect 2.0.4 to the latest 2.0.7 and get the following error: duoconnect: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by duoconnect).
I saw the updated version 2.0.8 had been released and being under the impression that it would include code changes to support RHEL 8 I attempted to update to version 2.0.8. Unfortunately it is still saying that it requires /lib64/libc.so.6: version `GLIBC_2.34"
To be clear it is not the "updating process" that throws the error it is when I attempt to run DuoConnect.

[DuoKristina]

Thanks, @dfouch , I did in fact read the entire thread before responding.

1. On April 24 you posted that you updated 2.0.4 to 2.0.7 and noted the glibc incompatibility.
2. On April 25 Mario offered that a 2.0.8 preview could be made available to you, and also suggested downgrading to 2.0.4.
3. On May 15 Mario offered that a preview could be available soon, and asked again about downgrading to 2.0.4,
4. On the same day, May 15, your response mentioned 2.0.8, but I assumed this was a typo and you meant 2.0.7 because you stated that your DNG "wants v2.0.8 and we are still using v2.0.4". Your DNG could not have required that you use a 2.0.8 client before we released 2.0.8 to GA, which did not happen until September. Also at this point in the conversation Mario was still referring to the 2.0.8 beta with future availability, not that it was already available.
5. Mario's second response on May 15 implied the 2.0.8 beta release was not yet available.
6. On November 25 you asked for an update, without mentioning if you had actually tried the September 16 2.0.8 GA DuoConnect release , which is why I responded by asking if you found an issue with 2.0.8 as well.

Now that you have confirmed the issue persists in the 2.0.8 release, we can proceed.

[DuoKristina]

Happy to share that while the team acknowledged the glibc fix did not make it into 2.0.8, they do plan to include it in 2.0.9 and that could be available as soon as next month.

[DuoKristina · Accepted solution]

Hey @dfouch , 2.0.9 is out and should have the glibc fix.

[dfouch]

Thank you,
I did a quick test using duoconnect --version and it no longer complains about missing a glibc dependency.
Thank you again.