Add a ncurse UI to wireshark
an idea by aaptel
Updated over 6 years ago. 3 hacker ♥️. Has no hacker: grab it!

Wireshark has a CLI program called tshark that can dump the dissectors raw (or xml) output. It would be nice to have complete curses wireshark UI, either by reusing tshark xml output or by making another ui program.

No Hackers yet

Join this project

Looking for hackers with the skills:

c terminal ui

This project is part of:

Hack Week 15

Activity

  • over 8 years ago: mbrugger liked this project.
  • almost 9 years ago: dwaas liked this project.
  • almost 9 years ago: dmulder liked this project.
  • almost 9 years ago: aaptel added keyword "terminal" to this project.
  • almost 9 years ago: aaptel added keyword "ui" to this project.
  • almost 9 years ago: aaptel added keyword "c" to this project.
  • almost 9 years ago: aaptel originated this project.


    • Comments

    • bmwiedemann
      almost 9 years ago by bmwiedemann | Reply

      could also use libyui which has an ncurses backend (in addition to QT and GTK ones)

    Similar Projects

    pudc - A PID 1 process that barks to the internet by mssola

    Description

    As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:

    • The backend is written in a mixture of C and RISC-V assembly.
    • The backend is actually PID1 (for real, not within a container).
    • We poll and parse incoming HTTP requests ourselves.
    • The frontend is a mere HTML page with htmx.

    The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.

    I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.

    Goals

    • Have a better understanding of different Linux features from user space down to the kernel internals.
    • Most importantly: have fun.

    Resources

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/