Test report for GpgOL 1.3.0-beta85 (2015-11-04)

using Gpg4win-2.2.6 under Windows 7 32bit with Outlook 2016 32bit

1.1.a (sign and verify Using PGP/MIME)

Signing an E-Mail with OpenPGP and sending it worked without a noticeable problem.

Receiving an signed E-Mail and read it worked without a problem.

To verify the received E-Mail, it was necessary to open it (The E-Mail) in an external window (double click) and navigate to the GpgOL-tab afterwards, which is inconvenient. It was not possible to verify the E-Mail inside the Outlook-Main-Window (missing option).

Expected:

• The E-Mail may be verified automatically
• The E-Mail may be verified from inside the main window (GpgOL-tab)

Result:

• Successful verification from an external window

1.1.b (encrypt and decrypt Using PGP/MIME)

Encrypting an E-Mail with OpenPGP and sending it worked without a noticeable problem.

Receiving an encrypted E-Mail worked without a problem.

Once clicked on an encrypted E-Mail, Kleopatra pops-up automatically and notified about the decryption.

It is necessary to close the popped-up window manually.

Expected:

• decryption of the encrypted mail automatically.

Result:

• decryption of the encrypted mail automatically (there was a suddenly appearing Kleopatra-window which needed attention, which is slightly inconvenient)

1.1.c (sign/encrypt and decrypt/verify using PGP/MIME)

Sign an E-Mail and encrypt it afterwards (using PGP/MIME).

• No noticeable problems when sending the E-Mail
• The decryption works as expected.
• The verification does not seem to work: After clicking on "verify" Kleopatra mentions that the decryption was successful, but does not react to the verification-request

Expected:

• The Program always Signs and Encrypts in the correct order
• The encryption process works similar to 1.1.b
• The verification process works similar to 1.1.a

Result:

• behavior depends on the order of actions. Can work when choosing the options in the right order, but Kleopatra will inform about errors.

The attachment was not encrypted.

1.2.a (sign and verify Using S/MIME)

(like in 1.1.a) Signing an E-mail with S/MIME and sending it worked without a noticeable problem.

Receiving a signed E-Mail and reading it worked without a noticeable problem.

The process of verifying failed. The error message was "Decryption failed: no data" (sic: (German) "Entschlüsseln fehlgeschlagen: Keine Daten.") The detailed error decryption was "input error: unknown error" (sic: (German) "Eingabefehler: Unbekannter fehler").

Expected:

• The E-Mail may be verified successful.
• The E-Mail may be verified from inside the main window (GpgOL-tab)

Result:

• The verification failed. Error message: "Decryption failed: no data" | "input error: unknown error"

noticed:

• After clicking on "sign" pinentry pops up. After entering the password, the E-Mail-window will vanish behind the main-window.

1.2.b (encrypt and decrypt Using S/MIME)

Encrypting an E-Mail with S/MIME and sending it worked without a noticeable problem.

Receiving an encrypted E-Mail worked without a problem.

Once clicked on an encrypted E-Mail, Outlook will display the encrypted text. It was necessary to open the E-Mail in an external window, navigating to the GpgOL tab and hitting "decrypt". The decrytion process itself worked without a problem.

Expected:

• decryption of the encrypted mail automatically.

Result:

• Outlook displayed the encrypted text.
• Decryption worked after manual navigating to according options in the GpgOL-tab on an external window.

1.2.c (sign/encrypt, and decrypt/verify using S/MIME)

• Signing and encrypting the E-Mail works without errors.
• Decryption works like in 1.2.b
• Verification fails like in 1.2.a

The attachment was not encrypted.

Expected:

• Similar behavior to 1.2.a and 1.2.b
• As mentioned in 1.1.c, the program is expected to sign and encrypt in the correct order.

Result:

• Similar behavior to 1.2.a and 1.2.b

2.1.a (Sign in KMail, Verify in Outlook, PGP/MIME)

Imported the required certificate (B) on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust".

Set up a new E-Mail Account in KMail e35 and added the openPGP-Key in the Identity section.

Signed an E-Mail using the according option on KMail and send them to the outlook client.

Signing and sending worked without problems. Receiving and verifying the E-Mail worked without a problem.

The verification process started immediately after clicking on the E-Mail. The verification was also repeatable using the way described in 1.1.a.

Expected:

• Automatic verification once clicked the E-Mail

Result:

• Automatic verification once clicked the E-Mail (Kleopatra still seems to be in the way)
• Manual verification is also possible

2.1.b (Sign in KMail, Verify in Outlook, PGP/MIME)

Imported the required certificate on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust" for both keys (source an target).

Encrypted a new E-Mail using the according option on KMail and send them to the outlook client.

Encrypting and sending worked without problems. Receiving and decrypting the E-Mail worked without a problem.

The decrpting started immediately after clicking on the E-Mail, similar to the result of 1.1.b.

Expected:

• Automatic verification once clicked the E-Mail

Result:

• Automatic verification once clicked the E-Mail (Kleopatra still seems to be in the way)

Test matrix for 1.3-beta85

Legend:
? = untested
x = passed
F = failed

+++ Tested GpgOL version: 1.3.0-beta85 (2015-11-04) +++

• ⁰) Currently no Entry in the test plan
• ¹) To verify and decrypt an email, it is necessary to open it in an external window, which is inconvenient.
• ²) Kleopatra is popping up and requires attention (which is slightly inconvenient)
• ³) Seems to work when choosing the right combination of actions, but throws errors and is susceptible for "wrong usage"