this post was submitted on 08 Apr 2026
4 points (66.7% liked)

Linux

17027 readers
92 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
MigratingtoLemmy@lemmy.world
4
Are there any ways to block unicode private use areas from coding at the kernel level? (lemmy.world)
submitted 1 day ago by j4k3@lemmy.world to c/linux@lemmy.world
16 comments fedilink hide all child comments
 

https://en.wikipedia.org/wiki/Private_Use_Areas

I came across a Python library that passed the ASCII range into one of these non printable character ranges and then into a database. If someone was doing that manually with a hex table, how is that detected and mitigated?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] vk6flab@lemmy.radio 6 points 1 day ago (1 children)

Globally we've agreed that the ASCII code for a space is 32, 65 for the letter A.

Unicode characters are also globally defined, so when someone uses an agreed upon code, everyone sees the same thing, like this grimace smiley ๐Ÿ˜

A private area is a place that we've all agreed is for "private use". If a trademark owner wants to use their special character in their documentation, they can define one area to represent their character, but the only people who will see it in the same way, are people who installed their particular font.

Anyone without that font would see whatever the font on their own machine displayed.

Putting random stuff in such a place is no more than putting gobbledygook in a text and it might even be used as a way to fingerprint text.

I'm not sure what you want to "detect" or "mitigate".

[โ€“] j4k3@lemmy.world 1 points 15 hours ago

I need to block a known threat actor already present on a system. Call it an exercise. I am interested in exploring and understanding it. This text obfuscation is a technique I discovered being used. This is a stage 3 threat model type of situation where every possible vector is in play.

This is not the theoretical, rtfm or read and trust the source situation.