Welcome to the mailbox user forum
 

GPG Inbox Encryption fails to recognise ASCII code

Old Chatterhand shared this problem 42 hours ago
Published

PGP inbox encryption stopped at the day my public key expired. To be expected, I guess.

I then pasted the ASCII code of a current public key into the key field of the respective inbox encryption field and, no matter what I use for key generation, mailbox complains with a cryptic error message: "Open-Xchange: line 322: error: pgp_encrypt command: invalid ASCII armor for key 1/*number or digits*: invalid tail line. Open-Xchange: error: validation failed."

It is highly unlikely that two different gpg key generation software applications (Thunderbird and GPGTools) would generate any uncommon ASCII format.

Anybody´s got an idea what I am doing wrong? I opened the exported public key with a text editor and copy and pasted to mailbox Inbox Encryption Public Key Field. Then that error appears. I mean to recall that I did exactly that the last time I entered my public key into that public key field of Inbox Encryption.

Replies (1)

photo
1

Update: shortly after I posted this, inbox encryption worked again. So that´s a bit of mailbox Voodoo.
I noticed that there were two filter rules, named "Ihr verschlüsseltes Postfach" present when copy and paste failed. I then logged in via a second browser and tried to paste the ASCII code there. The first browsers login session then somehow corrupted and an error box appeared atop the mailbox UI that I was not logged in any more. However, pasting the exact same code into the field via the second browser did not lead to the previously observed problem. I then logged out, went back to the first browser, logged back in, went to GPG Inbox, deleted the code, disabled encrypted inbox, did some other work within the mailbox web mailer, went back to PGP Inbox, pasted the exact same code, enabled encrypted inbox and it worked. There were also no more the two identical filter rules any more - but just one, for the encrypted inbox.
I used the Safari browser on MacOS when the issue occurred. The second browser was Firefox. However, the last attempt to paste exactly the same ASCII code that previously lead to error in Safari, now worked flawlessly in Safari. Which is why I tend to attribute this error to some hiccups at mailbox.

photo
1

Hi Old Chatterhand,

thank you very much for posting your findings here. We will look into the matter, so far we can't see any hiccups in our backend, but we will get back to you as soon as we have more information. Until then, we ask for a little more patience.

With kind regards

Your mailbox support


---

Useful Links:

d9e15a7fee470fb66af17115c3a43886

photo
Leave a Comment
 
Attach a file