[SOLVED] Re: How add key of 3rd party repo?
> > curl -fsSL https://download.jitsi.org/jitsi-key.gpg.key | gpg -o
> > /usr/share/keyrings/jitsy-key.gpg --dearmor
> > No error messages!
>
> I notice that this is not the same filename as the one in the quote
> further above. The original had 'jitsi-keyring.gpg', and this one has
> 'jitsy-key.gpg' - that's two differences.
>
> (Also, this command line isn't 'including the prompt'.)
>
This might be an error by me, as there are several names in the different
documentations. I rechecked and the names are identical. Maybe a typo here in
this mail.
> <snip>
>
> > And the entry in /etc/apt/sources.list.d/jitsi-stable.list is this:
> > deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg]
> > https://download.jitsi.org stable
> This is referencing the original filename, not the one you used in your
> "no error messages" command.
>
Yes, this is the required entry of one of the documentations in the web. As I
mentioned before: There are several different instructions, and they are
different, as one is for Ubuntu, Ubuntu+Debian and Debian.
> Does that file exist? If so, what contents does it have? Are they the
> same as the one in the other filename?
Yes, it does exist.
>
> > Should be all ok, but it isn't.
>
> If the file named in the sources.list entry doesn't exist (or has the
> wrong contents), then I think that would explain it.
Yes, you are correct, but I rechecked. There is "jitsi-keyring.gpg.key", which
is from the original jitsi-site, and there is also "jitsi-key.gpg", which is
from the jitsi-*keyring*.deb (on the original jitsi-meet website), which I
testwise downloaded manually and installed using dpkg.
At the moment, there is only one key existent: jitsi-keyring.gpg.key, which is
acually resides in /usr/share/keyrings/.
But I found the reason!
The eys are set "rw- --- ---", so they could not read.
This adds another problem: Looks like gpg or sq is setting wrong rights.
Several minutes ago I discovered another issue: /usr/bin/dpkg was set
to "rwx r-- r--", what is also wrong. As I did not change this, it must have
been changed by some upgrade. Had this issue already in 2014 (with a
mediathekview problem, same reason),
I suppose, we can safely close this. Thanks for your help, again laerned
something.
Best regards
Hans
Reply to: