News for hackers. Stuff that matters.
Re:Linux Problems on the Desktop (2018) by hartator on Sunday February 24, 2019 @08:37PM (#19242040)
If you need the last version of Wireshark, it’s getting complicated. And when you have a setup with Wireshark that works why update it? I am dubious that Wireshark can be an attack vector so security updates won’t be useful. Installing last versions is very straight forward when you are on Osx or Windows. You just go to the website and download it. Plus you get the original binaries not a doctored version to fit whatever launcher and log organization is currenty trending at Ubuntu HQ. Don’t get me wrong I still love my Ubuntus. But this we need to rewrite all software to fit our distributions is not a strenght. I think this line of thinking is kind of shared by Linus himself.
Re:Linux Problems on the Desktop (2018) by mr_toad on Sunday February 24, 2019 @10:47PM (#19242741)
Going to dozens or even hundreds of different websites to download the latest versions of software and then manually installing them all isn’t fast at all.

c.f. apt-get upgrade or similar, which takes a few seconds.

Re:Linux Problems on the Desktop (2018) by sandov on Tuesday February 26, 2019 @12:03AM (#19252088)
>c.f. apt-get upgrade or similar, which takes a few seconds.

Except when the package isn't included, or it isn't the version you needed, because then you have to spend 40 minutes trying to install all the dependencies and building the package from source, instead of the 3 minutes it would have taken to install an .exe on Windows.

Re:Linux Problems on the Desktop (2018) by ti_ranger on Tuesday February 26, 2019 @05:24AM (#19253234)
> because then you have to spend 40 minutes trying to install all the dependencies and building the package from source, instead of the 3 minutes it would have taken to install an .exe on Windows.

No, you take 2 minutes to install it using flatpak, or download a .appimage file.

And if neither of those are available, you spend that 40 minutes packaging the software, and submitting it to the distro you use for inclusion.

(If it was already packaged, but not new enough, that's a ~5 min job to do the update for your distro)

Re:Linux Problems on the Desktop (2018) by yjftsjthsd-h on Sunday February 24, 2019 @11:08PM (#19242829)
> And when you have a setup with Wireshark that works why update it? I am dubious that Wireshark can be an attack vector so security updates won’t be useful.

Ignoring feature enhancements and bug fixes for a moment, do you really think it improbable that there are security issues in a piece of software whose entire job is to sit on the network and record everything that it sees and then translate and interpret it?

Re:Linux Problems on the Desktop (2018) by hartator on Sunday February 24, 2019 @11:42PM (#19242995)
If an evil app is already communicating on the web and is already on your computer, what can it gain more?
Re:Linux Problems on the Desktop (2018) by crummy on Monday February 25, 2019 @01:14AM (#19243442)
Because the "evil app" is just a specially crafted JPG that your browser opened up that triggers some edge case in the old unpatched version of Wireshark that is inspecting traffic.
Re:Linux Problems on the Desktop (2018) by yjftsjthsd-h on Monday February 25, 2019 @01:01AM (#19243371)
Wireshark (usually) runs in promiscuous mode; it'd be "an evil app is already able to send something visible from your network interface" - which to be fair, might help for internal uses. It does usually mean that anything on your local network can attack you.
Re:Linux Problems on the Desktop (2018) by vlowther on Monday February 25, 2019 @10:39AM (#19246368)
You have a very limited imagination. Wireshark is regularly attacked -- it parses random data it gets off the network, therefore it can be attacked using deliberately malformed packets. See https://www.wireshark.org/security/ for more info.
Re:Linux Problems on the Desktop (2018) by hartator on Monday February 25, 2019 @10:52AM (#19246454)
Every single of these vulnerabilities are crashes and infinite loops. The worst thing you can do - if I am running a 5-year old Wireshark - is to make it crash if I am visiting one of your web services. And you probably can already do that in newer versions if you dig enough.