Needless to say, you shouldn’t even consider using such old versions in 2019. But if you have to use it after all, e.g. because the management of your company is grossly handicapped mind-bogglingly incapable, or you just have fun in getting hacked in production, these are the things to consider:

  • ruby < 2.4 not being compatible with OpenSSL 1.1 (which is the default one on Arch)
    • OpenSSL 1.0 still available in repos, pacman -S openssl-1.0
    • compile with PKG_CONFIG_PATH=/usr/lib/openssl-1.0/pkgconfig set
  • ruby 1.9.3 requiring SSLv3, which isn’t compiled in Arch’s OpenSSL (for good reason)
    • make it optional with this patch
  • ruby 1.9.x not supporting TLS (any)
  • CVE-2015-1855 2 not fixed
  • GCC crashes
    • ↑ don’t have these anymore since gcc 8, but had these with gcc 7

good news is, I made a patch mitigating all of these problems.


PKG_CONFIG_PATH=/usr/lib/openssl-1.0/pkgconfig ruby-install \
--patch \

or rbenv

PKG_CONFIG_PATH=/usr/lib/openssl-1.0/pkgconfig \
rbenv install --patch 1.9.3-p551 < <(curl -sSL 

or asdf

PKG_CONFIG_PATH=/usr/lib/openssl-1.0/pkgconfig \
asdf install ruby 1.9.3-p551