3 ms·

Sounds like you had better upgrade to the fixed glibc version if you're running php...

• smsm42 2y ago
  Or if you're not running PHP, since surprisingly enough PHP is not the only software using iconv() function.
• thenickdude 3y ago
  Or else edit /usr/lib/x86_64-linux-gnu/gconv/gconv-modules and comment out this section: # from to module cost alias ISO2022CNEXT// ISO-2022-CN-EXT// module ISO-2022-CN-EXT// INTERNAL ISO-2022-CN-EXT 1 module INTERNAL ISO-2022-CN-EXT// ISO-2022-CN-EXT 1 Then run "iconvconfig" to rebuild the iconv cache. This disables that charset completely.
  • LXicon 3y ago
    As a test on various distros, I ran iconv -l |grep 2022 |grep -i cn and it listed ISO-2022-CN-EXT// and ISO2022CNEXT// before I made any changes. After editing the modules and running iconvconfig the command no longer showed those charsets. This was handy since the alma8 has a /usr/lib64/gconv/gconv-modules file but the file to edit was /usr/lib64/gconv/gconv-modules.d/gconv-modules-extra.conf
    • voyagerfan5761 3y ago
      Thanks a bunch to you and thenickdude for the test command and config to change. I have an old VPS that isn't worth trying to update to a newer OS image, because I'm already (slowly) migrating things off of it before the current paid-up term expires, but it definitely won't get the newer glibc. Disabling the vulnerable character encoding works for me, since no legitimate user of the server will need these conversion pairs.