You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been experiencing crashes with Kismet (currently 2021-06-R1). It's pretty much guaranteed to crash at some point after running it for a while. This seems to be related to Prelude logging which I have enabled.
Uncaught exception "Unknown IDMEF child 'alert_type' for class 'additional_data'"
Stack trace (most recent call last) in thread 8599:
#6 Object ", at 0xffffffffffffffff, in
INFO: Detected new 802.11 Wi-Fi device XX:XX:XX:XX:XX:XX
ALERT: BEACONRATE IEEE80211 Access Point BSSID XX:XX:XX:XX:XX:XX SSID
"XXXXXXXXXXXXXXXX" changed beacon rate from 21 to 13 which may
indicate AP spoofing/impersonation
#5 Object "/lib64/libc-2.23.so, at 0x7f90df029eec, in __clone
#4 Object "/lib64/libpthread-2.23.so, at 0x7f90dfd02683, in start_thread
#3 Object "/usr/lib64/libstdc++.so.6.0.21, at 0x7f90e0229be7, in
#2 Object "/usr/lib64/libstdc++.so.6.0.21, at 0x7f90e01ff640, in std::terminate()
#1 Object "/usr/lib64/libstdc++.so.6.0.21, at 0x7f90e01ff5f5, in
#0 Object "/usr/bin/kismet, at 0x9f50cd, in TerminationHandler()
Uncaught exception "std::exception"
Aborted
The text was updated successfully, but these errors were encountered:
I pushed a stop-gap to git that will show up in tomorrows nightlies (or you can build your own) that should, at least, prevent this from causing a crashing condition.
However, I've never actually gotten Prelude working; what this whole section of code really needs is someone to rewrite the interface who understands how Prelude does things so that it inherits the priorities, alert names, etc. Unfortunately I think the original contributor of the Prelude linkage is long gone.
On Friday, July 2nd, 2021 at 3:07 AM, pyllyukko ***@***.***> wrote:
I have been experiencing crashes with Kismet (currently 2021-06-R1). It's pretty much guaranteed to crash at some point after running it for a while. This seems to be related to Prelude logging which I have enabled.
Uncaught exception "Unknown IDMEF child 'alert_type' for class 'additional_data'"
Stack trace (most recent call last) in thread 8599:
#6 Object ", at 0xffffffffffffffff, in
INFO: Detected new 802.11 Wi-Fi device XX:XX:XX:XX:XX:XX
ALERT: BEACONRATE IEEE80211 Access Point BSSID XX:XX:XX:XX:XX:XX SSID
"XXXXXXXXXXXXXXXX" changed beacon rate from 21 to 13 which may
indicate AP spoofing/impersonation
#5 Object "/lib64/libc-2.23.so, at 0x7f90df029eec, in __clone
#4 Object "/lib64/libpthread-2.23.so, at 0x7f90dfd02683, in start_thread
#3 Object "/usr/lib64/libstdc++.so.6.0.21, at 0x7f90e0229be7, in
#2 Object "/usr/lib64/libstdc++.so.6.0.21, at 0x7f90e01ff640, in std::terminate()
#1 Object "/usr/lib64/libstdc++.so.6.0.21, at 0x7f90e01ff5f5, in
#0 Object "/usr/bin/kismet, at 0x9f50cd, in TerminationHandler()
Uncaught exception "std::exception"
Aborted
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [view it on GitHub](#382), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFKJYY66EC4EP5UTCO4HL2TTVVQT7ANCNFSM47WEKPQQ).
I have been experiencing crashes with Kismet (currently 2021-06-R1). It's pretty much guaranteed to crash at some point after running it for a while. This seems to be related to Prelude logging which I have enabled.
The text was updated successfully, but these errors were encountered: