geraldcombs

Well, crap. The domain and site are still fairly new, so maybe that's the issue? Is there anyone here from Palo Alto that can take a look?

Thanks for the feedback! I'll see if we can make the top of the site more descriptive.

Update: Changed the first sentence to "Stratoshark lets you explore and analyze applications at the system call level using a mature, proven interface based on Wireshark.

It's currently only passive, but that'd be an interesting feature. In order for that to happen we'd have to add that functionality to https://github.com/falcosecurity/libs/ along with the necessary plumbing in the UI.

Thanks! It's part of the same code base (and therefore open source), and Linux is definitely supported. It adds libscap and libsinsp as dependencies, and you can find basic build instructions at https://gitlab.com/wireshark/wireshark/-/blob/master/doc/str....

We return 402 (payment required) for one of our affected sites. Seems more appropriate.

The explanation someone gave me years ago was that midwesterners can speak to northerners and southerners without needing a translator, and the cost of labor in rural Nebraska and Kansas (which also had a ton of call centers at the time) is low.

Why not both? Git itself checks and sanitizes branch names, and GitHub should arguably match that behavior. I don't think anyone would object to safer workflows and related tooling instead of being told "here, have some bash inside YAML, now be careful!"

Yeah, I think the story that's being missed here is that GitHub allows branches named "$(curl...|bash)".

Maybe it's the hacking equivalent of Schrödinger's douchebag? If the hacking attempt succeeds, then you've achieved your goal. If it fails then you obviously joking or doing "research."

And canals: https://www.tid.org/current-projects/project-nexus/

Apparently ME was so bad it's been memory-holed.

Ours contains a Banana Splits reference: https://www.wireshark.org/404.html

I was trying to make the point that string validation isn't limited to protobuf. You need to do it for any network protocol that uses strings, which is most of them.

This could be generalized to any `string` field in any network packet.

So does DigitalOcean. It'd be nice if the page specified which vendors do and don't.

Windows 10 and 11 support Arm64, but their Server counterparts don't. Microsoft has also been reaching out to application developers, asking them to add Arm64 support. I think we're going to see a major shift to Arm64 in the Windows world in the near future.

TShark (the CLI companion to Wireshark) does with the `-T json` flag.

The traceroute that ships with macOS supports ICMP, UDP, TCP, and GRE. As I recall, the one(s) available on most Linux distributions do as well.

How are Electron apps typically shipped? If the answer is "inside an installer" then the installer needs to be signed.

Apples and Acorns

You're leaving out the "...and then they reported it to the project" part, which meant that the project maintainers had to put in time and effort responding to a reported vulnerability.

The traceroute command on modern Linux and macOS supports TCP, which I've found to be quite useful since you can see where in the path a connection is failing.

This shifted from "can" to "absolutely have to" a long time ago for my use cases.

For those wondering where the property in question is, there's an SF Chronicle article with a map:

https://www.sfchronicle.com/bayarea/article/flannery-associa...

There's a sizeable overlap with the Montezuma Hills wind farm. It'll be interesting to see how a bunch of pre-existing wind turbines fit into their plans.

Oh wow, thanks!

In the early aughts it was fashionable for web sites to have elaborate "intro" pages, usually animated using flash. They were so ubiquitous and annoying that someone created a parody at skipintro.com. Does anyone know if the skipintro animation can viewed anywhere today? It looks like the Wayback Machine has snapshots archived, but trying to load it returns an error.

Wireshark's creator here. Waking up to everyone's kind words and reminiscing made my morning. Thanks!

I wonder which version of Wireshark he was using; we've supported the evil bit since 2009.

kydns looks really cool!

(and if you're tired of Wireshark's hex dumps you can switch to the packet diagram view: https://www.wireshark.org/docs/wsug_html_chunked/ChUsePacket...)

It (and most other scripting languages) are likely just calling inet_aton under the hood.