Ariel Millennium Thornton @arielmt@computerfairi.es

#Linux ransomware in the wild: https://forums.gentoo.org/viewtopic-t-1060828.html

Linux-based malware not only exists but has existed for longer than most Linux users realize.

Also, not running anything as root that doesn't need root helps with defense in depth, but especially don't run as root anything *designed* to download & run completely unvetted code, like Web browsers do.

Sadly, spoiler: Flash Player was suspected but never confirmed as the ransomware entry vector.

Wow, it's been ages since I used diff and patch. Anyway, I'm making progress.

And finding that GCC is apparently happy with non-void C functions using `return;` without a value, while clang (rightly, IMO) throws an error.

@ticky That's actually GNU living up to the "GNU's Not Unix" moniker. :3c

FreeBSD basename actually works as expected in all three examples instead of keeling over the way GNU basename does without the -a switch.

I was reminded that PHP is still the only programming language in which a version deployed into production gave "Hello, world!" at least one RCE vulnerability. The one I have in my notes is CVE-2012-1823.

I'm not the only one who uses and customizes xterm. I am absolutely delighted. :3

@softgoat They're supposed to help with multitasking in the brain sense by organizing windows into separate piles. I don't know how useful or effective it is because it's been an age since I tried one.

After hand-patching and creating a new diff comes getting it to compile in clang.

Because absolutely NOTHING I do to the Imakefile is creating Makefiles with "CC = gcc" in them. No matter what, they're all "CC = cc", which is clang's C compiler.

The patch file is a unified diff that contains at least one unified diff nested within.

I sure hope patch processes files in lines from first to last, because that's how I'm making and skipping the hand-editing. :/

@thefishcrow@cybre.space 2038: I hate that computers think their time travel to 1901 worked.

"It's the CIA, Charlie Brown"
https://botsin.space/@TheSoundOfBot/785328

If we're going to reuse nonces in WPA2, then we need a way to better verify their integrity. Thankfully, my favorite rag, Hacking Gibsons, was on it four years ago. :V
https://computerfairi.es/media/UkWau8OkX4iwA542ytQ

@masklayer The best reply: https://twitter.com/JodiraHorsey/status/920327835130257409 #nsfw

@MissMacSee Please consider a trans friendly instance before swearing off Mastodon. Your story is not the first I've heard about the dot-social instance.
https://kitty.town/@GinnyMcQueen/1786666

@kibi Qwerty is so inefficient your layout is almost guaranteed to be at least a little better.

@shekkiesqueaks AsciiDoc? If that's not it, check out https://en.wikipedia.org/wiki/List_of_markup_languages

xcalpr.c:89:21: error: initializer element is not constant
static FILE *fout = stdout;

Everything I'm reading says that hasn't been valid C since before ANSI standardization way back in the '80s.

Oh, duh. The Debian package page has a diff file downloaded separately, and some of them are patches to the C files fixing the compiler error I'm getting. Guess I should read it, edit the source, and re-diff them.

The latest date in xcal's CHANGES file is 1995-09-13.