Nicolas Oliver

Having Docker Content Trust enabled is recommended by [docker-bench-security](https://github.com/docker/docker-bench-security/blob/master/tests/4_container_images.sh#L106) and the [Center for Internet Security (CIS) Docker Benchmark](https://www.cisecurity.org/benchmark/docker/). So anybody following those guidelines will run into this problem with an...

I run into this issue as well. The problem seems to be Fedora. There are some hints about what may be happening here https://www.mail-archive.com/[email protected]/msg08846.html > I haven't looked very far...

I found a workaround to the key generation step, but run into the same problem when I try to `ssh` using the pkcs11 module: The workaround is to use `p11tool`...

Trying to set the CKA_LABEL with `p11tool` fails with unsupported feature :( ```shell [root@28e9da3af1d5 workdir]# p11tool --set-label=label 'pkcs11:model=IoT%20Software%20TPM;manufacturer=MSFT;serial=0000000000000000;token=label;id=%33%38%36%62%34%65%65%39%33%66%32%36%65%31%62%62;type=public' > my.pem note: assuming --login for this operation. Token 'label' with URL...

Not sure if there is a lib problem. This is how I reproduce it: On the same host, create both Fedora and Ubuntu images, and run the test: **test.sh** ```bash...

Still failing with the latest `fedora:33` image, using openssh-8.4 And it is still working with the latest `ubuntu:20.04` image, using openssh-client-8.2 Filed a bug in Fedora's Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1919007

Fix is on the way for Fedora 34. There is a test package for Fedora 33. You get a free PKCS11 URI at the end of the RSA key! ```shell...

It was Fedora's openssh. The fix is here https://src.fedoraproject.org/rpms/openssh/pull-request/16 (it now accepts empty labels) ~~I wanted to test if the trailing PKCS11 URI cause problems to stablish the ssh connection.~~...

This looks like a similar https://vmware.github.io/vic-product/assets/files/html/1.5/vic_vsphere_admin/ts_imagestore_error.html error. But in this case, the error message is different, and I did not assigned any container to run yet.

Nothing in the KB articles https://kb.vmware.com/s/global-search/%40uri#q=Error%20getting%20image%20store&t=Knowledge&sort=relevancy&f:@commonproduct=[vSphere%20Integrated%20Containers]