Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rootless Pings in Rust

bou.ke

Post reply on HN
Print view View original

1–10 of 87 posts

Re: Rootless Pings in Rust

#2

Post by N_Lens »

The Linux vs macOS behavioral differences in ICMP sockets documented by the article are critical:

- Linux overwrites identifier and checksum fields

- macOS requires correct checksum calculation

- macOS includes IP header in response, Linux doesn't

I think this is the kind of subtle difference that would trip up even experienced programmers

Re: Rootless Pings in Rust

#4

Post by dmitrygr »

I struggled in vain to see what this has to do with rust. The answer is nothing other than the 4 lines of sample code shown are in Rust. The actually useful nugget of knowledge contained therein (one can create ICMP packets without being root on MacOS or Linux) is language agnostic.

So... why? Should I now add "in C" or "in assembly" to the end of all my article titles?

Re: Rootless Pings in Rust

#5

Post by bpbp-mango »

dmitrygr wrote: post #4

I struggled in vain to see what this has to do with rust. The answer is nothing other than the 4 lines of sample code shown are in Rust. The actually useful nugget of knowledge contained therein (one can create ICMP packets without being root on MacOS or Linux) is language agnostic. So... why? Should I now add "in C" or "in assembly" to the end of all my article titles?

If you want

Re: Rootless Pings in Rust

#6

Post by IshKebab »

dmitrygr wrote: post #4

I struggled in vain to see what this has to do with rust. The answer is nothing other than the 4 lines of sample code shown are in Rust. The actually useful nugget of knowledge contained therein (one can create ICMP packets without being root on MacOS or Linux) is language agnostic. So... why? Should I now add "in C" or "in assembly" to the end of all my article titles?

Yeah it would definitely be a good idea for the assembly ones. Maybe not C since C has kind of been the de facto language for this stuff for decades so it's implied.

Re: Rootless Pings in Rust

#8

Post by franga2000 »

dmitrygr wrote: post #4

I struggled in vain to see what this has to do with rust. The answer is nothing other than the 4 lines of sample code shown are in Rust. The actually useful nugget of knowledge contained therein (one can create ICMP packets without being root on MacOS or Linux) is language agnostic. So... why? Should I now add "in C" or "in assembly" to the end of all my article titles?

It's a lot more than 4 lines of sample code, in fact on my screen, it looks like it's more code than text. This is closer to a Rust tutorial then a low-level networking explainer, so yeah, it makes sense to say "in Rust". If I wanted to do this in C, this would not be the best resource.

Re: Rootless Pings in Rust

#9

Post by raesene9 »

Worth noting you don't actually need to be fully root in Linux to do standard pings with your code, there's a couple of different options available at the OS level without needing to modify code.

1. You can just add the capability CAP_NET_RAW to your process, at which point it can ping freely

2. There's a sysctl that allows for unprivileged ping "net.ipv4.ping_group_range" which can be used at the host level to allow different groups to use ICMP ping.

Post reply on HN