• Browser
  • Mail
  • News
  • Community
  • About
Register Login
HomeBlogsForumThemesContributeSocial

Vivaldi

  • Browser
  • Mail
  • News
  • Community
  • About

Navigation

    • Home
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. Desktop
    3. Vivaldi for Linux
    4. pub key missing

    pub key missing

    Vivaldi for Linux
    7
    11
    1.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      michaa7
      last edited by

      Todays update throws an error:

      coHolen:18 https://repo.vivaldi.com/archive/deb stable Release.gpg [833 B]
      Fehl:17 https://repo.vivaldi.com/snapshot/deb stable Release.gpg
        Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 62993C724218647E
      de_text
      

      Was working some hours ago!

      ???

      nomadic
      N
      1 Reply Last reply
      Reply Quote 1
      • nomadic
        N
        nomadic Soprano @michaa7
        last edited by

        @michaa7 Maybe the discussion here will help: https://forum.vivaldi.net/post/636731

        1 Reply Last reply Reply Quote 1
        • unclemez
          U
          unclemez
          last edited by

          Well same here to,
          here's the ouput

          File 'repomd.xml' from repository 'vivaldi' is signed with an unknown key '62993C724218647E'. Continue? [yes/no] (no)

          I'm running opensuse tumbleweed if more info need i believe this is not fixed soon will lead many people to write or cal you for resolution

          1 Reply Last reply Reply Quote 0
          • M
            michaa7
            last edited by michaa7

            @nomadic

            No, it does not.

            Ich have manually created my-vivaldi-snapshot.list and my-vivaldi.list for some reason (I would need to browse my postings here to remeber why, but it was to circumvent some automatic reconfiguring of some settings ... which I hate!)

            This seems to prevent to update the key! None of the commands worked. But guys, there has to be a way of updating without overwriting whatever a user likes to keep unchanged! (I will have alook why I need my own list, I'm too tired now.)

            Thanks, your help is appreciated.

            becm
            B
            1 Reply Last reply
            Reply Quote 0
            • becm
              B
              becm @michaa7
              last edited by becm

              @michaa7 the Vivaldi install will create a .list file and register (global) signing keys and defend this setting (to a degree) by utilizing a cron script. This will not be prevented completely by just adding a manual repository config.

              Due to that, chances are high the update to the latest version already got applied (generated file with working repo setup).
              But apt will throw an error for the (second) config file with a bad signature key state.

              That manual file is (likely) superfluous and destined to break if you are using a signed-by setting with a key file that does not get updated regularly (the exact state described in discussion linked by @nomadic).

              So either delete your manual (duplicated) .list file, remove the explicit signed-by setting or update the keyfile referenced in signed-by with (at least) the current KEY08 package signing key.

              IGVazquez
              I
              M
              2 Replies Last reply
              Reply Quote 2
              • IGVazquez
                I
                IGVazquez @becm
                last edited by

                @becm I removed the explicit signed-by setting, but I had the issue yet. Where the .list file is saved?

                becm
                B
                1 Reply Last reply
                Reply Quote 0
                • becm
                  B
                  becm @IGVazquez
                  last edited by

                  @IGVazquez you can print an overview of all files and settings regarding Vivaldi package sources via

                  $ grep -nr repo.vivaldi.com /etc/apt/sources.list.d
                  

                  There should only be a single entry in the file named vivaldi.list which is kept active by the Vivaldi install routines and cron job.

                  @michaa7 also see /opt/vivaldi/cron/vivaldi if you want to keep the cron script from touching existing repository entries.
                  If you want more/less, you'll have to forgo Vivaldi package installation and use a standalone file extraction approach.

                  1 Reply Last reply Reply Quote 1
                  • M
                    michaa7 @becm
                    last edited by

                    @becm said in pub key missing:
                    ...

                    ... or update the keyfile referenced in signed-by with (at least) the current KEY08 package signing key.

                    How would I do that?

                    ~$ grep -nr repo.vivaldi.com /etc/apt/sources.list.d
                    /etc/apt/sources.list.d/my-vivaldi-snapshot.list:3:deb [arch=amd64 signed-by=/usr/share/keyrings/my-vivaldi-snapshot-archive-keyring.gpg] https://repo.vivaldi.com/snapshot/deb/ stable main
                    /etc/apt/sources.list.d/my-vivaldi.list:3:deb [arch=amd64 signed-by=/usr/share/keyrings/my-vivaldi-archive-keyring.gpg] http://neutower:3142/repo.vivaldi.com/stable/deb/ stable main
                    /etc/apt/sources.list.d/vivaldi.list:3:deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
                    
                    1 Reply Last reply Reply Quote 0
                    • M
                      michaa7
                      last edited by michaa7

                      ok, understood:

                      # sh -c 'echo "deb [arch=amd64,armhf signed-by=/etc/apt/trusted.gpg.d/packages.vivaldi.gpg] https://repo.vivaldi.com/archive/deb stable main" > /etc/apt/sources.list.d/my-vivaldi.list' 
                      
                      

                      did the trick. Error gone. Thanks!

                      1 Reply Last reply Reply Quote 0
                      • Cqoicebordel
                        C
                        Cqoicebordel Ambassador
                        last edited by Cqoicebordel

                        For posterity, I solved the same issue with :

                        # Remove all previous keys
                        sudo rm /etc/apt/trusted.gpg.d/vivaldi-*
                        # Download the latest key
                        wget -qO- https://repo.vivaldi.com/archive/linux_signing_key.pub | gpg --dearmor | sudo dd of=/etc/apt/trusted.gpg.d/vivaldi.gpg
                        

                        Note that I didn't touch the repos list files, nor added a "signed-by".

                        Edit : As I'm stumbling upon my own post months later to fix the same thing, I'll add two commands to do things properly :

                        apt-key list | grep -B4 vivaldi
                        

                        to list the current key in place and

                        sudo apt-key del "XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX"
                        

                        to delete them properly.

                        1 Reply Last reply Reply Quote 1
                        • DoctorG
                          D
                          DoctorG Soprano
                          last edited by DoctorG

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          Loading More Posts
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes
                          Reply
                          • Reply as topic
                          Log in to reply
                          • 1 / 1
                          • First post
                            Last post

                          Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.

                          Copyright © Vivaldi Technologies™ — All rights reserved. Privacy Policy | Code of conduct | Terms of use | Vivaldi Status