From: John Floren <john@jfloren.net>
To: aek@bitsavers.org, tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Thompson trojan put into practice
Date: Sun, 19 Sep 2021 16:10:06 +0000 [thread overview]
Message-ID: <jZXTwSxBUL2gCzV2e690kJN4C2H6YCuHyrCs5YIUYzA7J1LFDzZM4nb-hf_qf-rWmGP9G6c_LjLs7Z_tq3as0FLxlCHp3eEDksgu2QogBzM=@jfloren.net> (raw)
In-Reply-To: <fd0b2166-54ec-0f2e-7f0f-2fe80abaf501@bitsavers.org>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
-------- Original Message --------
On Sep 19, 2021, 8:58 AM, Al Kossow < aek@bitsavers.org> wrote:
>> For demonstration purpose I put my experiment with a compiler backdoor in a
>> public repository
>> It's part of my academic project to work on provable compiler security.
Sounds like excellent grounds for expulsion.
Whatever happened to the people who were submitting poison pull requests at U-Minnesota?
It's in his own fork, in a directory called tcc-evil. He's not exactly sneaking it into the distribution. Calling it expulsion-worthy reminds me of the time a guy phoned the FBI because of an article he read in the NYT: Sandia Labs was running botnets in a virtualized environment! (Could the cluster route to the Internet? No, but he didn't know that, and he didn't care; only bad people have botnets)
john
[-- Attachment #2: Type: text/html, Size: 875 bytes --]
next prev parent reply other threads:[~2021-09-19 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 15:46 arnold
2021-09-19 15:58 ` Al Kossow
2021-09-19 16:02 ` arnold
2021-09-19 16:10 ` John Floren [this message]
2021-09-20 2:39 Douglas McIlroy
2021-09-20 2:50 ` Larry McVoy
2021-09-20 7:12 ` arnold
2021-09-20 3:04 Noel Chiappa
2021-09-20 3:21 ` David Arnold
2021-09-20 4:35 ` Earl Baugh
2021-09-20 4:36 ` Earl Baugh
2021-09-20 11:57 Douglas McIlroy
2021-09-20 13:51 ` Ken Thompson
2021-09-20 14:35 ` John P. Linderman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jZXTwSxBUL2gCzV2e690kJN4C2H6YCuHyrCs5YIUYzA7J1LFDzZM4nb-hf_qf-rWmGP9G6c_LjLs7Z_tq3as0FLxlCHp3eEDksgu2QogBzM=@jfloren.net' \
--to=john@jfloren.net \
--cc=aek@bitsavers.org \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).