ash47 / OmegleMiddleMan

Lets you connect strangers to each other, and intercept messages AKA Man in the Middle Attack
233 stars 60 forks source link

Proxy Functionality (or lack thereof) #29

Closed mrtostados closed 6 years ago

mrtostados commented 6 years ago

I'd first like to say that this program is super useful. The code you wrote to filter out bots is really good (better than whatever Omegle uses, at least). Unfortunately, Omegle hit me with a "temporary ban" (not quite sure what for).

Looking at the code, I noticed that there are provisions for proxies to subvert bans and Captchas. Obviously, the code doesn't work---it's 2-year-old test code after all. I'm a complete Java noob, but from what I can tell, most of the code seems serviceable. If I had to guess, the problem is that the event setting the "proxyInfo" is detection of a Captcha (which at this point is likely deprecated), but there doesn't seem to be a corresponding ban-related event.

I'm mostly curious as to why you never pursued fully implementing that code, which it seems was pretty close to finished 2 years ago. I'm also wondering if you could be convinced to look into dusting it off or give some idea of what might need to be done (short of a complete rewrite) to render it operable.

ash47 commented 6 years ago

Hey mate, temp ban is easy to bypass, just jump on omegle and do the captcha, then you're good to go.

I just need to implement it on The app, they changed it recently.

On Sat, Apr 28, 2018, 8:31 AM mrtostados notifications@github.com wrote:

I'd first like to say that this program is super useful. The code you wrote to filter out bots is really good (better than whatever Omegle uses, at least). Unfortunately, Omegle hit me with a "temporary ban" (not quite sure what for).

Looking at the code, I noticed that there are provisions for proxies to subvert bans and Captchas. Obviously, the code doesn't work---it's 2-year-old test code after all. I'm a complete Java noob, but from what I can tell, most of the code seems serviceable. If I had to guess, the problem is that the event setting the "proxyInfo" is detection of a Captcha (which at this point is likely deprecated), but there doesn't seem to be a corresponding ban-related event.

I'm mostly curious as to why you never pursued fully implementing that code, which it seems was pretty close to finished 2 years ago. I'm also wondering if you could be convinced to look into dusting it off or give some idea of what might need to be done (short of a complete rewrite) to render it operable.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ash47/OmegleMiddleMan/issues/29, or mute the thread https://github.com/notifications/unsubscribe-auth/ADlKDi7QmfAA-BzM7nmtaeierUKERb1Wks5ts5wsgaJpZM4TrGFJ .

ash47 commented 6 years ago

Made this more obvious -- it will now tell you about the recaptcha