Kimmo Lehto
Kimmo Lehto
I think this can be classified as a duplicate of #384
And therefore also related: https://github.com/k0sproject/k0s/issues/1707
I made a small [gem](https://rubygems.org/gems/yaml-safe_load_stream) for this but it's not very full featured.
Json-jwt comes as a dependency of the LE certificate client dependency `Acme::Client`, which has dropped the json-jwt dependency in recent versions. Comes from #830
Needs code + spec fixes if upgraded to 2.0. 1.0 seems compatible.
I wonder how that vulnerability affects the master
That is the case. Can be ignored for now in my opinion. ```console $ bundle show acme-client /usr/local/Cellar/rbenv/1.1.1/versions/2.5.0/lib/ruby/gems/2.5.0/gems/acme-client-0.3.4 $ ag -B 1 JWT /usr/local/Cellar/rbenv/1.1.1/versions/2.5.0/lib/ruby/gems/2.5.0/gems/acme-client-0.3.4 /usr/local/Cellar/rbenv/1.1.1/versions/2.5.0/lib/ruby/gems/2.5.0/gems/acme-client-0.3.4/lib/acme/client/crypto.rb 8- def generate_signed_jws(header:, payload:) 9:...
Ignoring though means that we need to disable the vulnerability check in specs or it can't do the release.
In conflict now
The `` in `~/.kontena/certs/.pem` must be the same address you use to login, if it's an IP address, it has to be something like `172.12.51.1.pem`. So if you're doing something...