-
-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BruteSharkCLI will fail on pcap files when running on Ubuntu 22.04 LTS #124
Comments
@Limpem
|
Thank you for looking into this. To answer your questions:
When I do the same thing on 22.04: So it doesn't seem to do anything after running the start command. libpcap on 20.04: libpcap on 22.04: |
Hello
brutesharkcli is looking for libdl.so but it does not exist anymore, the libdl has been merged in the libc: I fixed the issue in Kali with a symlink: /usr/lib/brutesharkcli/libdl.so -> /lib/x86_64-linux-gnu/libdl.so.2 |
Any updates on this? Still seems to be an issue on the latest version |
As @odedshimon suggested, an update in SharpPcap might be necessary. Therefore, I updated the following solution files:
What I updated was the package reference from SharpPcap 6.0.0 to SharpPcap 6.3.0: Under Linux, I was able to build the BruteSharkCli. First, I removed the BruteSharkDesktop solution (it's a Windows app) and then I ran: That resulted in a successful build on the latest Arch Linux. The BruteSharkCli is not quitting with an error anymore:
How could we further test my "fix" to implement it later into BruteShark? |
@Affenselfie I need to bump the version at the source code, compile a new version and publish it as a new release. |
BruteSharkCLI will fail on processing pcap files when running on the 22.04 LTS release on Ubuntu (20.04 seems to work fine):
./BruteSharkCli -i Pcap_Examples/Ftp.pcap -m Credentials -o Example
[+] Start analyzing 1 files
[+] Start processing file : Ftp.pcap
ERROR: Failed to process file : Ftp.pcap
[+] Successfully exported extracted files to: Demo/Files
[+] BruteShark finished processing
The text was updated successfully, but these errors were encountered: