Lars Kanis

Yes the gem supports AES-GCM. But your PKCS11 library must support it as well. You need to use `PKCS11::CKM_AES_GCM` and `CK_GCM_PARAMS`. If your library doesn't support GCM, then it's still...

@spencescu Is this issue solved?

This is what the digest value is for. So I think it would be better so print: ``` WARNING: insecure source being used: #{url} - Please define a MD5/SHA1/SHA256 digest...

As a quick workaround you can use either: `gem install serialport -- --with-cflags=-Wno-int-conversion` or with bundler: `bundle config build.serialport -- --with-cflags=-Wno-int-conversion`

There is a simple ruby version switcher builtin into RubyInstaller: https://github.com/oneclick/rubyinstaller2/wiki/The-ridk-tool#ridk-use It doesn't do installation of ruby versions but switching between them only. Switching between versions simply works without any...

The current mechanism for loading nmatrix plugins works, because some symbols (like `rubyval_to_cval`) are kept unresolved while linking and the `nmatrix.so` file is [always loaded before](https://github.com/SciRuby/nmatrix/blob/7f3fa5d2e1e858b5c7df7136fd899da7f590c018/lib/nmatrix/lapacke.rb#L30) `nmatrix_lapack.so` and the dynamic...

There will be no further ruby-3.0.x release since it is EOL. And with #381 merged I think we can close this issue.

The test is modified to show, that arbitrary Unicode characters can work now. However it is not necessary to change the test - it passes with and without modification.

It would be nice if this PR could be merged to Ruby-3.4 since it fixes longstanding bugs. I added an item to the compatibility section of the NEWS.md.

I rebased this and hope this can be merged to ruby-3.5.