aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
diff options
context:
space:
mode:
authorzotlabs <mike@macgirvin.com>2018-02-20 17:18:08 -0800
committerzotlabs <mike@macgirvin.com>2018-02-20 17:18:08 -0800
commit02575f46a6d288cd2c1168bbbe52be2c7863cb46 (patch)
tree3682f555485d18cf96b4eb32e36d439b22ae38a0 /include/zot.php
parent441cdeff3fb93a23fbaea7e19caca622fcc9c45d (diff)
downloadvolse-hubzilla-02575f46a6d288cd2c1168bbbe52be2c7863cb46.tar.gz
volse-hubzilla-02575f46a6d288cd2c1168bbbe52be2c7863cb46.tar.bz2
volse-hubzilla-02575f46a6d288cd2c1168bbbe52be2c7863cb46.zip
move the zot6 delivery to zot_fetch where it makes more sense. Exhaustively hand tested.
Diffstat (limited to 'include/zot.php')
-rw-r--r--include/zot.php7
1 files changed, 6 insertions, 1 deletions
diff --git a/include/zot.php b/include/zot.php
index 10550fd69..d28e584a1 100644
--- a/include/zot.php
+++ b/include/zot.php
@@ -1152,7 +1152,12 @@ function zot_process_response($hub, $arr, $outq) {
* @brief
*
* We received a notification packet (in mod_post) that a message is waiting for us, and we've verified the sender.
- * Now send back a pickup message, using our message tracking ID ($arr['secret']), which we will sign with our site
+ * Check if the site is using zot6 delivery and includes a verified HTTP Signature, signed content, and a 'msg' field,
+ * and also that the signer and the sender match.
+ * If that happens, we do not need to fetch/pickup the message - we have it already and it is verified.
+ * Translate it into the form we need for zot_import() and import it.
+ *
+ * Otherwise send back a pickup message, using our message tracking ID ($arr['secret']), which we will sign with our site
* private key.
* The entire pickup message is encrypted with the remote site's public key.
* If everything checks out on the remote end, we will receive back a packet containing one or more messages,