UPDATE: I was able to pack the tool myself. Here you go! - https://gitlab.com/wearecaster/above/-/tree/kali/master

Thanks @wearecaster.

Will see about this for 2024.1!

I'm here with a little news. I've released a new version of Above v2.2! (Codename: Vettel)
I've uploaded this update also on Gitlab specifically for you and the tool packaging (deb)
The tool has become much more functional

The code responsible for threads has been rewritten, the tool works more stable;
Added function to record traffic to .pcap file
Added function to analyze traffic .pcap files
Small cosmetic code changes

Release Link: https://github.com/wearecaster/Above/releases/tag/vettel
Gitlab Link: https://gitlab.com/wearecaster/above

Dear Kali Linux moderators, I will continue to write new updates for this tool and release them to improve the functionality.

I want "Above" to look very good and have a great range of features to add it to Kali 2024.1 (like g0tmi1k said for 2024.1)

But don't worry, I will be posting all updates on both Github and Gitlab (for the .deb package) in a timely manner. I'll be posting about all updates here to keep you informed.

Thank you!

I have released Above v2.3 for Kali Linux
Improved code for some protocols, added support for new protocols, also added output of tips for mitigating found security problems. Now the tool looks even better.
And I've also packaged this version for .deb and made a merge request to create an icon in the kali menu.

v2.3 Release Link: https://github.com/wearecaster/Above/releases/tag/radiant
Gitlab Link: https://gitlab.com/wearecaster/above/-/tree/kali/master
Merge Request Link (for icon): https://gitlab.com/kalilinux/packages/kali-menu/-/merge_requests/17

@wearecaster thanks for the packaging.
I started to work on your package.

I have already two small "issues":

• in the debian/copyright, you chose to use the license GPL-2+ for the debian files but the project is licensed under Apache-2.0. We usually use the same license for the debian files as used for the project. It's to avoid issues, for examples if a Debian/Kali patch is merged in upstream project, no problem with different licenses... Are you ok to use Apache-2.0 for the debian files too?

• in your github repo (https://github.com/wearecaster/Above) you tag the releases with a codename. In Kali / Debian we have tools to monitor the new tagged releases but it only works with versions numbers. The tool can not see if a more recent version exist when it compares codenames. Is it possible for the next releases to tag them like "v2.4" or "2.4" or you want to keep the codename maybe "2.4-codename"/ "v2.4-codename" ?

@sbrun

Hi!

1) Yes, I agree.

2) No problem. Changed the tag of the latest release to v2.3 on the github repo

@sbrun

I fixed the LICENSE file, now Apache-2.0 license for debian files

I apologize for disturbing you. I would like to inform you that I have changed my nickname to "Cursed" (@cursedpkt), I have updated all files, name and mail. Everything is ready for further packing!

https://github.com/cursedpkt/above
https://gitlab.com/cursedpkt/above

Hello
I have just uploaded above version 2.3-0kali1 in kali-dev. It will be available in few hours.

@sbrun

Hi, Sophie!
Okay, thank you so much.

Thanks, I have checked the tool works in Kali. Everything works fine. What about the icon? I created a merge request and left icons in the comments!

https://gitlab.com/kalilinux/packages/kali-menu/-/merge_requests/17

Have a nice day!

I've added above to kali-menu so this can be closed now
https://gitlab.com/kalilinux/packages/kali-menu/-/merge_requests/17
https://gitlab.com/kalilinux/packages/kali-menu/-/commit/ff15b865ad9d2dcdb91bcd90ece3fd7ba1043ebf