[Module] EvilPortal

[3kh0]

I have a website already setup for this, can I just provide the URL?

[dark_pyrro]

You mean that you have the captive portal somewhere outside the Pineapple? Never seen that before using the Evil Portal module specifically. I guess you have to make changes in the extent that it's rather pointless to use the current Evil Portal module as a base for it. Try creating a new module from scratch instead or just simply start digging into the code of the Evil Portal module and make the changes needed. But, as said, my guess is that you have to tear down a perfectly well built "house" to the ground to create a new one. So, better to start off from scratch in that case.

[viggolek]

Hi, I've made a custom microsoft login portal but the captive portal doesn't show up when a device connects to the AP. It just connects and says no internet connection. The default test portal shows up fine. I can access the portal on http://172.16.42.1 and the preview works as well and it also successfully logs credentials. There's nothing out of the ordinary in the logs. I've imported other login forms and they work completely fine. Is this something anyone else has experienced before?

snippet of the logs:

2023-10-18 15:35:19,115 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:19,145 - evilportal - DEBUG - Calling handler for action toggle_portal and passing {'module': 'evilportal', 'action': 'toggle_portal', 'portal': 'microsoft-login'} (module.py:114)
2023-10-18 15:35:19,194 - evilportal - WARNING - Portal API already exists under /www/captiveportal. This is probably not an issue. (module.py:87)
2023-10-18 15:35:19,291 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:19,331 - evilportal - DEBUG - Sending response {"payload": "Portal has been activated."} (module.py:89)
2023-10-18 15:35:19,474 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:19,513 - evilportal - DEBUG - Calling handler for action list_portals and passing {'module': 'evilportal', 'action': 'list_portals'} (module.py:114)
2023-10-18 15:35:19,546 - evilportal - DEBUG - Creating portal folder (module.py:476)
2023-10-18 15:35:19,624 - evilportal - DEBUG - Listing directories (module.py:479)
2023-10-18 15:35:19,731 - evilportal - DEBUG - Building list (module.py:482)
2023-10-18 15:35:19,854 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:19,883 - evilportal - DEBUG - Sending response {"payload": [{"title": "google-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/google-login", "active": false}, {"title": "facebook-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/facebook-login", "active": false}, {"title": "microsoft-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/microsoft-login", "active": true}, {"title": "Test", "portal_type": "basic", "size": 4096, "location": "/root/portals/Test", "active": false}, {"title": "instagram-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/instagram-login", "active": false}, {"title": "twitter-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/twitter-login", "active": false}]} (module.py:89)
2023-10-18 15:35:46,582 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:46,623 - evilportal - DEBUG - Calling handler for action toggle_evilportal and passing {'module': 'evilportal', 'action': 'toggle_evilportal'} (module.py:114)
2023-10-18 15:35:46,850 - evilportal - DEBUG - Starting Evil Portal (module.py:340)
2023-10-18 15:35:48,952 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:48,979 - evilportal - DEBUG - Sending response {"payload": "Evil Portal started."} (module.py:89)
2023-10-18 15:35:49,039 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:49,100 - evilportal - DEBUG - Calling handler for action load_file and passing {'module': 'evilportal', 'action': 'load_file', 'path': '/tmp/EVILPORTAL_CLIENTS.txt'} (module.py:114)
2023-10-18 15:35:49,188 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:49,228 - evilportal - DEBUG - Sending response {"payload": "172.16.42.42\n\n"} (module.py:89)
2023-10-18 15:35:49,359 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:49,398 - evilportal - DEBUG - Calling handler for action status and passing {'module': 'evilportal', 'action': 'status'} (module.py:114)
2023-10-18 15:35:50,464 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:50,507 - evilportal - DEBUG - Sending response {"payload": {"running": true, "webserver": true, "start_on_boot": false}} (module.py:89)

 

[viggolek]

On 10/18/2023 at 5:00 PM, viggolek said:

Hi, I've made a custom microsoft login portal but the captive portal doesn't show up when a device connects to the AP. It just connects and says no internet connection. The default test portal shows up fine. I can access the portal on http://172.16.42.1 and the preview works as well and it also successfully logs credentials. There's nothing out of the ordinary in the logs. I've imported other login forms and they work completely fine. Is this something anyone else has experienced before?

snippet of the logs:

2023-10-18 15:35:19,115 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:19,145 - evilportal - DEBUG - Calling handler for action toggle_portal and passing {'module': 'evilportal', 'action': 'toggle_portal', 'portal': 'microsoft-login'} (module.py:114)
2023-10-18 15:35:19,194 - evilportal - WARNING - Portal API already exists under /www/captiveportal. This is probably not an issue. (module.py:87)
2023-10-18 15:35:19,291 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:19,331 - evilportal - DEBUG - Sending response {"payload": "Portal has been activated."} (module.py:89)
2023-10-18 15:35:19,474 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:19,513 - evilportal - DEBUG - Calling handler for action list_portals and passing {'module': 'evilportal', 'action': 'list_portals'} (module.py:114)
2023-10-18 15:35:19,546 - evilportal - DEBUG - Creating portal folder (module.py:476)
2023-10-18 15:35:19,624 - evilportal - DEBUG - Listing directories (module.py:479)
2023-10-18 15:35:19,731 - evilportal - DEBUG - Building list (module.py:482)
2023-10-18 15:35:19,854 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:19,883 - evilportal - DEBUG - Sending response {"payload": [{"title": "google-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/google-login", "active": false}, {"title": "facebook-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/facebook-login", "active": false}, {"title": "microsoft-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/microsoft-login", "active": true}, {"title": "Test", "portal_type": "basic", "size": 4096, "location": "/root/portals/Test", "active": false}, {"title": "instagram-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/instagram-login", "active": false}, {"title": "twitter-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/twitter-login", "active": false}]} (module.py:89)
2023-10-18 15:35:46,582 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:46,623 - evilportal - DEBUG - Calling handler for action toggle_evilportal and passing {'module': 'evilportal', 'action': 'toggle_evilportal'} (module.py:114)
2023-10-18 15:35:46,850 - evilportal - DEBUG - Starting Evil Portal (module.py:340)
2023-10-18 15:35:48,952 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:48,979 - evilportal - DEBUG - Sending response {"payload": "Evil Portal started."} (module.py:89)
2023-10-18 15:35:49,039 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:49,100 - evilportal - DEBUG - Calling handler for action load_file and passing {'module': 'evilportal', 'action': 'load_file', 'path': '/tmp/EVILPORTAL_CLIENTS.txt'} (module.py:114)
2023-10-18 15:35:49,188 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:49,228 - evilportal - DEBUG - Sending response {"payload": "172.16.42.42\n\n"} (module.py:89)
2023-10-18 15:35:49,359 - evilportal - DEBUG - Processing request. (module.py:217)
2023-10-18 15:35:49,398 - evilportal - DEBUG - Calling handler for action status and passing {'module': 'evilportal', 'action': 'status'} (module.py:114)
2023-10-18 15:35:50,464 - evilportal - DEBUG - Accepting on module socket (module.py:85)
2023-10-18 15:35:50,507 - evilportal - DEBUG - Sending response {"payload": {"running": true, "webserver": true, "start_on_boot": false}} (module.py:89)

 

found one on github that works, so I just ended up using that one instead

[DP01]

Hi newbi3,

the portals work great except that they don't log anything the first time I enter my creds. I have to reconnect and enter them again before they get logged. This happens with all the portals.

I am using the Kleo Portals.

Any idea what the Problem could be that i dont get the creds on the first attempt ?