overview for exposable

12

Can Ghidra do inline strings? (slrpnk.net)

submitted 6 months ago* (last edited 6 months ago) by exposable_preview to c/cybersecurity@sh.itjust.works

0 comments fedilink

I'm not sure if this is the right place to ask, but here we go.

I run into scenarios like these quite often. There is some kind of stack based array (or character string in this case) which is initialized on declaration. Ghidra displays it like this in the decompilation window, which is, declaration first and initialization one element at a time. Is there a way to make Ghidra display a stack string like this on a single line? Something like:

wchar16 buf[22] = L"69F2a+18d346b/SQ5c65e";

This would be a lot nicer on the eyes.

Kaktovik Hex - Featural compact binary/base16 in c/conscripts

[–] exposable_preview 2 points 8 months ago (1 children)

Glad I could help! I'd like to follow the project, so please give some updates in the future. Also, when the font is finished, please make sure to share it!

I found about the writing system when searching for the Kaktovik on the web, but didn't see the video, so thanks for sharing!

Kaktovik Hex - Featural compact binary/base16 in c/conscripts

[–] exposable_preview 1 points 8 months ago

here the pdf

Kaktovik Hex - Featural compact binary/base16 in c/conscripts

[–] exposable_preview 2 points 8 months ago (4 children)

This is very cool. So cool in fact that I want to contribute with some suggestions:

The part which I like the most is the ability to visualize how the numbers are constructed by adding parts together, and especially the fact that it (at least in my mind) reflects the binary representations. I'm specifically talking about the fact that to get a 3 you add the 1 to the RIGHT of the 2. The consistency is however broken with the number 15, supposedly for the easy of writing? I would prefer the 15 to look more like 3 / 7
There is some visual inconsistency with the 9, which has curved edges as opposed to all the rest (I don't mind the 0)
In addition to the previous point, I see the point (hah) as kind of a forced addition, despite it making sense, as I suppose you'd start confusing 9 and 11 / 13

After thinking about the above, I've made my own variation If the image is not clear enough, I've got a PDF which looks much better and I'll share somehow.

The main difference is the change of 8, which makes the >8s more consistent, and reduces the level of confusion. I've also added stroke order suggestions. My variation can also be written without lifting the pen off the paper, but for consistency's sake there are some symbols which I'd rather write with 2 strokes. I don't find that too bad though.

Please share some thoughts and good luck with the font!!

ps: for more inspiration there's also maya numerals