Devlog 5:

I finally did it! It’s now a cli tool!

What changed:

It’s a Cli. So, to use it just try the --help/-h flag to get the usage.

Also, I restructured the project into a core lib and the cli bin crates using a cargo workspace. This should allow me to more easily develop the Tui later.

I also set up two github workflows, one that audits my used packages using the actions-rust-lang/audit action. The other one builds me the cli for a lot of different targets using the dtolnay/rust-toolchain action.

I also started writing some instructions to try the project, but this is still an area of active development.

Next up

I defiantly need to document the protocol that I’m using.

Also, as I have mentioned I want to create a tui. Maybe later a gui would be a great addition but that’s something I’m not quite sure about.

Devlog 4: (Now with logging)

What change

• Rewrote a lot of the logic making it safer
• Added a timeout for pinging
• Added a Code struct which has TryFrom<&str> and std::fmt::Display implemented so it’s really easy to convert a code string to the code structure and back
• added logging with tracing
• Combined both sending sockets to one Arc<UdpSocket> so broadcaster and direct connection check share one socket reducing overhead
• Changed how I handle Errors, no longer ignoring them

Next up:

• Cli
• Maybe a tui

Devlog 3:

Got everything working in Rust.
Now the direct connection check works in both directions.

Next up:

• Optimizing
• TUI
• CLI

Devlog 2:

I started reimplementing everything in rust. Already have the discovery broadcast and listener working.
So the only things missing are the direct connection check from the program site and a better looking interface like a tui.

Devlog 1:

So I reverse engineered the protocol hak5 uses for SharkLink using one SharkJack Display and my PC with Wireshark for package inspection.

I first needed to implement the device discovery which is a broadcast UDP package which in plan text says <PIN> <Sender_Ip>\n so for example 1-3-3-7 192.168.178.1\n

Then I reverse engineered the ping messages which are a direct connection with first PING <Sender_IP>\n and then the response which is ACK <Sender_IP>\n.

Nextup:

Reimplement the program in rust and after that create a tui.

Fixed the /man command. I forgot to change some stuff when modifying some functions form the /help command. But now it’s fixed.

So yes this took me for ever.

I added a /tic_tac_toe command. It
detects if someone one and if there is a draw, also only the current
player can make a move.

Also I added some Man pages for the
/clear_channel and /gen_channel_history commands.

For this devlog I only changed some stuff and didn’t add that much.

What changed and got added:

• Changed to postgres for handling stuff related to the hak5_products
• the product list now auto updates every hour
• servers only need to opt in for products using the /enable_hak5_products command and can disable it using the /disable_hak5_products
• users can subscribe to get up notified if a new product is added
• the sitemap_products.xml is now automatically getting fetched from the sitemap.xml

That should be everything that I added and changed. I’m still putting of writing the man pages for all commands.

If you have any ideas for this project, I would love to here them.

Added a lot since the last Devlog.

What’s new:

• The _bot command can now only be used by the account which id is specified in the .env file of the bot
• Created a Dockerfile and an example docker compose file
• added the /internet_checksum command to calculate the checksum for an udp header (was learning for an exam)
• added a /base84 command (maybe useful for CTFs)

Published a first prerelease of my extension to the vscode marketplace.

I also added commands for adding new commands or event listeners to the bot.

If you want to you can check out the prerelease here:
https://marketplace.visualstudio.com/items?itemName=ERR0RW0LF.fluxerbothelper

I would love some feedback.

Added auto completion for the structure following the event listener decorators. Also added a bit to the readme

Started creating an extension to help me with developing my fluxer bot.

For now there is some code completion for when creating new commands.
And a new “Create: new file…” option to create a cog with everything already setup.

Added 2 new commands and fixed some stuff.

The new commands are:

/file_profile which displays different information about files like there hashes or there file extension.
I also added a /man command which gets the information about commands added by cogs, so mostly all commands except for /_bot, and displays the more detailed information to only one command in contrast to the /help command.

What I fixed:

Locked the /_bot command to only be able to be used by admins. This is still not completely save for publicly hosting this bot so that anyone can invite it to there server.
Also fixed some things I forgot or not correctly changed when moving the code for the /update_hak5_product_list command to a cog. Also made the command now able to support multiple servers at the same time using the same bot.

Next up:

Write the man pages for all my commands and to improve that command

Added the new command /base64_file which allows the decoding of base64 directly to a file. This files extension gets determent based on the magic number in it. The command also allows the conversion of files into base64. ———————————————————————————————————————– Added hot reloading to the cogs as it’s called in the lib I’m using. cogs allow the loading of commands from other files. To reload you now can use the command /_bot reload ———————————————————————————————————————– Also added cheat sheets for markdown using the /markdown command. Then a user can select between markdown for GitHub, Fluxer or both.

Worked on a lot of stuff before I joined Stardance. But the first thing i added after joining was a base64 command similar to the one found in Linux. I now have implemented these commands: /clear_channel, /gen_channel_history (generates fake history for testing), /get_data, /bad_apple, /update_hak5_product_list (better way to view there stuff then going throughthe sitemap manually), /help, /base64 and /ping