James Cuzella

I can reproduce this with CoreOS versions, `835.12.0`, and `835.13.0`. This is in addition to the original poster's version `835.11.0`. Seems that the versions of `/lib64/libcrypto.so.1.0.0` and `/lib64/libssl.so.1.0.0` shipped with...

> Related `vagrant-libvirt` is currently having installation issues with M1 mac because of confusing ruby native packages: [vagrant-libvirt/vagrant-libvirt#1205](https://github.com/vagrant-libvirt/vagrant-libvirt/issues/1205) Yes, this is still [correct as of today][1] when using officially released...

Ping @mrtazz

> I think in addition to making the matching a bit better we should probably also never treat `.PHONY` as a variable name anyways. @mrtazz It's funny you mention that...

> I am not sure why this PR's GitHub Actions is not executed. Maybe it's because permissions are needed? I just created a PR (#69) and it says this: >...

I've noticed with Yubikey 4 Nano, sometimes `scdaemon` gets into a borked state. It ends up yielding the same error when using signed commits. Workaround that seems to fix it...

This tool [appears to be stagnant][1] & suffering [bit-rot][2]. No updates to `scapy` version since `v2.4.0`, updates were discussed in #8 but it never was completed. They suggest pinning `scapy`...

🎉 🙌 🚀 Excited to see Vagrant 2.3.0 is now released, and `vagrant-go` is included! Congrats @chrisroberts & Vagrant dev team! ```bash brew info --cask vagrant ==> vagrant: 2.3.0 https://www.vagrantup.com/...

> If anyone has a workaround, please let me know. I've been able to work around the issue by [installing `vagrant` and other ruby gems from source][1]. While this works...

Bumping issue to avoid the `dessant/lock-threads` bot 🤖 closing it prematurely...