Menu

#127 Incompatible format of encrypted data (no lienfeeds in encrypted data, especially in header)

New
nobody
None
Medium
Defect
2012-06-28
2012-01-31
Anonymous
No

Originally created by: Zoli197...@googlemail.com

What steps will reproduce the problem?
1. write an email in k9
2. encrypt using APG
3. try to decrypt at the recipient's side (outlook/PGP Desktop)->email seems to be broken

What is the expected output?
decrypted email.

What do you see instead?
email cannot be decrypted by the recipient. Recipient sees an un-decrypted email. The format of the encrypted data seems to be unusual. Line feeds between the data blocks aren't there as they would be with other PGP software, also no line feed in header behind the "begin PGP message"-string and the version info string, as well as at the end before the "end PGP message" string. GnuPG and PGP Desktop don't recognize any encrypted message, unless it's been sent in the correct format. Here is an example:

With APG (current incompatible behaviour):
-----BEGIN PGP MESSAGE----- Version: APG v1.0.8 <encrypted data, no linefeeds> -----END PGP MESSAGE-----

result at the recipient's side for this format:
GnuPG says "maybe 'quoted printable' in armor part"
PGP Desktop says message is broken.

Encrypted message should look like:
-----BEGIN PGP MESSAGE----- <cr+linefeed>
Version: APG v1.0.8 <cr+linefeed>
<encrypted data, cr+linefeeds between the blocks>
-----END PGP MESSAGE-----

result at the recipient's side for this format:
message can be decrypted with PGP Desktop and GnuPG.

What version of the product are you using? APG v1.0.8, K9-mail 4.001

On what operating system?
Android 2.3.4 on Motorola Milestone 2

Please provide any additional information below.
see above

Discussion

  • Anonymous

    Anonymous - 2012-02-10

    Originally posted by: johannes...@googlemail.com

    Probably a duplicate of issue 116 but with more information,

     
  • Anonymous

    Anonymous - 2012-02-10

    Originally posted by: Zoli197...@googlemail.com

    Sorry, but still nowhere to find an announcement, when an update will come out to patch this issue. Are you still working on it? Please note, that PGP Desktop as THE standard software, which is mostly used in companies, I strongly recommend you to take it as a reference for compatibility. So, as long as APG is unable to handle encryption exactly like PGP Desktop does, it is simply not a working PGP solution for adroid.

    Zoli

     
  • Anonymous

    Anonymous - 2012-02-27

    Originally posted by: harald.k...@gmail.com

    Even if sending encrypted email from K9 to K9 (sender equals receiver) AGP can't decrypt own encrypted message stating error about broken message. In second screen where error and message are presented manual insertation of 2 cr+lf after (...)Version: APG v1.0.8 makes decryption possible afterwards.

     
  • Anonymous

    Anonymous - 2012-02-27

    Originally posted by: Zoli197...@googlemail.com

    For me, only one cr+lf after version info was enough to get the message decryptable.

    Zoli

     
  • Anonymous

    Anonymous - 2012-06-28

    Originally posted by: enzom...@gmail.com

    Still present in APG 1.0.8, K-9 4.009. However, everything works if K-9 is set for sending text messages rather than HTML (in Account settings -> Sending mail).

    Basically the problem is that the ASCII-armoured PGP message is simply embedded in the HTML MIME message part without proper conversion to HTML (particularly, without adding at the end of each line the tag "<br />" (or at least placing it within <pre> ... </pre> tags):

    ------JVRUJL5CVDEMNAZ651V0FLU0FY2YBO
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: 8bit

    -----BEGIN PGP MESSAGE-----
    Version: APG v1.0.8

    hQIMA+EiaPJRIvEFAQ//eCy07R+ZXqV93NIu++MrQg4tz7tSEncc5U2GFGmo6CeT
    D9niZ5+UXQfPrsZyWc1HTqTV9dgG4JFmW65qyDP1WZCdTpQPbljpDgx7DnxmW5Tz
    wh4+HLs6tECpquYxzUjLVtUtGHKIj37oUIHPHyXYZe1C5LSHd5+5A145EDD+Opg6
    kwpYfY7cpmGWa2VIVymQeBZGIscCoP8Z/IFx+VHOPhJI68xaW7q9gWzH7s2LEzhg
    HodZidF9SUneTjsOeYgq4BVFoQ7sHFndG5kwI/k3A7rZzNM63ZPeOXUi3RrhKjad
    scpkmbAz3vqzhEMdUlFK6YmnB74y+ycsjBGQqRDjXcQRjEM5uqLD6ySvDNaH8eI0
    m7pkU5BwRR7EJFFs62mwpCj8sZvoeVv3nZAGMsF9YevHNkpr/LaF92nQPTL2Bem/
    5vHTS1k8abzLXQ8OwCXAcwZl0R6dbNMXPQrPU3pUUBP3Udn0JXBew9qnLoR+SRL2
    odpzj0GLbt+Gktmff8BirbcpTO/Q8eSrikTjTsbi7okNwP1m3EEd7NBzM1sMs42L
    V70nlcMkEozYBRi/geri4IoWlJT2H890Fnubi2SCa/suQ7jmvZtRnkJygiQkIopy
    zd11HlQRWZQb9HwiYSXu5Ord5jrAI0acB/q+B30/cYJcKJEbrMR0i6v84NkmdfTS
    wdgBoxpLZDolpaVAJPszUAqghQErPi2ChWyqnoreFPgOZ9uzKOfhZ6qW26zbaYUG
    MnJxTJRDdSa4AcIdEe1WOyx4B6sziFK17WT93JQhe8z7YDP3LFrfcOk5nKQ0f1Y9
    x3UgC1A0DeYq5X2AMv/ABpdMoyKdJF78dK4DNAY1l4ZAOgvht8+nZT15FMRLJAd+
    k+Z27ftimmVY5duMYwyfNEJPA1Hficmv8DJiiZvRYUHxxb9XQx99fg3XdkY8ca3q
    KWWFPmPkKx61NyUK0Syqt/FOag/6YMz+ik2OkN7enwEijl/4N2Jby9ZoCbR6tEYo
    7IBinO+OaEL/xlst+F7/c0dAkcaYq8eHrr6w0jcQ/T2/rj0tnPhodJ9laWYPSMLH
    11MwQ6omIadu6Spr2SlzyhR6/eEGsl1B98CJysEuWlPNMMSLjaDp1LUwsgWgl4dQ
    qE2OXjsJKymww4+S28k2HxAgQNQBWg20wjtonGH7+SPaK7hlMn91fwiYN0mPO2e4
    6f4ZTY7g+YymsaS9P80lbwoEnC9k0V9RX6Wjj/yQ97jGPsXI6t2Kl5JT59pXmXdi
    Ahh8HSU77XtW6KmpainEGJv9G59RyXdSjW6O6JupiOQ9TQgW/V2lokunMhCYH08k
    AEvWnQ5ehYEsSOUVS40QQWcAeXNudLr5ym9RC1QVEzVT/Wl7B7KId0H2EZtyVXcm
    1w7i4qxt2kCAtMm7Ie5IFZe3582SLJNwAQPgdFaPUPb/mygKOI9+tLclxT/3eHBf
    hxpenRnjySGyGvS8PJOQG+Li17mqz0EY1M5hYAWNRsRA0MQ/yq07diyGZlv2Dtu4
    jjOcPoK1Gzw0bM05U+WaVuOCDQyTb5sU+B8Lm0G7OxQkxPEOAUfpWFgD
    =4Y/0
    -----END PGP MESSAGE-----

    ------JVRUJL5CVDEMNAZ651V0FLU0FY2YBO--

    Enzo

     

Log in to post a comment.

MongoDB Logo MongoDB