Created attachment 28519 [details]
A sample file encrypted with Chiasmus
Chiasmus is a encryption standard developed by the German Federal
Office for Information Security ("Bundesamt für Sicherheit in der
The encrypted files usually have an extension of .xia and start with
the three letters "XIA1". I attached a sample file for your reference.
Currently the bubble pop up in konqueror says "Unkown".
The chiasmus keys are usually stored in a file with an extension of
.xis and have the following header:
*** Aendern Sie diese Datei nicht direkt!! ***
(i.e. two lines with those characters, the key itself starts in the
next line) and are currently by konqueror recogonized as "diff files".
I confirmed these information with the developer of Chiasmus.
For more information either see
with the english version or
which also shows the Linux version but is only in German.
A (German) wikipedia article is also available under
I initially filed this to the Debian konqueror package whose maintainer asked me to carry it upstream where David Faure requested it to be filed here.
Created attachment 32905 [details] [review]
The attached patch adds the MIME types application/x-chiasmus-encrypted and application/x-chiasmus-key based on the information in the report.
Missing a test file, and an entry in the test suite.
I already added a sample file to the report, what kind of "test file" is required?
(In reply to comment #3)
> I already added a sample file to the report, what kind of "test file" is
You need both an xsi and an xia file in the test suite, and you need to add them to tests/list. See the HACKING file for details.
Created attachment 40746 [details]
A sample chiasmus key
A sample key as requested (containing one comment)
(In reply to comment #4)
> (In reply to comment #3)
> > I already added a sample file to the report, what kind of "test file" is
> > required?
> You need both an xsi and an xia file in the test suite, and you need to add
> them to tests/list. See the HACKING file for details.
I now uploaded an sample key (.xis). Unfortunately I don't know what kind of test suite of HACKING you are refering to.
As stated in my original bug report, I was asked by David Faure from KDE to file the bug here, I have (not yet) done more that that and it would be great if you could apply the necessary changes (I can provide you additional information as needed, of course).
The HACKING file is here:
And it has explanations on how to add files to the test suite.
Created attachment 89288 [details]
Updated patch to the proposed one by Daniel Leidert
I tried to understand the format of the file you specified. Given my limited understanding (I mainly want konqueror to detect these files, cf. the initial description) I believe the following two lines should suffice:
Examplekey.xis application/x-chiasmus-key ooo
VTestdatei.pdf.xia application/x-chiasmus-encrypted ooo
I applied Daniels patch from Comment1, ran autogen.sh and make freedesktop.org.xml
The make command gave errors and I updated the patch (which I attached to this report).
However, even then test-mime-data does not really produce sensible results (to me).
Now I ran make in the top level directory of shared-mime-info.
Using the settings for test/lists given above I get as output:
Examplekey.xis, 'name' test: expected application/x-chiasmus-key, got application/octet-stream
Examplekey.xis, 'data' test: expected application/x-chiasmus-key, got text/plain
Examplekey.xis, 'file' test: expected application/x-chiasmus-key, got text/plain
Is that ok?
I would be glad if you could query me about the missing information (especially those which you cannot find in the bug log) and update the relevant files yourself. I'm really guessing now whats to be done / updated.
Created attachment 89289 [details] [review]
Updated patch to the one from Daniel (2nd try)
I noticed another typo in the patch from Daniel. Please consider the latest one (from 20:48 UTC).
Now make in the top directory of shared-mime-info no longer complains, i.e. I think it looks fine. (But please verify)
It would be great if you could integrate the patch, the test files and the updated tests/list in your repository.