I guess this is a bit embarrassing, but I finally fell for a May Fools joke...

https://lists.riscv.org/g/apps-tools-software/topic/risc_v_tech_unprivileged/105892640

I buy cars at 200k miles...

https://jalopnik.com/americans-are-driving-their-cars-to-death-in-order-to-s-1851450846

When someone moved your cheese 20 years ago. :)

https://bugzilla.kernel.org/show_bug.cgi?id=218796

https://hackaday.com/2024/05/01/manta-an-open-on-fpga-debug-interface/

Mentioned this in passing, but want to publicly thank Dell for sponsoring a big test box. Tons of storage, tons of bandwidth, and now 100G connected in my little lab for great io_uring networking testing as well. They even stopped by my office for a day to rack mount it!

Cambridge Street, Cambridge.

This isn't a lack of parking; this is a driver who couldn't be bothered to pull all the way into the space.

updated my recommended network/firewall topology #infosec

I implemented Ken Thompson’s Reflections on Trusting Trust (1984 Turing Award Lecture) compiler #backdoor for the GNU Compiler Collection (GCC). The backdoor maintains persistence by re-injecting itself to any new versions of the compiler built. The secondary payload modifies a test application by adding a backdoor password to allow authentication bypass:

$ cat testapp.c
#include <string.h>
#include <stdio.h>
#include <stdlib.h>

int main(int argc, char **argv)
{
if (argc == 2 && !strcmp(argv[1], "secret"))
{
printf("access granted!\n");
return EXIT_SUCCESS;
}
else
{
printf("access denied!\n");
return EXIT_FAILURE;
}
}
$ gcc -Wall -O2 -o testapp.c -o testapp
$ ./testapp kensentme
access granted!
$

I spent most time (around two hours) writing the generalized tooling that produces the final quine version of the malicious payload. Now that this is done, the actual code can be adjusted trivially to exploit more target code without any need to adjust the self-reproducing section of the code. This method of exploitation could be extended to target various binaries: SSH Server, Linux Kernel, Setuid binaries and similar. While itself written in C, the secondary payloads can target any programming languages supported by GCC.

It should be noted that GCC build checks for malicious compiler changes such as this. This check can – of course – also be bypassed. However, most serious projects have measures in place to avoid hacks of this nature.

Some links:
- Ken Thompson's "Reflections on Trusting Trust" paper: https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf
- David A. Wheeler: "Fully Countering Trusting Trust through Diverse Double-Compiling (DDC) - Countering Trojan Horse attacks on Compilers" https://dwheeler.com/trusting-trust/

#hacking #exploitdevelopment #kenthompson #infosec #cybersecurity @vegard

@etchedpixels @sjvn TBH, I'd love to be making other people's mistakes. We're just too busy making up new ones right now, maybe in a few years we'll get there ;)

@rjohnston @notjustbikes This is why people keep getting killed.

Oooh, @fedora 40 is a GO! 🚀

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/MZMGHPSYWTCVVM6LV67EBBOS7X7MS2P5/

#fedora #linux

Deepak Gupta talking about Control Flow Integrity on RISC-V.

[$] Gentoo bans AI-created contributions https://lwn.net/Articles/970072/ #LWN

If you're wondering why my LinkedIn profile says "flooring inspector" is because of a long-running joke. You see, once or twice a week I get calls on my *personal* mobile number from sketchy "IT security" companies peddling their products to anyone with "IT" and "Director" in the title. I'm 100% convinced that they are working from some stolen and resold sources, because I never use my personal mobile line for business (I have a Google Voice US number that I always put into any work-related forms).

For a few years now I've been trying to convince these callers that they have reached the wrong person and that I'm actually with "Lennox Foundation Repair." Yes, I do IT because I'm in charge of the laptop used to inspect the subfloors with a camera.

I know this is petty, but it brings me 2 minutes of schadenfreude joy as I hear the poor sod on the other end of the line get progressively more and more confused.

(Bonus points if you get the "I'm a flooring inspector" reference.)

@conor sounds rough...

@conor seems pretty on-brand for an LF event ;)

b4 am --check <msgid>

Initial implementation. The goal was to show a quick summary without outputting a wall of obtuse text.

@sanityinc @bagder Now I'm going to have to write my software BOMs as something like "Warning: this product was produced by a development team that uses curl and may contain traces of curl"...

Linus is a bit devious 😬

"'Kconfig: add some hidden tabs on purpose

[…] showed breakage in some third-party kernel config parsing tool.

[…] let's make sure it gets fixed. Because if you can't parse tabs as whitespace, you should not be parsing the kernel Kconfig files.

In fact, let's make such breakage more obvious than some esoteric ftrace record size option. If you can't parse tabs, you can't have page sizes."'

https://git.kernel.org/torvalds/c/d5cf50dafc9dd5faa1e61e7021e3496ddf7fd61e

#Linux #kernel #LinuxKernel

Happy to announce that I am now a Trusted Contributor in the @postmarketOS project! It has been around 3.5 years since I found out about it and started contributing (mostly with ports and mainline linux support for various Samsung devices). It really feels great to be part of a joint effort to give devices a second life, and decrease the amount of #eWaste in the world!