Snare tanner communication

[rnehra01]

fix #100
This is how return value from tanner look like :

Case 1 (where you need to return the page normally)
detection = {
		type : 1
        }
Case 2 (inject payload in the page)
detection = {
		type : 2,
payload = {
		page : ‘/vuln.php’,
		value : ‘<script>alert(1)</script>’
		headers : {
				new_header : ‘new_header_value’
			     }
	      }
        }
Case 3 (where input cause some error so return related to the type of error produced 
  e.g if input takes more time than expected then return 50X) 
detection = {
		type : 3,
                payload = {
		                  status_code : 500/504
                                 } 
       }

To make communication more systematic, return value type from each emulator is fixed i.e dict(value='', page=True/False) (if page=False then payload won't be injected on any page but on a new page)

[afeena]

As I understood from code, status_code in detection['payload'], am I right?

[rnehra01]

Yes, you're right.

[afeena]

Can we return any status info about error?

[rnehra01]

Do we need that because usually that will be present in logs where it was present? And even if get it then how will we use it, as suppose we return 500 error to the client then sending any other data won't be needed.

[afeena]

In case of tanner error, snare should works normally (e.g. return index page). Imagine the situation, when we use snare with default tanner and we don't have access to tanner's log. Something happens, but we don't know what.

[rnehra01]

Ok, but this thing is when you want to give a particular status_code intentionally to give positive results for the attack, though I'll add that too for normal tanner error.