Question
Droplet console (Ubuntu 18.04.3) error: 'PKCS#7 signature not signed with a trusted key'
- Posted on September 24, 2019
- DigitalOceanControl Panels
Asked by Johnny Utahh
PKCS#7 signature not signed with a trusted key
DigitialOcean- can you eliminate this error msg/symptom?
I’m seeing this (seemingly) error message on my Droplet consoles - screenshot of 1 console below. I have not surveyed all the Droplets to see if they exhibit this msg. The 2 droplets I did survey (by running their console) did both exhibit this error, and both are running Ubuntu 18.04.3 (coincidentally or not).
Weblink #1 below shows a screenshot of one of these consoles. The rest of the weblinks show results of brief web searching I did hunting for accounts of similar experiences. I’m not trying to “solve” this; rather, I’m just giving DO a jumpstart on the search.
- https://i.imgur.com/ogXXllp.png
- https://www.google.com/search?q=pkcs%237+signature+not+signed+with+a+trusted+key
- https://unix.stackexchange.com/questions/455189/pkcs7-signature-not-signed-with-a-trusted-key
- https://askubuntu.com/questions/1031375/pkcs-signature-error-warnings-running-dmesg-on-ubuntu-mate-18-04
- https://www.linuxquestions.org/questions/linux-hardware-18/ubuntu-18-04-lts-desktop-pkcs-7-signature-not-signed-with-a-trusted-key-nvidia-gpu-4175646607/
Thanks for any help, ~J
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
(ping)
So, trying to answer the revised (?) question quoted below:
When I ssh login to node110 I believe I do not see the same error. I added this ssh session (from macOS Terminal.app) to the top of the gist found at the weblink above; once again, wait for github cache to update, or just add a
/#to the end of the URL to get the updated content.I’m hoping this addresses what you mean by “connect via your terminal.”
~J
---- quote of request ---- Hi @johnnyutahh,
before we resort to DO’s DEV team, can you please let me know if the error is experienced when you connect via your terminal rather than the DO console?
Kind regards, Kalin
[I can not edit my original message post in this thread - that’s no fun. 😕 ]