14 Dec 2010

Implementation Options with RPost Encryption – TLS, PKI, 128-bit PDF?

Author:

SENDER    —— Path A —–>   SERVICE PROVIDER (RPOST)  —– Path B —–>   RECIPIENT

With RPost service, the sender can opt to send encrypted messages by Message-Level Encryption, Transport Layer Encryption, or a combination. As such, there are four scenarios for encrypted transmission.  In all cases, the encrypted message is delivered direct to the recipient’s desktop; RPost never requires the recipient to visit a website to collect their email.

Encrypted Data Flow Path A Path B
Desktop-to-Desktop Message-Level Encryption Message-Level Encryption
Desktop-to-Server Message-Level Encryption Transport Layer Encryption
Server-to-Desktop Transport Layer Encryption Message-Level Encryption
Server-to-Server Transport Layer Encryption Transport Layer Encryption


OPTIONS FOR PATH A: SENDER TO PROVIDER

A sender using RPost’s Outlook plug-in has two administrative settings that we will discuss here.  Once set by the sender or sender IT department, they are transparent from a user perspective. When sending Registered Email messages with the encryption option selected, the message will either:

Read more: Implementation Options with RPost Encryption – TLS, PKI, 128-bit PDF?