Project

General

Profile

Bug #10571

The 'application/pgp-keys' MIME type has bad application associations

Added by anonym over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
11/17/2015
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

E.g. .key files are associated with gedit in the browser, and Archive Manager in GNOME. Because of the former, the 'Importing an OpenPGP key from a website' scenario is broken in Tails/Jessie since it expects the browser to want to open .key files with "Import Key".


Related issues

Related to Tails - Bug #10889: shared-mime-info associates .key files with LibreOffice Writer in GNOME Files Resolved 01/09/2016
Related to Tails - Bug #15213: Tails signing key can't be imported from Seahorse with the default key files filter Resolved 01/22/2018
Blocks Tails - Feature #7563: Update the automated test suite for Jessie ISO images Resolved 11/26/2014 01/15/2016

Associated revisions

Revision d0d539f5 (diff)
Added by anonym over 3 years ago

Update the rest of torified_browsing.feature's images.

... for Debian Jessie. Now all scenarios except 'Importing an OpenPGP
key from a website' passes, due to

Refs: #10571

Revision ee418a6a (diff)
Added by intrigeri over 3 years ago

Manually associate application/pgp-keys with Seahorse's "Import Key" application.

Closes: #10571

I can't reproduce this in my Tor Browser on current sid, so I don't see
where I could report it. Hence added a "XXX: Stretch" so that we check
if we can remove it next time we upgrade to a new Debian release.

History

#1 Updated by anonym over 3 years ago

  • Blocks Feature #7563: Update the automated test suite for Jessie ISO images added

#4 Updated by anonym over 3 years ago

  • Target version set to Tails_1.8

#5 Updated by intrigeri over 3 years ago

  • Assignee set to intrigeri
  • Priority changed from Normal to High

I will try with a newer shared-mime-info.

#7 Updated by intrigeri over 3 years ago

Probably not relevant, but on current sid I see:

$ mimetype  wiki/src/tails-signing.key
wiki/src/tails-signing.key: application/x-iwork-keynote-sffkey
$ mimetype --debug -a wiki/src/tails-signing.key
> Data dirs are: /home/intrigeri/.local/share, /usr/share/gnome, /usr/local/share, /usr/share
> Checking inode type
> Checking globs for basename 'tails-signing.key'
> Checking for extension '.key'
wiki/src/tails-signing.key: application/x-iwork-keynote-sffkey
> Checking all magic rules
> Value "-----BEGIN PGP PUBLIC KEY BLOCK-----" at offset 36 matches at /usr/share/mime/magic line 337
wiki/src/tails-signing.key: application/pgp-keys
> File exists, trying default method
wiki/src/tails-signing.key: text/plain

And on current feature/jessie, the file manager says that /usr/share/doc/tails/website/tails-signing.key is "Apple Keynote 5 presentation (application/x-iwork-keynote-sffkey)", which indeed opens with Archive Manager by default.

So I'm not sure it's a problem of associating application/pgp-keys with a particular application, it seems rather like it's a matter of detecting the correct MIME type to start with, no?

#8 Updated by intrigeri over 3 years ago

http://cgit.freedesktop.org/xdg/shared-mime-info/tree/NEWS says that shared-mime-info 1.3 "Add Apple Keynote 5 mime-type". On Tails 1.7 we're installing 1.3-1~bpo70+1, and in the file manager I see the same results as those reported above on Jessie. I think this confirms that I was on the wrong track: the browser is passed the correct MIME type, but indeed the association between that MIME type and Seahorse is broken on Jessie. anonym was right :)

#9 Updated by intrigeri over 3 years ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 20

The application we want in /usr/share/applications/seahorse-pgp-keys.desktop and on current feature/jessie:

$ grep pgp-keys /usr/share/applications/mimeinfo.cache
application/pgp-keys=seahorse-pgp-keys.desktop;

... which sounds right.

Anyway, manually adding application/pgp-keys=seahorse-pgp-keys.desktop to /etc/gnome/defaults.list solves the problem. I'm going to do that and spend some reasonable amount of time reproducing / reporting the problem where it should be.

#10 Updated by intrigeri over 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100

#11 Updated by intrigeri over 3 years ago

  • Assignee deleted (intrigeri)
  • Target version changed from Tails_1.8 to Tails_2.0

#12 Updated by intrigeri over 3 years ago

  • Related to Bug #10889: shared-mime-info associates .key files with LibreOffice Writer in GNOME Files added

#13 Updated by intrigeri over 1 year ago

  • Related to Bug #15213: Tails signing key can't be imported from Seahorse with the default key files filter added

Also available in: Atom PDF