Errors

[marten4n6]

Errors

[Marten4n6]

Run the server first then run the launcher.

[marvic2409]

Run the server (start.py) and the launcher is what?

[Marten4n6]

Explain how you're getting that error? Payloads are sent to the background so you won't be able to see anything after the launcher has been run and the payload is successfully loaded.

[marvic2409]

Well at first I was using my rubber ducky and I wasn't getting any result, so I decided to paste in the code (Starting with echo) into terminal and seeing the output.

[Marten4n6]

urllib2.URLError: <urlopen error [Errno 61] Connection refused>

Not sure what to tell you, it can't connect to the server to ask for a payload.
Maybe you specified the wrong IP/port (remake a launcher), if you're outside a local network make sure you forward your ports.

[marvic2409]

What port should I use, Im currently using 1200

…

On Tue, Jul 10, 2018 at 3:15 PM, Marten4n6 ***@***.***> wrote: urllib2.URLError: <urlopen error [Errno 61] Connection refused> Not sure what to tell you, it can't connect to the server to ask for a payload. Maybe you specified the wrong IP/port (remake a launcher), if you're outside a local network make sure you forward your ports. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#41 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYaL-3fxxTcUVYiK4T8CQFCxzpzNUPdaks5uFJrfgaJpZM4VJRLb> .

[Marten4n6]

That doesn't matter as long as your specify the same thing in the builder and when starting the server.
You can run echo YOUR_BASE64_LONG_STRING | base64 --decode | grep -i 'request = ' to see where the launcher will connect back to, try visit this URL and see if it responds.

[marvic2409]

It shows 192.168.1.11:1200 (My local ip) and it does nothing. Did I do something wrong, why isn't my computer hosting the payload.

…

On Tue, Jul 10, 2018 at 3:19 PM, Marten4n6 ***@***.***> wrote: That doesn't matter as long as your specify the same thing in the builder and when starting the server. You can run echo YOUR_BASE64_LONG_STRING | base64 --decode | grep -i 'request = ' to see where the launcher will connect back to, try visit this URL and see if it responds. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#41 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYaL-w10IGIegZp8Q8UD3e6kqY1SiNQSks5uFJvNgaJpZM4VJRLb> .

[Marten4n6]

Hey, thanks very much for this letting me know of this, it was a stupid mistake on my part.
Please redownload this repository and everything should magically work now.

[marvic2409]

What was the issue, just wondering

…

On Tue, Jul 10, 2018, 3:32 PM Marten4n6 ***@***.***> wrote: Hey, thanks very much for this letting me know of this, it was a stupid mistake on my part. Please redownload this repository and everything should magically work now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#41 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYaL-_p0ImdnqGWSH1ZByNLiwSwiaEzXks5uFJ7dgaJpZM4VJRLb> .

[Marten4n6]

You can see every changes I make here, the commit that fixed this can be found here.
The problem was that I was starting the user interface (view) before the "background server", it never actually started the background server because the view is blocking, meaning it will not run any other code until it exits. I just overlooked this when I was cleaning up some code...