networking

It would be useful to be able to toggle/flag into a process-level mode to group by pid and display more process-level information like the full command line.

• For the "Utilization by process name" window, we could group by pid rather than process name so that it's easier to find specific heavy network resource consumers.
• For the "Utilization by connection" window, including the pid + cmdlin

RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.

Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:

1. [!]
2. [~]
3. [>]
4. | {}

If any of these characters appear in any of the tests, fail the CI. E

~/Local/laminar (master) $ cargo bench
    Updating crates.io index
  Downloaded bincode v1.2.0
  Downloaded quickcheck v0.9.0
  Downloaded rand v0.7.2
  Downloaded either v1.5.3
  Downloaded libc v0.2.64
  Downloaded crossbeam-channel v0.3.9
  Downloaded bitflags v1.2.1
  Downloaded arrayvec v0.4.12
  Downloaded quickcheck_macros v0.8.0
  Downloaded ryu v1.0.2
  Downloaded env_lo

the lets-encrypt branch contains the effort to automatically handle authorization and certificate signing via Let's Encrypt. A background worker thread can be spun for auto-renewal with the intention of checking the expiration status once per week. It should be possible to rotate the certs without dropping requests by possibly queuing them when the renewal is triggered(?)

Background

ICMP messages are used by network devices, including routers, to send error messages and operational information indicating success or failure when communicating with another IP address. Examples include errors indicating when a requested service is not available or when a host or router could not be reached. We've

In distant-lua's process userdata, we have a status method that returns Status|nil, but the wait method returns success, exit_code instead of Status.

Users should be able to load any theme from a config folder for rshark (maybe located in ~/.config/rshark/ for Linux users for example).

The theme can be defined in a JSON format so it will give access to a wide variety of popular themes already present, and a user can easily obtain them from websites such as this one.