Its two set of methods, getter and setter methods helps to get all the information or modify the message if needed. IHttpRequestResponse:Īll the HTTP messages captured with the Burp or Burp extension have details associated with it like host, port, request, response etc. Using the callbacks interface, we can send requests to repeater/intruder, send alerts to the Alert tab, issue arbitrary requests and retrieve responses. Hence, it can call any of the methods described in the IBurpExtenderCallbacks. If BurpExtender (an implementation of IBurpExtender) implements this method, it receives an implementation of the IBurpExtenderCallbacks interface. The IBurpExtender interface has a method “registerExtenderCallbacks”. ![]() It links the Burp tools like Repeater, Proxy, Intruder, etc., with the BurpExtender class with the help of functions like sendToRepeater, sendtoIntruder, etc. ![]() Its main purpose is to pass callback methods to the IBurpExtender interface implementation class (BurpExtender). This class is supposed to implement the IBurpExtender interface.Īfter BurpExtender is loaded during startup, whenever Burp Proxy receives a client request or server response it invokes the function “processProxyMessage” (if declared in the BurpExtender class).Īnother important interface to note while working on BurpSuite extension is the IBurpExtenderCallbacks interface. When we start Burp, it looks for a class BurpExtender in its classpath to load and instantiate. It can be implemented by declaring a public class called “BurpExtender”. All the Burp extensions provide an implementation of this class by implementing at least one method of IBurpExtender interface. This interface forms the base of the BurpSuite extension. We will try and understand what each interface does and then in the later part of the article, we will see how various interfaces interact with the help of an example.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |