hvqzao / burp-wildcard Goto Github PK

Is it possible to move extension from wildcard to main page by tab moving

Hello there,

The extension in question behaves incorrectly by hiding Dashboard tab of Burpsuite's where it shouldn't do that. Also, there are times when the extension after disabling it's work through it's options pane - does not unhide that Dashboard tab leaving Burp without it completely, until restarted.

I have to stay on Burpsuite Pro v.2.1.03 or else wildcard stops functioning and doesn't redraw all tabs underneath the wildcard (or only selectively).

Please see the screenshots from a working v2.1.03 and wildcard (v1.0.5).

And when updating Burp and using latest version of both

Hello there,

I'm using your burp-wildcard plugin which gets it's simple job fine. But unfortunately, since Burp has updated their UI interface in 1.7 version - they have separated Options tab into two of them: Project Options and User Options. Therefore, your burpTabs array located at: BurpExtender.java:59 is no longer relevant and should get updated :)

Could you update your extension?

Hi,

In some releases recently, they don't use the Nimbus/Dracula theme, etc anymore. Only Dark/Light available now. Can you fix this problem, please? Thanks.

If I use the new v1.05 it breaks on non-default "Look and Feel" darcula , the dark color version. However nimbus works without problem. If I switch the theme the UI crashes and produces the following error:
java.lang.ClassCastException: javax.swing.JLabel cannot be cast to burp.e75
at burp.b0t.getTitleAt(Unknown Source)
at javax.swing.plaf.basic.BasicTabbedPaneUI.paintTab(Unknown Source)
at javax.swing.plaf.basic.BasicTabbedPaneUI.paintTabArea(Unknown Source)

    at javax.swing.plaf.basic.BasicTabbedPaneUI.paint(Unknown Source)
    at javax.swing.plaf.ComponentUI.update(Unknown Source)
    at javax.swing.JComponent.paintComponent(Unknown Source)
    at javax.swing.JComponent.paint(Unknown Source)
    at javax.swing.JComponent.paintChildren(Unknown Source)
    at javax.swing.JComponent.paint(Unknown Source)
    at javax.swing.JComponent.paintToOffscreen(Unknown Source)
    at javax.swing.BufferStrategyPaintManager.paint(Unknown Source)
    at javax.swing.RepaintManager.paint(Unknown Source)
    at javax.swing.JComponent._paintImmediately(Unknown Source)
    at javax.swing.JComponent.paintImmediately(Unknown Source)
    at javax.swing.RepaintManager$4.run(Unknown Source)
    at javax.swing.RepaintManager$4.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionP

rivilege(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.RepaintManager.prePaintDirtyRegions(Unknown Source)
at javax.swing.RepaintManager.access$1200(Unknown Source)
at javax.swing.RepaintManager$ProcessingRunnable.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionP
rivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

As shown in the figure, the functions such as external proxy do not respond, and only the wildcard can be used normally

Burp's new version 2022.9.5 has unfortunately broken this extension (https://portswigger.net/burp/releases/professional-community-2022-9-5).

The changelog mentions a lot of API modifications, which might be the cause for this. No errors are printed in the console/extender area which might help understand what's going on. Any idea if this extension is still compatible with the new API?

Thank you!