Scammers sometimes pose as Facebook friends who need help gaining access to an online account, and want to send you a two-factor authentication (2FA) code. In reality, the scammer has already found your login information (username and password) and only needs a 2FA code to gain access to your account.
I have an interesting scenario which I cant seem to find a solution to. I am hoping the community will be able to point me in the right direction. I need to block facebook messenger on a wifi network. To be more specific I need to block the facebook messenger (android & apple) application while mobile devices are on our wireless network. I have successfully blocked facebook web chat in the browser, but mobile devices on our wifi are still able access messenger. I dont want to block HTTPS completely, as many services utilize HTTPS. I dont want to block the entire facebook.com either since there is a need to use facebook.
Does anyone know what port the facebook messenger (android & apple) app uses to communicate? I read facebook implemented MQTT which uses 1883 and 8883 for SSL communications. However blocking these ports has had no impact. Maybe the app has hard coded IP addresses which it uses to avoid using DNS. If so, using DNS filters (i.e. OpenDNS) would not work. I would appreciate any insight anybody has regarding this matter. Thank you.
The facebook messenger app however has not been effected. I would like to thank @Chris75 for his recommendation. I have enabled Instant Messaging on my OpenDNS and I will test to see if this resolves my problem. I have to admit there is VERY little information regarding how the facebook apps operate. Short of utilizing a major UTM appliance (i.e. Watchguard) I was stumped. Blocking HTTPS works, but in this scenario I need to excise the disease not cut off the limb.
For those of you whom are curious I have some additional information regarding this topic. First let me address the last question. By blocking the domains I mentioned the apps were unaffected. Blocking the domains I mentioned only prevented users from using facebook chat in their browsers. Upon initial login to facebook it looks like you are connected to chat, but then a few seconds later it shows you disconnected. Works great.
The trade off is that apps that need to connect to Facebook will be unable to connect as well. Now let me be clear, by blocking these two domains you will not effect the Facebook app. This will block the facebook messenger app. If you want to make sure the facebook app has no problems you can whitelist graph.facebook.com.
I'm trying to implement some features inside a web view in facebook messenger. on the phone the webview is opening fine, but in desctop web browser the webview is opening inside a new tab.im using the following feature:buttons:[ type: "web_url", url: " -us/rift/", title: "Open Web URL", webview_height_ratio: "compact", messenger_extensions: true, I know that maybe it is supposed to open like this but you all can agree that if I'm implementing a custom feature inside the conversation it would be mach better to open it inside a small webview in the conversation.does anyone knows if this even possible?
df19127ead