Log when an incoming dialback verification request is an invalid key for our domain

Sat, 25 Oct 2008 20:34:21 +0100

author
Matthew Wild <mwild1@gmail.com>
date
Sat, 25 Oct 2008 20:34:21 +0100
changeset 168
744fafa8b700
parent 167
c51246bc679d
child 169
92768120b717

Log when an incoming dialback verification request is an invalid key for our domain

core/stanza_router.lua file | annotate | diff | comparison | revisions
--- a/core/stanza_router.lua	Sat Oct 25 18:21:34 2008 +0100
+++ b/core/stanza_router.lua	Sat Oct 25 20:34:21 2008 +0100
@@ -114,9 +114,12 @@
 				print(tostring(origin.to_host), tostring(origin.from_host))
 				-- FIXME: Grr, ejabberd breaks this one too?? it is black and white in XEP-220 example 34
 				--if attr.from ~= origin.to_host then error("invalid-from"); end
-				local type = "invalid";
+				local type;
 				if s2s_verify_dialback(attr.id, attr.from, attr.to, stanza[1]) then
 					type = "valid"
+				else
+					type = "invalid"
+					log("warn", "Asked to verify a dialback key that was incorrect. An imposter is claiming to be %s?", attr.to);
 				end
 				origin.send(format("<db:verify from='%s' to='%s' id='%s' type='%s'>%s</db:verify>", attr.to, attr.from, attr.id, type, stanza[1]));
 			elseif stanza.name == "result" and origin.type == "s2sin_unauthed" then

mercurial