paul@11 | 1 | Introduction
|
paul@11 | 2 | ------------
|
paul@11 | 3 |
|
paul@11 | 4 | MoinMessage provides a library for creating, signing, encrypting, decrypting,
|
paul@12 | 5 | and verifying PGP/GPG content in Python along with mechanisms for updating
|
paul@11 | 6 | MoinMoin Wiki instances with such content such that contributors can be
|
paul@11 | 7 | identified from their PGP signatures and such details used to authenticate
|
paul@11 | 8 | their contributions.
|
paul@11 | 9 |
|
paul@11 | 10 | Configuring GPG for a Wiki
|
paul@11 | 11 | --------------------------
|
paul@11 | 12 |
|
paul@37 | 13 | Initialise a homedir for GPG and configure it using filesystem ACL (access
|
paul@37 | 14 | control list) properties:
|
paul@11 | 15 |
|
paul@12 | 16 | ./scripts/init_wiki_keyring.sh WIKI WEBUSER
|
paul@12 | 17 |
|
paul@12 | 18 | Here, WIKI should be replaced by the top-level Wiki instance directory, and
|
paul@12 | 19 | WEBUSER should be the name of the user under which the Web server operates.
|
paul@12 | 20 |
|
paul@12 | 21 | Note that this script may need re-running after the homedir has been changed
|
paul@12 | 22 | by gpg operations as gpg likes to remove permissions from various files.
|
paul@11 | 23 |
|
paul@11 | 24 | To be in any way useful, signing keys must be made available within this
|
paul@11 | 25 | homedir so that incoming messages can have their senders verified.
|
paul@11 | 26 |
|
paul@11 | 27 | To see the keys available to you in your own environment:
|
paul@11 | 28 |
|
paul@11 | 29 | gpg --list-keys --with-fingerprint
|
paul@11 | 30 |
|
paul@11 | 31 | The full fingerprints are used when defining a user mapping in the Wiki, and
|
paul@11 | 32 | the --with-fingerprint option is used to show them. Otherwise, only the last
|
paul@11 | 33 | eight characters of the fingerprints are shown.
|
paul@11 | 34 |
|
paul@11 | 35 | Export the public key used when signing messages from your own environment:
|
paul@11 | 36 |
|
paul@11 | 37 | gpg --armor --output 1C1AAF83.asc --export 1C1AAF83
|
paul@11 | 38 |
|
paul@11 | 39 | Import the key into the Wiki's GPG homedir:
|
paul@11 | 40 |
|
paul@11 | 41 | gpg --homedir wiki/gnupg --import 1C1AAF83.asc
|
paul@11 | 42 |
|
paul@11 | 43 | For the Wiki to receive encrypted data, a key for the Wiki must be created:
|
paul@11 | 44 |
|
paul@11 | 45 | gpg --homedir wiki/gnupg --gen-key
|
paul@11 | 46 |
|
paul@12 | 47 | For the Wiki environment to be able to use the key, password access must be
|
paul@12 | 48 | disabled. This can be done by either not specifying a password or by removing
|
paul@12 | 49 | it later using the --edit-key option.
|
paul@12 | 50 |
|
paul@11 | 51 | Export the Wiki's key for encrypting messages sent to the Wiki:
|
paul@11 | 52 |
|
paul@11 | 53 | gpg --homedir wiki/gnupg --armor --output 0891463A.asc --export 0891463A
|
paul@11 | 54 |
|
paul@11 | 55 | This exported key can now be imported into your own environment:
|
paul@11 | 56 |
|
paul@11 | 57 | gpg --import 0891463A.asc
|
paul@11 | 58 |
|
paul@11 | 59 | Configuring the Wiki
|
paul@11 | 60 | --------------------
|
paul@11 | 61 |
|
paul@11 | 62 | In the Wiki configuration, define the following settings:
|
paul@11 | 63 |
|
paul@11 | 64 | moinmessage_gpg_homedir
|
paul@11 | 65 | This sets the path to the homedir initialised above.
|
paul@11 | 66 |
|
paul@11 | 67 | moinmessage_gpg_users_page (optional, default is MoinMessageUserDict)
|
paul@11 | 68 | This provides a mapping from key fingerprints to Moin usernames.
|
paul@11 | 69 |
|
paul@12 | 70 | moinmessage_gpg_signing_users_page (optional, default is MoinMessageSigningUserDict)
|
paul@12 | 71 | This provides a mapping from Moin usernames to key fingerprints.
|
paul@12 | 72 |
|
paul@12 | 73 | moinmessage_gpg_recipients_page (optional, default is MoinMessageRecipientsDict)
|
paul@12 | 74 | This provides a mapping from recipients to remote URLs and key fingerprints.
|
paul@37 | 75 | Each user can define the named page as a subpage of their own home page.
|
paul@37 | 76 | If no such personal mapping exists, a common mapping exists relative to the
|
paul@37 | 77 | site root.
|
paul@12 | 78 |
|
paul@20 | 79 | moinmessage_reject_messages_without_dates (optional, default is True)
|
paul@20 | 80 | This causes messages sent to a Wiki using the PostMessage action to be
|
paul@20 | 81 | rejected if date information is missing.
|
paul@20 | 82 |
|
paul@40 | 83 | moinmessage_static_files (optional, may refer to the built-in htdocs directory)
|
paul@40 | 84 | This explicitly defines the path to static resources used by Moin, enabling
|
paul@40 | 85 | such resources to be attached to messages. When set, the path must refer to
|
paul@40 | 86 | the htdocs directory (possibly renamed) containing the different theme
|
paul@40 | 87 | resource directories, together with the robots.txt and favicon.ico files.)
|
paul@40 | 88 |
|
paul@38 | 89 | For signature verification to function, the following needs to be added:
|
paul@38 | 90 |
|
paul@38 | 91 | from MoinMoin.auth.pgp import PGPAuth
|
paul@38 | 92 |
|
paul@38 | 93 | This should import an authentication handler installed when the MoinMessage
|
paul@38 | 94 | software is installed as an extension package.
|
paul@38 | 95 |
|
paul@38 | 96 | Within the configuration class itself, the auth setting needs to be updated to
|
paul@38 | 97 | include PGPAuth in the list of registered handlers. For example:
|
paul@38 | 98 |
|
paul@38 | 99 | auth = [MoinAuth(), PGPAuth()]
|
paul@38 | 100 |
|
paul@38 | 101 | This would permit the traditional Moin authentication and add signature-based
|
paul@38 | 102 | authentication so that messages can be accepted by the Wiki.
|
paul@38 | 103 |
|
paul@12 | 104 | Fingerprints and Keys
|
paul@12 | 105 | ---------------------
|
paul@12 | 106 |
|
paul@12 | 107 | All fingerprints mentioned in the various configuration pages must exclude
|
paul@12 | 108 | space characters - that is, the letters and digits must appear together in a
|
paul@12 | 109 | continuous block of text - and refer to keys available in the Wiki homedir.
|
paul@12 | 110 |
|
paul@11 | 111 | The Fingerprint-to-Username Mapping
|
paul@11 | 112 | -----------------------------------
|
paul@11 | 113 |
|
paul@12 | 114 | The mapping from fingerprints to usernames typically defined by the
|
paul@12 | 115 | MoinMessageUserDict page is a WikiDict having the following general format:
|
paul@11 | 116 |
|
paul@11 | 117 | fingerprint:: username
|
paul@11 | 118 |
|
paul@12 | 119 | Each fingerprint corresponds to a key used by a person wanting to send
|
paul@12 | 120 | messages to the Wiki to sign such messages.
|
paul@11 | 121 |
|
paul@11 | 122 | Each username must correspond to a registered user in the Wiki.
|
paul@11 | 123 |
|
paul@12 | 124 | The Username-to-Signing Key Mapping
|
paul@12 | 125 | -----------------------------------
|
paul@12 | 126 |
|
paul@12 | 127 | The mapping from usernames to fingerprints typically defined by the
|
paul@12 | 128 | MoinMessageSigningUserDict page is a WikiDict having the following general
|
paul@12 | 129 | format:
|
paul@12 | 130 |
|
paul@12 | 131 | username:: fingerprint
|
paul@12 | 132 |
|
paul@12 | 133 | Each fingerprint corresponds to a key available in the Wiki's GPG homedir
|
paul@12 | 134 | generated for the purpose of signing the specified user's messages. Such a key
|
paul@12 | 135 | is not the same as one used by a person to send messages to the Wiki since
|
paul@12 | 136 | only the public key used to verify such messages should be known to the Wiki.
|
paul@12 | 137 |
|
paul@12 | 138 | The Recipients Mapping
|
paul@12 | 139 | ----------------------
|
paul@12 | 140 |
|
paul@12 | 141 | The mapping from recipients to remote URLs and fingerprints typically defined
|
paul@12 | 142 | by the MoinMessageRecipientsDict page is a WikiDict having the following
|
paul@12 | 143 | general format:
|
paul@12 | 144 |
|
paul@27 | 145 | recipient:: location ... [ fingerprint ]
|
paul@27 | 146 |
|
paul@27 | 147 | Locations are specified as follows:
|
paul@27 | 148 |
|
paul@27 | 149 | type=value
|
paul@27 | 150 |
|
paul@28 | 151 | Where the type is "page", the accompanying value must be a page name
|
paul@28 | 152 | indicating a page that provides a message store that will accept messages.
|
paul@12 | 153 |
|
paul@27 | 154 | Where the type is "url", the accompanying value must be a URL that must itself
|
paul@27 | 155 | refer to a resource that can accept MoinMessage content.
|
paul@12 | 156 |
|
paul@27 | 157 | Where a location of type "url" has been given, a fingerprint must accompany
|
paul@27 | 158 | this information in order to encrypt messages sent to the specified resource.
|
paul@27 | 159 |
|
paul@27 | 160 | Each fingerprint corresponds to a key used by the Wiki to encrypt messages and
|
paul@27 | 161 | by the remote site (as identified by the URL) to decrypt messages.
|
paul@12 | 162 |
|
paul@11 | 163 | Quick Start: Signing, Encrypting and Sending Messages
|
paul@11 | 164 | -----------------------------------------------------
|
paul@11 | 165 |
|
paul@11 | 166 | To send a message signed and encrypted to a resource on localhost:
|
paul@11 | 167 |
|
paul@12 | 168 | python tests/test_send.py 1C1AAF83 0891463A http://localhost/wiki/ShareTest \
|
paul@16 | 169 | collection update 'An update to the Wiki.' 'Another update.'
|
paul@11 | 170 |
|
paul@11 | 171 | Here, the first identifier is a reference to the signing key (over which you
|
paul@11 | 172 | have complete control), and the second identifier is a reference to the
|
paul@11 | 173 | encryption key (which is a public key published for the Wiki).
|
paul@11 | 174 |
|
paul@11 | 175 | This needs password protection to be removed from the secret key in the Web
|
paul@12 | 176 | server environment. It also uses a modified trust model when invoking gpg in
|
paul@12 | 177 | order to avoid complaints about the identity of the sender during encryption.
|
paul@11 | 178 |
|
paul@11 | 179 | Below, the mechanisms employed are illustrated through the use of the other
|
paul@11 | 180 | test programs.
|
paul@11 | 181 |
|
paul@11 | 182 | Signing
|
paul@11 | 183 | -------
|
paul@11 | 184 |
|
paul@11 | 185 | Prepare a message signed with a "detached signature" (note that this does not
|
paul@11 | 186 | seem to be what gpg calls a detached signature with the --detach-sig option):
|
paul@11 | 187 |
|
paul@16 | 188 | python tests/test_message.py collection update 'An update to the Wiki.' \
|
paul@16 | 189 | 'Another update.' \
|
paul@11 | 190 | | python tests/test_sign.py 1C1AAF83
|
paul@11 | 191 |
|
paul@11 | 192 | The complicated recipe based on the individual operations is as follows:
|
paul@11 | 193 |
|
paul@16 | 194 | python tests/test_message.py collection update 'An update to the Wiki.' \
|
paul@16 | 195 | 'Another update.' \
|
paul@11 | 196 | > test.txt \
|
paul@11 | 197 | && cat test.txt \
|
paul@11 | 198 | | gpg --armor -u 1C1AAF83 --detach-sig \
|
paul@11 | 199 | | python tests/test_sign_wrap.py test.txt
|
paul@11 | 200 |
|
paul@11 | 201 | Encryption
|
paul@11 | 202 | ----------
|
paul@11 | 203 |
|
paul@11 | 204 | Prepare a message with an encrypted payload using the above key:
|
paul@11 | 205 |
|
paul@16 | 206 | python tests/test_message.py collection update 'An update to the Wiki.' \
|
paul@16 | 207 | 'Another update.' \
|
paul@11 | 208 | | python tests/test_encrypt.py 0891463A
|
paul@11 | 209 |
|
paul@11 | 210 | The complicated recipe based on the individual operations is as follows:
|
paul@11 | 211 |
|
paul@16 | 212 | python tests/test_message.py collection update 'An update to the Wiki.' \
|
paul@16 | 213 | 'Another update.' \
|
paul@11 | 214 | > test.txt \
|
paul@11 | 215 | && cat test.txt \
|
paul@11 | 216 | | gpg --armor -r 0891463A --encrypt --trust-model always \
|
paul@11 | 217 | | python tests/test_encrypt_wrap.py
|
paul@11 | 218 |
|
paul@11 | 219 | Note that "--trust-model always" is used only to avoid prompting issues.
|
paul@11 | 220 |
|
paul@11 | 221 | Signing and Encrypting
|
paul@11 | 222 | ----------------------
|
paul@11 | 223 |
|
paul@12 | 224 | Sign and encrypt a message:
|
paul@11 | 225 |
|
paul@16 | 226 | python tests/test_message.py collection update 'An update to the Wiki.' \
|
paul@16 | 227 | 'Another update.' \
|
paul@11 | 228 | | python tests/test_sign.py 1C1AAF83 \
|
paul@11 | 229 | | python tests/test_encrypt.py 0891463A
|
paul@11 | 230 |
|
paul@11 | 231 | The complicated recipe based on the individual operations is as follows:
|
paul@11 | 232 |
|
paul@16 | 233 | python tests/test_message.py collection update 'An update to the Wiki.' \
|
paul@16 | 234 | 'Another update.' \
|
paul@11 | 235 | > test.txt \
|
paul@11 | 236 | && cat test.txt \
|
paul@11 | 237 | | gpg --armor -u 1C1AAF83 --detach-sig \
|
paul@11 | 238 | | python tests/test_sign_wrap.py test.txt \
|
paul@11 | 239 | | gpg --armor -r 0891463A --encrypt --trust-model always \
|
paul@11 | 240 | | python tests/test_encrypt_wrap.py
|
paul@11 | 241 |
|
paul@11 | 242 | Posting a Message
|
paul@11 | 243 | -----------------
|
paul@11 | 244 |
|
paul@11 | 245 | To post a signed and/or encrypted message, output from the above activities
|
paul@11 | 246 | can be piped into the following command:
|
paul@11 | 247 |
|
paul@12 | 248 | python tests/test_post.py http://localhost/wiki/ShareTest
|
paul@11 | 249 |
|
paul@11 | 250 | Here, the resource "/wiki/ShareTest" on localhost is presented with the
|
paul@11 | 251 | message.
|
paul@16 | 252 |
|
paul@32 | 253 | Fetching Messages
|
paul@32 | 254 | -----------------
|
paul@32 | 255 |
|
paul@32 | 256 | To fetch messages from a message store associated with a page, the following
|
paul@32 | 257 | command can be used:
|
paul@32 | 258 |
|
paul@32 | 259 | python tests/test_fetch.py 1C1AAF83 0891463A http://localhost/wiki/ShareTest \
|
paul@32 | 260 | RETR
|
paul@32 | 261 |
|
paul@32 | 262 | This should retrieve all messages from the store associated with the
|
paul@32 | 263 | "/wiki/ShareTest" resource on localhost.
|
paul@32 | 264 |
|
paul@16 | 265 | The Message Format
|
paul@16 | 266 | ------------------
|
paul@16 | 267 |
|
paul@16 | 268 | Messages are MIME-encoded and consist of one or more update fragments. Where
|
paul@16 | 269 | the "Update-Type" header is present and set to a value of "collection", a
|
paul@16 | 270 | multipart message describes as many updates as there are parts. Otherwise,
|
paul@16 | 271 | only a single update is described by the message.
|
paul@16 | 272 |
|
paul@16 | 273 | For each update, the "Update-Action" header indicates the action to be taken
|
paul@16 | 274 | with the update content. Where it is absent, the content is inserted into the
|
paul@16 | 275 | Wiki page specified in the request; where it is present and set to "replace",
|
paul@16 | 276 | the content replaces all content on the Wiki page; where it is set to "store",
|
paul@16 | 277 | the content is stored in a message store associated with the Wiki page.
|
paul@16 | 278 |
|
paul@16 | 279 | Each update may describe multiple representations of some content by employing
|
paul@16 | 280 | a multipart section containing parts for each of the representations.
|
paul@16 | 281 | Alternatively, a single message part may describe a single representation.
|