1.1 --- a/README.txt Wed Oct 16 16:11:30 2013 +0200
1.2 +++ b/README.txt Wed Oct 16 16:50:48 2013 +0200
1.3 @@ -96,6 +96,10 @@
1.4 their fingerprint-to-user mapping (see moinmessage_gpg_users_page) to be
1.5 able to receive messages from this wiki.
1.6
1.7 + moinmessage_gpg_relays_page (optional, default is MoinMessageRelayDict)
1.8 + Where message relaying is specified for a recipient, the relay name will be
1.9 + looked up in the dictionary provided by this page.
1.10 +
1.11 moinmessage_gpg_recipients_page (optional, default is MoinMessageRecipientsDict)
1.12 This provides a mapping from recipients to remote URLs and key fingerprints.
1.13 Each user can define the named page as a subpage of their own home page.
1.14 @@ -219,8 +223,12 @@
1.15 Where the type is "url", the accompanying location must be a URL that must
1.16 itself refer to a resource that can accept MoinMessage content.
1.17
1.18 -Where a type of "url" has been given, a fingerprint must accompany this
1.19 -information in order to encrypt messages sent to the specified resource.
1.20 +Where the type is "relay", the accompanying location is an identifier that
1.21 +must be defined in the relays mapping (see below) and yield a URL that can
1.22 +accept MoinMessage content.
1.23 +
1.24 +Where a type of "url" or "relay" has been given, a fingerprint must accompany
1.25 +this information in order to encrypt messages sent to the specified resource.
1.26
1.27 Each fingerprint corresponds to a key used by the wiki to encrypt messages and
1.28 by the remote site (as identified by the URL) to decrypt messages.
1.29 @@ -229,6 +237,18 @@
1.30 MoinMessageRecipientsDict unless overridden by the configuration, as a subpage
1.31 of their own home page.
1.32
1.33 +The Relays Mapping
1.34 +------------------
1.35 +
1.36 +The mapping from relay identifiers to remote URLs defined by the
1.37 +MoinMessageRelayDict page is a WikiDict having the following general format:
1.38 +
1.39 + relay:: url
1.40 +
1.41 +The URL must be able to accept MoinMessage content, and it will typically be
1.42 +configured so that the user or entity accepting relayed content on the remote
1.43 +site can store such content for later propagation or retrieval.
1.44 +
1.45 Quick Start: Signing, Encrypting and Sending Messages
1.46 -----------------------------------------------------
1.47