Question

Droplet console (Ubuntu 18.04.3) error: 'PKCS#7 signature not signed with a trusted key'

Posted September 24, 2019 950 views
DigitalOcean Control Panels 
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.

  1. https://i.imgur.com/ogXXllp.png
  2. https://www.google.com/search?q=pkcs%237+signature+not+signed+with+a+trusted+key
  3. https://unix.stackexchange.com/questions/455189/pkcs7-signature-not-signed-with-a-trusted-key
  4. https://askubuntu.com/questions/1031375/pkcs-signature-error-warnings-running-dmesg-on-ubuntu-mate-18-04
  5. 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

Add a comment
johnnyutahh
By:
johnnyutahh
Add a comment

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.

6 answers
KDSys September 24, 2019

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

Reply Report
  • johnnyutahh September 24, 2019

    Wait… @KFerdinandov - the email I received from this thread (I’m presuming it’s your original post?) reads as the following. Hence I was running the apt install nvidia-driver-396 commands per my gist. But… now I see you’re asking a different question in your answer-post.

    ——– Forwarded Message ——–
    Subject: [DigitalOcean Community] KFerdinandov mentioned you in an answer
    Date: Tue, 24 Sep 2019 16:50:11 +0000
    From: community@noreply.digitalocean.com

    […]

    Hi @johnnyutahh,

    before we resort to DO’s DEV team, can you please and try to install the proper drivers:

    sudo apt install nvidia-driver-396

    (version can vary, of course)

    It opens up a graphical interface inside your terminal at some point and proposes to add a signing MOK key. After I did that reboot the droplet and enter the key when prompted.

    Kind regards,
    Kalin

    Reply Report
    • KDSys September 25, 2019

      Hi @johnnyutahh,

      that was for another question in the forum which is why I eddited my comment.

      Having said that, what I mean is to try and use the terminal on your personal computer. If you try to 

      ssh root@ip

      Do you still get the same error?

      Reply Report
      • johnnyutahh September 26, 2019

        I’ve answered this in my posts below, made yesterday, at the end of this question thread.

        (I’ve put a lot of effort into responding to DO’s requests - it’s been rather inefficient. If this continues, I might request a phone. A phone call would have taken about 5 mins of conversation.)

        Reply Report
johnnyutahh September 24, 2019
Reply Report
johnnyutahh September 24, 2019

I also ran a few more apt upgrade-ish commands, reran your nvidia install command with the same problem. I added all this to the above gist.

(Give it a few mins and the raw gist content will update after a refresh, after the github servers cycle through the content cache. And/or just add a / to the end of the gist URL, and you’ll see the updates.)

Reply Report
johnnyutahh September 24, 2019

[I can not edit my original message post in this thread - that’s no fun. 😕 ]

Reply Report
johnnyutahh September 24, 2019

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

Reply Report
johnnyutahh September 27, 2019

(ping)

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help