AArnott / IronPigeon
Messages are signed for authenticity, encrypted for confidentiality, and transmitted indirectly so that eavesdroppers find it difficult or impossible to establish whether two parties have even communicated, what was communicated or how much was communicated.
This project includes libraries that implement the protocol and a message relay web service project that provides the cloud component necessary for passing messages.
There are a small collection of objects that work together to provide the functions required to send and receive messages. These objects can be manually and individually instantiated, and properties set on them to point to the other objects you've created. Or you can rely on MEF to do this work for you.
When targeting .NET 4.0, use MEF as it is found in the framework under the System.ComponentModel.Composition namespace. When targeting .NET 4.5 or Windows 8, you should use the MEF "v2" found in the Microsoft.Composition NuGet package. The code below assumes you're using the MEF framework from NuGet. Most fundamental IronPigeon services are in the core IronPigeon assembly, so we add that entire assembly to the MEF catalog:
You will need to configure some of these services (setting properties, etc.) and other services you'll call methods on to actually send and receive messages. You can acquire these services directly from the container using:
