12/8/2023 0 Comments Wireshark windows portable config![]() Does anyone know what other packages might be affected or needed to run as a non-root account user? I know tor is one - vidalia will only work outside root as well. Wireshark 1.8.8 on my windows 7 incidentally always works fine and probably always will. I think its a bug or conflict with one of the new libraries it depends on. I don't have the foggiest idea why wireshark decided to hate my root account though. Very strange but I'm slowly getting better with my linux stuff. all this happened when I did the processes apt-get upgrade - apt-get update - apt-get update install - apt-get dist-upgrade to get everything updated in my BT5R3. You will still get that warning "Dangerous to run wireshark as root" though! Strange. making sure it has sufficient privileges to look at and run everything your root account can, and then issuing the commands as super-user (sudo). Like I say, it's all about having a user account which isn't root. Lo-and-behold! wireshark is perfect now, not only that but I'm pretty sure I can upgrade it by compiling the 1.8.8 version from source (in root of course). ![]() Wireshark comes in handy when initalising and debugging networks so I don't know why using it as root is discouraged, They should make programs as "root-proof" or "damage-proof" as as possible!Īnyhow, I installed wireshark (again) using synaptic on my root account, logged out and logged in to my browsing account - I couldn't install or compile it at all on my new user account - once again I gotta tweak the settings to let it do this, I'm not sure but if I have to logout and login to root everytime I need to install or compile something I'm gonna get annoyed - my Fast Account Switching doesn't work. I use this account specifically for testing proxies and browsing using but I should really be using this account as Default and using root ONLY to do housekeeping and major things installs etc, This took a little while to get going, but once I'd ironed out any conflicts most things seem to work just fine in there. I tried uninstalling, reinstalling, synaptic, downloading the source and re-compiling, going back to older versions, the whole shebang and EVERY time it ran, it would freeze! The ONLY way around this was for me to learn about User Accounts control in my Backtrack 5 R3 (ubuntu 32-bit) and add a user account which wasn't root. warning but I never really worried too much, thinking that I couldn't possibly damage anything really badly, right? Anyway to cut a long story short, wireshark started hanging up on me when I started it up and told it to capture on ANY interface - it would just freeze. it gave me the usual "wireshark should not be run as root" etc etc. The Mad thing is, I used to have wireshark running on my root user account (which was the only account I had lol) and it worked fine for ages and ages. usr/local/bin/ - you can just cd into there and then in a terminal execute 'sudo wireshark' it will ask for your user password then everything will be hunky-dory (but it will still warn you about running as root!). As above - assuming your user account has access to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |