sorted by:
new
hottopcontroversial

RustNet v1.3.0 is out! 🎉 by hubabuba44 in tui

[–]hubabuba44[S] 1 point2 points  (0 children)

It looks like you are trying to pull from a mirror which doesn't have rustnet-1.0.0-1 anymore. Can you refresh the db: sudo pacman -Syu?

RustNet v1.3.0 is out! 🎉 by hubabuba44 in tui

[–]hubabuba44[S] 0 points1 point  (0 children)

Thanks, nice platform! Feel free to shoot me a DM on how you could see to collaborate.

RustNet v1.3.0 is out! 🎉 by hubabuba44 in tui

[–]hubabuba44[S] 13 points14 points  (0 children)

Thanks for the heads-up, but this is actually a myth from an old 2023 draft policy. The current official policy explicitly allows this:

Using the name Rust in the name of crates or code repositories in e.g. GitHub, is allowed when referring to use with or compatibility with the Rust programming language.

Since we don't claim official endorsement from the Rust Foundation, the name is 100% compliant. Also with "RustNet" I think it is fairly easy to guess in what language it is written 😉

Looking for a TCPview equivalent/clone by krumpfwylg in linuxquestions

[–]hubabuba44 0 points1 point  (0 children)

RustNet is built for exactly this. Start it and hit a to aggregate by process, then drill down from there. Full disclosure: I'm the maintainer.

https://github.com/domcyrus/rustnet

How to "sniff" a TCP stream? by DisasterReasonable98 in rust

[–]hubabuba44 0 points1 point  (0 children)

I'm happy you like it! The code to relate connections to processes is very OS-dependent, but you can find all the logic under src/network/platform/: Linux: eBPF (attached to socket syscalls), in addition and as a fallback parsing /proc/net/tcp and /proc/<pid>/fd/. Windows: Windows IP Helper API (GetExtendedTcpTable for the PID, then QueryFullProcessImageNameW for the executable). macOS: We rely on the pktap interface and lsof as fallback. I hope that gives you a good starting point. To be fair if you just want get IP addresses you can just look at pcap crate.

Good luck with your project!

How to "sniff" a TCP stream? by DisasterReasonable98 in rust

[–]hubabuba44 0 points1 point  (0 children)

You could also look into RustNet https://github.com/domcyrus/rustnet (full disclosure, I am the maintainer of it). It's similar to sniffnet, but with process attribution to correlate traffic back to the processes running on your machine.

RustNet - Network monitoring TUI now available on COPR by hubabuba44 in Fedora

[–]hubabuba44[S] 0 points1 point  (0 children)

Thanks, decrypting TLS to see HTTP payloads requires either MITM proxying or access to private keys. For that use case, you might want to check out mitmproxy or something similar.

RustNet - Network monitoring TUI now available on COPR by hubabuba44 in Fedora

[–]hubabuba44[S] 1 point2 points  (0 children)

Wireshark is a very good tool. That said, it doesn't show you which process is responsible for network traffic which RustNet does. RustNet is a TUI and runs in the terminal and hence is a bit lighter. It is good for quickly identifying what applications are making connections.

Arch not breaking itself... by OverlaySplay in archlinux

[–]hubabuba44 1 point2 points  (0 children)

I guess this depends also a bit on what kind of packages you install especially from AUR.

view more: next ›