Skip to main content

Secure messaging

Process Secure Messaging
  1. The sender writes an eMail online and sends it over a secure SSL-connection to the secure messaging server.
  2. The recipient is notified through a normal eMail that a secure message is waiting for delivery on the secure server. The recipient is invited to download the message through a link.
  3. The sender provides the recipient with a message unlock code. The code is required in order to access the pending message. If the recipient has already been in contact with the sender through secure messaging server and has registered, this step is not required.
  4. The secure message and confidential documents such as contracts, business plans, resumes or loan documents can then be accessed with the message unlock code and downloaded.
MUC (Message Unlock Code)
A MUC is a message password and protects a message sent to a new communication partner from being seen by erroneous recipients and is used to initiate trust. If a message is sent to a new recipient, the system generates a random MUC. The sender communicates the MUC to the recipient by using another communication channel than email, e.g. personally, by phone or SMS for security reasons (Out-of-band). With the MUC the recipient gets access to the secure message and confidential documents and can download them. If the recipient has already been in contact with the sender through secure messaging and is enrolled, a MUC is no longer required.

Trust management


Secure Messaging relies on the method of the dynamic personal web of trust. This method synthesizes the authentication approach of web of trust, known from PGP, with the advantages of hierarchical structures, known from centralized PKI systems. Those combined with certificates provide high quality of electronic identities. This approach focuses on the user and allows for immediate and personal bootstrapping of trust, respectively revocation.
Labels:

Comments

Post a Comment

Popular posts from this blog

Android Developer Learning Resource

Developing In Eclipse, with ADT http://developer.android.com/guide/developing/eclipse-adt.html Signing Your Applications http://developer.android.com/guide/publishing/app-signing.html Compile and sign with Eclipse ADT To create a signed and aligned .apk in Eclipse: Select the project in the Package Explorer and select File > Export . Open the Android folder, select Export Android Application, and click Next . The Export Android Application wizard now starts, which will guide you through the process of signing your application, including steps for selecting the private key with which to sign the .apk (or creating a new keystore and private key). Complete the Export Wizard and your application will be compiled , signed , aligned , and ready for distribution. DroidDraw is a graphical user interface (GUI) builder for the Android platform http://code.google.com/p/droiddraw/
10 comments
Read more

RMO programming

http://msdn2.microsoft.com/en-us/library/ms151819.aspx SQL Server Express does not include SQL Server Agent, which is typically used to run replication agents. If you use a pull subscription (in which agents run at the Subscriber), you must synchronize the subscription using Windows Synchronization Manager or RMO. For more information, see the following topics: Windows Synchronization Manager RMO programming: How to: Synchronize a Pull Subscription (RMO Programming) Replication does not support the Run As Normal User (RANU) feature of SQL Server Express. For more information about this feature, see the SQL Server Express documentation.
Post a Comment
Read more