sniffnet: Sniffnet (installed from .deb) not starting on Debian 11 (stable) due to missing/not available libraries and versions
Describe the bug When installed from the current stable .deb (v1.2.0) on up-to-date Debian 11 (current stable), the binary cannot be launched.
To Reproduce Describe steps to reproduce the bug, e.g.:
- Download current 1.2.0 .deb
- Install package via dpkg -i and install dependencies
- try to start binary sniffnet from commandline
- Experience error:
sniffnet: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
Expected behavior Program should be started.
Desktop (please complete the following information):
- OS: Debian Linux
- Version 11 (stable)
Additional context
ldd /usr/bin/sniffnet | grep “not found”
/usr/bin/sniffnet: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.35' not found (required by /usr/bin/sniffnet) /usr/bin/sniffnet: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.33’ not found (required by /usr/bin/sniffnet)
/usr/bin/sniffnet: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by /usr/bin/sniffnet) /usr/bin/sniffnet: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34’ not found (required by /usr/bin/sniffnet)
libssl.so.3 => not found
libcrypto.so.3 => not found
Available libraries on Debian 11:
ll /lib/x86_64-linux-gnu/libssl* -rw-r–r-- 1 root root 398K 15. Feb 21:31 /lib/x86_64-linux-gnu/libssl3.so -rw-r–r-- 1 root root 988K 5. Feb 22:23 /lib/x86_64-linux-gnu/libssl.a lrwxrwxrwx 1 root root 13 5. Feb 22:23 /lib/x86_64-linux-gnu/libssl.so -> libssl.so.1.1 -rw-r–r-- 1 root root 584K 5. Feb 22:23 /lib/x86_64-linux-gnu/libssl.so.1.1
ll /lib/x86_64-linux-gnu/libcrypto* -rw-r–r-- 1 root root 5,3M 5. Feb 22:23 /lib/x86_64-linux-gnu/libcrypto.a lrwxrwxrwx 1 root root 16 5. Feb 22:23 /lib/x86_64-linux-gnu/libcrypto.so -> libcrypto.so.1.1 -rw-r–r-- 1 root root 3,0M 5. Feb 22:23 /lib/x86_64-linux-gnu/libcrypto.so.1.1
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 21 (12 by maintainers)
Just tested, looks OK for me on BackBox linux, based on Ubuntu. GJ.
@GyulyVGC I can confirm, that this DEB (better: it’s contents 😃 ) now work fine on Debian 11 (current stable)!
Sniffnet now starts without errors. 🥇
Thank you for your efforts!
EDIT: I’ll leave this issue open for now, until the other affected people have also confirmed.
Thanks for the confirmation!
Don’t worry about the issue, I will personally close it after other confirmations or eventually due to inactivity.
I’m happy it’s working for you for the moment!!
Hey @ZEROF @sysms @RP-11 @onlineapps-cloud
We changed the building strategy and we are looking for feedback/testers to see if we finally solved this issue.
Could you kindly try the new package available below?
Sniffnet_LinuxDEB_amd64.deb.zip
Thanks in advance.
Thanks for pointing out. Using cargo will perform the build step directly on the target machine, therefore in this case all the dependency should actually be on point 👍
Right now using cargo is the solution. Small how to install ( tested on Ubuntu 20.04):
Install cargo:
curl https://sh.rustup.rs -sSf | shInstall dependency (one is missing in documentation libfontconfig1-dev)
sudo apt install libfontconfig1-dev libasound2-dev libfontconfig1 libpcap-devcargo install sniffnetsudo setcap cap_net_raw,cap_net_admin=eip /home/$USER/.cargo/bin/sniffnetStart using:
sniffnetThis allow running sniffnet as regular user, not root.
Same as #225, the issue is that the
reqwestcrate defaults to using thenative-sslfeature, which relies on v1.1 of OpenSSL. While Debian aligns with this version by default, Ubuntu adopts v3. To resolve this matter, you can opt to build the project with therustls-tlsfeature, or alternatively, ask the user manually install the olderlibssl1.1package.P.S. I’ve already addressed this issue in my incoming PR.
Don’t worry man!
Thank you very much! Much appreciated!
For me personally not, because I don’t want another package manager on my system which I have to take care of.
But maybe others could benefit?
Thanks very much for your confirmation. And yes, managing all the different distros is a nightmare.
@4r7if3x is going to help me package an AppImage / Flatpak in the future, and I will take care of pinging you.
Maybe it’s a stupid question but: could Homebrew work for you?