feat: standalone PineAPE enterprise engine on phy1
The stock daemon's enterprise config generation is broken on this firmware (it hardcodes eap_server_erp=1, which hostapd rejects), so the enterprise attack now runs its own karma+PineAPE hostapd instance on wlan1ent/phy1: iw-created iface, EAP config with catch-all user file, pineape+auth capture enabled via ctrl, mgmtiface registered in pineapd UCI so captured creds flow into recon.db (hostap_basic/hostap_chalresp). Boot-recovery redeploys a live attack after a Mark VIII restart.
This commit is contained in:
@@ -1523,7 +1523,7 @@ views.attacks_enterprise = (root) => {
|
||||
status.append('Attack', attackBadge(ap));
|
||||
status.append('SSID', h('span', { text: ap && ap.ssid ? ap.ssid : '—' }));
|
||||
status.append('Interface', h('span', { text: ap ? ap.iface : '—' }));
|
||||
status.append('Band', h('span', { text: '2.4 GHz' }));
|
||||
status.append('Band', h('span', { text: ap && ap.band ? ap.band + ' GHz' : '5 GHz' }));
|
||||
status.append('Channel', h('span', { text: ap && ap.channel != null ? ap.channel : '—' }));
|
||||
status.append('Credentials', h('span', { text: String(ent.creds || 0) }));
|
||||
pApeBody.innerHTML = '';
|
||||
|
||||
Reference in New Issue
Block a user