Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-29 09:16:22 -05:00
Code Issues Packages Projects Releases Wiki Activity

added line breaks

Browse Source
This commit is contained in:
praschdorff 2018-02-21 23:43:35 +01:00 committed by GitHub
parent 00e76d21fc
commit ad738ca2c6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
configuration/multimedia.md
View File

@ -67,7 +67,9 @@ Check the signature of the signing key (still in the AppVM where you downloaded
This should look like: This should look like:
> [user@my-untrusted ~]$ `gpg --with-fingerprint spotify.pubkey` > [user@my-untrusted ~]$ `gpg --with-fingerprint spotify.pubkey`
> pub 4096R/341D9410 2017-07-25 Spotify Public Repository Signing Key <tux@spotify.com> > pub 4096R/341D9410 2017-07-25 Spotify Public Repository Signing Key <tux@spotify.com>
> Key fingerprint = 0DF7 31E4 5CE2 4F27 EEEB 1450 EFDC 8610 341D 9410 > Key fingerprint = 0DF7 31E4 5CE2 4F27 EEEB 1450 EFDC 8610 341D 9410
You can (and should) lookup the fingerprint on at least one (or more) keyservers as the above information might be outdated. You can (and should) lookup the fingerprint on at least one (or more) keyservers as the above information might be outdated.
@ -120,8 +122,11 @@ Check the signature of the signing key (still in the AppVM where you downloaded
This should look like: This should look like:
> [user@my-untrusted ~]$ `gpg --with-fingerprint videolan.pubkey` > [user@my-untrusted ~]$ `gpg --with-fingerprint videolan.pubkey`
> pub 2048R/B84288D9 2013-08-27 VideoLAN APT Signing Key <videolan@videolan.org> > pub 2048R/B84288D9 2013-08-27 VideoLAN APT Signing Key <videolan@videolan.org>
> Key fingerprint = 8F08 45FE 77B1 6294 429A 7934 6BCA 5E4D B842 88D9 > Key fingerprint = 8F08 45FE 77B1 6294 429A 7934 6BCA 5E4D B842 88D9
> sub 2048R/288D4A2C 2013-08-27 > sub 2048R/288D4A2C 2013-08-27
You can (and should) lookup the fingerprint on at least one (or more) keyservers as the above information might be outdated. You can (and should) lookup the fingerprint on at least one (or more) keyservers as the above information might be outdated.
@ -172,10 +177,15 @@ Check the signature of the signing key (still in the AppVM where you downloaded
This should look like: This should look like:
> [user@my-untrusted ~]$ `gpg --with-fingerprint google.pubkey` > [user@my-untrusted ~]$ `gpg --with-fingerprint google.pubkey`
> pub 4096R/D38B4796 2016-04-12 Google Inc. (Linux Packages Signing Authority) > pub 4096R/D38B4796 2016-04-12 Google Inc. (Linux Packages Signing Authority)
> <linux-packages-keymaster@google.com> > <linux-packages-keymaster@google.com>
> Key fingerprint = EB4C 1BFD 4F04 2F6D DDCC EC91 7721 F63B D38B 4796 > Key fingerprint = EB4C 1BFD 4F04 2F6D DDCC EC91 7721 F63B D38B 4796
> sub 4096R/640DB551 2016-04-12 [expires: 2019-04-12] > sub 4096R/640DB551 2016-04-12 [expires: 2019-04-12]
> sub 4096R/997C215E 2017-01-24 [expires: 2020-01-24] > sub 4096R/997C215E 2017-01-24 [expires: 2020-01-24]
You can (and should) lookup the fingerprint on at least one (or more) keyservers as the above information might be outdated. You can (and should) lookup the fingerprint on at least one (or more) keyservers as the above information might be outdated.