Signed-off-by: Penny Leach <penny@mjollnir.org>

this is useful for importing data over mnet, but also potentially in the
future when we can import leap data into existing user accounts
Signed-off-by: Penny Leach <penny@mjollnir.org>

- Breaking up of the validation into two stages:
    - Performed by the importtransport object, before moving files
      around
    - Performed by the import class, after the files are transported

To this end I changed the importtransport objects to take the
importqueue record (or a fake one) in their constructor, so they have
the same data available as the importer would.
Signed-off-by: Penny Leach <penny@mjollnir.org>

This commit includes:

- Moved a lot of logic out of admin/users/add.php to the various plugins
- Moved around unzipping and detecting files into the transport layers
- Refactored a lot of transport code into the base class

I tested:

- Adding a user from a leap2a xml file
- Adding a user from a leap2a zip file
- Importing non leap (straight files) data over mnet
Signed-off-by: Penny Leach <penny@mjollnir.org>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Signed-off-by: Penny Leach <penny@mjollnir.org>

Went through and changed all the throws of ImportException to correctly
pass the importer (or null) as the first argument
Signed-off-by: Penny Leach <penny@mjollnir.org>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

This patch adds two fields in the Networking configuration page: the SHA1
fingerprint of the certificate and the MD5 fingerprint of the certificate.
This can be used to verify certificates. See feature request #3431
Signed-off-by: Juan Segarra Montesinos <juan.segarra@si.uji.es>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Although it isn't propogated up to the UI, it'll end up in Mahara's error log, which will help debugging.

The class of errors this catches is mainly to do with having invalid ssl keys on the remote host.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>
(cherry picked from commit c1451f16)

we can no longer compare int and text fields without an explicit cast.
this should maybe be ported to stable.

Moodle outcomes integration: view submission/release to/from mnet hosts; hidden view access keys; export of additional artefacts with views

http://www.mahara.org/node/406

so we can bounce the user back over mnet with a better url

This has happened once for someone on an ubuntu hardy box (probably
broken-depenency related).

(cherry picked from commit 7e09936f)

[#3000] quote a string value in a query for 8.3 compliance. Chris Bandy and Piers Harding, patch doctored by me for readability.
(cherry picked from commit 0dc059b9)

If we're decrypting a message and the signature doesn't validate, try grabbing a new public key from the remote host and verifying the message again.

This is the last bit of functionality required before all given cases of Moodle/Mahara keyswap work. Yay!

When decrypting responses to our XMLRPC requests, consider an older key to be OK. This fixes keyswap when both hosts have different keys (!)
(cherry picked from commit cfde5bfd)

When we receive a request using an old key, respond with a signed and encrypted message with our new key.

This makes it so that when Moodle and Mahara are set up to network, and Mahara's key expires, Moodle can successfully grab the new key.

Modify get_keypair so that it can be called from outside the class, and the regenerate parameter being true actually regenerates a key.

When an CryptException occurs when sending an XMLRPC request (because the response was using an old key for example), fail in a nicer manner.

Update the message for the primary cause of this (old key) so it's more obvious in the logs.

The MNET code uses this a bit.