Only Listening to a Single Port at a Time - Githubissues

Morsmalleo / AhMyth

Cross-Platform Android Remote Administration Tool | Official maintained repository for the AhMyth R.A.T Project | A dedicated revival of the original repository at https://GitHub.com/AhMyth/AhMyth-Android-RAT

GNU General Public License v3.0

786 stars 191 forks source link

Only Listening to a Single Port at a Time #330

Closed TheDarkLord05 closed 1 year ago

TheDarkLord05 commented 1 year ago

This is an issue with the

[x] AhMyth Server

Describe the bug

When I try to listen on multiple ports I have a problem, when I input the First Port Number to listen on, it replies with:

Started Listening on Port: 1st PortNumber

But when I type the Second Port Number to listen on, it replies with:

Already Listening on Port: 2nd PortNumber

Even though we are not listening on the second port number.

To Reproduce

Steps to reproduce the behavior:

Create a payload and send it to the Victim.
Create another payload with different Port Number and send it to the Victim.
Try to listen on both ports and be greeted with an error when trying to listen on the Second Port saying that we are already listening on the Second Port when we are actually already listening on the first port, not the second one.

Expected behavior

It should listen to multiple ports like It was doing before the release of v1.0-beta.5 .

OS Information

OS Name: Any OS
OS Version: N/A

Morsmalleo commented 1 year ago

Hmm weird, I'll check this out ASAP

Morsmalleo commented 1 year ago

This is an issue with the

[x] AhMyth Server

Describe the bug

When I Try to Listen to Multiple Ports and Type the Port Number in , On First Port it Replies with " Started Listening on Port: PortNumber " but when i type 2nd Port Number to Listen on it Replies with: "Already Listening on Port: 2ndPortNumber " When though i have not Typed that Port Number Before.

To Reproduce

Steps to reproduce the behavior: After Creating Payload Send it to Victim and Create Another Payload with Different Port Number and Listen to Both of the Ports and Let me Know If This is Really an Issue.✅

Expected behavior

It should Listen to Multiple Ports Like It was Doing Before the Update v Beta 0.5 .

OS Information

OS Name: [Kali Linux]

So just for examples sake, let's say you first started listening on port 42474, it greeted you with a Green message stating it's listening on this port yes? And again for examples sake after that you went to listen on port 4444, it greeted you with a red error message stating that you're already listening on port 4444, have I got that correct??

TheDarkLord05 commented 1 year ago

This is an issue with the

[x] AhMyth Server

Describe the bug

When I Try to Listen to Multiple Ports and Type the Port Number in , On First Port it Replies with " Started Listening on Port: PortNumber " but when i type 2nd Port Number to Listen on it Replies with: "Already Listening on Port: 2ndPortNumber " When though i have not Typed that Port Number Before.

To Reproduce

Steps to reproduce the behavior: After Creating Payload Send it to Victim and Create Another Payload with Different Port Number and Listen to Both of the Ports and Let me Know If This is Really an Issue.✅

Expected behavior

It should Listen to Multiple Ports Like It was Doing Before the Update v Beta 0.5 .

OS Information

OS Name: [Kali Linux]

So just for examples sake, let's say you first started listening on port 42474, it greeted you with a Green message stating it's listening on this port yes? And again for examples sake after that you went to listen on port 4444, it greeted you with a red error message stating that you're already listening on port 4444, have I got that correct??

Exactly i am getting same message and when i tried with payload i am getting nothing from the 2nd port. Only Port, what i have Listened first is Working

Morsmalleo commented 1 year ago

This is an issue with the

[x] AhMyth Server

Describe the bug

When I Try to Listen to Multiple Ports and Type the Port Number in , On First Port it Replies with " Started Listening on Port: PortNumber " but when i type 2nd Port Number to Listen on it Replies with: "Already Listening on Port: 2ndPortNumber " When though i have not Typed that Port Number Before.

To Reproduce

Steps to reproduce the behavior: After Creating Payload Send it to Victim and Create Another Payload with Different Port Number and Listen to Both of the Ports and Let me Know If This is Really an Issue.✅

Expected behavior

It should Listen to Multiple Ports Like It was Doing Before the Update v Beta 0.5 .

OS Information

OS Name: [Kali Linux]

So just for examples sake, let's say you first started listening on port 42474, it greeted you with a Green message stating it's listening on this port yes? And again for examples sake after that you went to listen on port 4444, it greeted you with a red error message stating that you're already listening on port 4444, have I got that correct??

Exactly i am getting same message and when i tried with payload i am getting nothing from the 2nd port. Only Port, what i have Listened first is Working

Ok I'll take a look at this ASAP

Morsmalleo commented 1 year ago

Yep I'm getting the same thing on my end, I'll fix this as soon as possible

Morsmalleo commented 1 year ago

This is an issue with the

[x] AhMyth Server

Describe the bug

When I Try to Listen to Multiple Ports and Type the Port Number in , On First Port it Replies with " Started Listening on Port: PortNumber " but when i type 2nd Port Number to Listen on it Replies with: "Already Listening on Port: 2ndPortNumber " When though i have not Typed that Port Number Before.

To Reproduce

Steps to reproduce the behavior: After Creating Payload Send it to Victim and Create Another Payload with Different Port Number and Listen to Both of the Ports and Let me Know If This is Really an Issue.✅

Expected behavior

It should Listen to Multiple Ports Like It was Doing Before the Update v Beta 0.5 .

OS Information

OS Name: [Kali Linux]

So just for examples sake, let's say you first started listening on port 42474, it greeted you with a Green message stating it's listening on this port yes? And again for examples sake after that you went to listen on port 4444, it greeted you with a red error message stating that you're already listening on port 4444, have I got that correct??

Exactly i am getting same message and when i tried with payload i am getting nothing from the 2nd port. Only Port, what i have Listened first is Working

Should be fixed now, please re-download the source code and try again to confirm. If it's fixed I'll update the binaries for the beta.5 release

TheDarkLord05 commented 1 year ago

This is an issue with the

[x] AhMyth Server

Describe the bug

When I Try to Listen to Multiple Ports and Type the Port Number in , On First Port it Replies with " Started Listening on Port: PortNumber " but when i type 2nd Port Number to Listen on it Replies with: "Already Listening on Port: 2ndPortNumber " When though i have not Typed that Port Number Before.

To Reproduce

Steps to reproduce the behavior: After Creating Payload Send it to Victim and Create Another Payload with Different Port Number and Listen to Both of the Ports and Let me Know If This is Really an Issue.white_check_mark

Expected behavior

It should Listen to Multiple Ports Like It was Doing Before the Update v Beta 0.5 .

OS Information

OS Name: [Kali Linux]

So just for examples sake, let's say you first started listening on port 42474, it greeted you with a Green message stating it's listening on this port yes? And again for examples sake after that you went to listen on port 4444, it greeted you with a red error message stating that you're already listening on port 4444, have I got that correct??

Exactly i am getting same message and when i tried with payload i am getting nothing from the 2nd port. Only Port, what i have Listened first is Working

Should be fixed now, please re-download the source code and try again to confirm. If it's fixed I'll update the binaries for the beta.5 release

Yep Fixed now. Thanks Man for Your KindNess And Also HARDWORK for this Project to keep it Alive. Also I dont want to post again same ISSUE as it is already there Pending: When i Try to Download Any Big file Like 10 MB from Victom , I am getting Disconnected from server and Connects Again BUt this ERROR was also in Previous Version Should't be FIXED in This Version? Or need Some things to Do More?

Morsmalleo commented 1 year ago

This is an issue with the

[x] AhMyth Server

Describe the bug

When I Try to Listen to Multiple Ports and Type the Port Number in , On First Port it Replies with " Started Listening on Port: PortNumber " but when i type 2nd Port Number to Listen on it Replies with: "Already Listening on Port: 2ndPortNumber " When though i have not Typed that Port Number Before.

To Reproduce

Steps to reproduce the behavior: After Creating Payload Send it to Victim and Create Another Payload with Different Port Number and Listen to Both of the Ports and Let me Know If This is Really an Issue.white_check_mark

Expected behavior

It should Listen to Multiple Ports Like It was Doing Before the Update v Beta 0.5 .

OS Information

OS Name: [Kali Linux]

So just for examples sake, let's say you first started listening on port 42474, it greeted you with a Green message stating it's listening on this port yes? And again for examples sake after that you went to listen on port 4444, it greeted you with a red error message stating that you're already listening on port 4444, have I got that correct??

Exactly i am getting same message and when i tried with payload i am getting nothing from the 2nd port. Only Port, what i have Listened first is Working

Should be fixed now, please re-download the source code and try again to confirm. If it's fixed I'll update the binaries for the beta.5 release

Yep Fixed now. Thanks Man for Your KindNess And Also HARDWORK for this Project to keep it Alive. Also I dont want to post again same ISSUE as it is already there Pending: When i Try to Download Any Big file Like 10 MB from Victom , I am getting Disconnected from server and Connects Again BUt this ERROR was also in Previous Version Should't be FIXED in This Version? Or need Some things to Do More?

No I didn't manage to get onto that one in this version, I'm hoping to get some client updates done for the next version 😁 hopefully I can fix that disconnection problem with large files