Unknown/unsupported OpenSSL version ("30100040 (OpenSSL 3.1.4 24 Oct 2023)")

[ickc]

When installing on Arch Linux,

checking OpenSSL library version... configure: error: Unknown/unsupported OpenSSL version ("30100040 (OpenSSL 3.1.4 24 Oct 2023)")

From

gct/gsi_openssh/source/configure.ac

Lines 2844 to 2862 in 07008c3

	ssl_library_ver=`cat conftest.ssllibver`
	# Check version is supported.
	case "$ssl_library_ver" in
	10000*|0*)
	AC_MSG_ERROR([OpenSSL >= 1.0.1 required (have "$ssl_library_ver")])
	;;
	100*) ;; # 1.0.x
	101000[[0123456]]*)
	# https://github.com/openssl/openssl/pull/4613
	AC_MSG_ERROR([OpenSSL 1.1.x versions prior to 1.1.0g have a bug that breaks their use with OpenSSH (have "$ssl_library_ver")])
	;;
	101*) ;; # 1.1.x
	200*) ;; # LibreSSL
	300*) ;; # OpenSSL 3
	301*) ;; # OpenSSL development branch.
	*)
	AC_MSG_ERROR([Unknown/unsupported OpenSSL version ("$ssl_library_ver")])
	;;
	esac

C.f. https://aur.archlinux.org/packages/gct#comment-943688

[fscheiner]

Thanks for the pointer.

But I wonder why it doesn't work for your OpenSSL version 3.1.4. Because considering that openssh/openssh-portable@f6d3ed9 enables version 3.2.x and openssh/openssh-portable@3e21d58 enables 3.3.x, 301 should enable 3.1.x if I'm not mistaken.

And 301* should at least match the first part of 30100040 (OpenSSL 3.1.4 24 Oct 2023).

[msalle]

but the commit adds just the 300 and 301 as unsupported versions. Also the one before, from 2 years ago, adds 300 as unsupported version.
That's different from this commit in the upstream patches.

[fscheiner]

@msalle

but the commit adds just the 300 and 301 as unsupported versions. Also the one before, from 2 years ago, adds 300 as unsupported version.

No, I think there is no fall-through to the unsupported *) case. If there was, all cases would fall-through instead of ending at the ;;.

[msalle]

ah right indeed, sorry shouldn't have looked on my phone.

The problem is that the configure.ac in gct-6.2.1653033972/gsi_openssh/source is an old one. I just noticed that the configure and configure.ac in there only support up to 3.0.X.
Also the current draft release still points to that version of Jun 8, 2022. The 301 support dates back to Feb 21 (see f60262d)

[fscheiner]

ah right indeed, sorry shouldn't have looked on my phone.

I made the same error at first, because it just looks like so.

The problem is that the configure.ac in gct-6.2.1653033972/gsi_openssh/source is an old one. I just noticed that the configure and configure.ac in there only support up to 3.0.X.

Now I understand the problem. I didn't notice that issue as the OP quoted from current code state - where it looks and is OK IIUC - but used the last release tarball when trying to build the package on AUR, which is pre 2022-05-24.

Also the current draft release still points to that version of Jun 8, 2022. The 301 support dates back to Feb 21 (see f60262d)

Yes, I haven't yet updated the draft release since copying the content from the last release.

[fscheiner]

@ickc: This issue will hence be solved with the next GCT release that will materialize before end of this year.

[ickc]

Thanks all. I guess it should be closed now.

[fscheiner]

Oh, we usually keep issues open until there's a release that fixes them.

[ickc]

Ok, sure. Thanks again! Sorry for not having time to look into it again and providing more details, but you all figured it out already.