The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.net>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] 30th Anniversary of most epic netnews post
Date: Thu, 1 Apr 2021 09:14:28 -0700	[thread overview]
Message-ID: <CAL4LZyhinZ7oxNk_eofMdeJqZMgfJS0r5zXT6q_+4VRT9T+nsQ@mail.gmail.com> (raw)
In-Reply-To: <20210401152810.GI4209@mcvoy.com>

On Thu, Apr 1, 2021 at 8:29 AM Larry McVoy <lm@mcvoy.com> wrote:
> It's always amazed me that courts will take emails as "evidence" because it is
> absolutely trivial to fake them.  Unless they've added some crypto host
> identification (have they?)
>
> --lm

To some extent, yes, via DKIM:
https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail

This came up during the Hunter Biden email, uh, "situation". Basically
you can use the DKIM signature to verify that an email was actually
sent from a particular user account on a particular server. Of course,
it makes no guarantee of who actually *wrote* that email, only that it
was sent by someone with access to the account... or, more sinisterly,
that the owner of the mail server has helped to fake the email! Here's
a POC: https://github.com/robertdavidgraham/hunter-dkim

For unrelated reasons, late last year people started calling for
Google to periodically rotate DKIM keys and release the old ones,
which would mean anyone could spoof an email from a few years ago:
https://blog.cryptographyengineering.com/2020/11/16/ok-google-please-publish-your-dkim-secret-keys/

John

  reply	other threads:[~2021-04-01 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 12:21 Ron Natalie
2021-04-01 14:24 ` Adam Sjøgren via TUHS
2021-04-01 15:20   ` Ron Natalie
2021-04-01 15:28     ` Larry McVoy
2021-04-01 16:14       ` John Floren [this message]
2021-04-01 16:22         ` Richard Salz
2021-04-01 21:27       ` John Cowan
2021-04-01 15:30     ` John Foust
2021-04-01 21:11 ` Dave Horsfall

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=CAL4LZyhinZ7oxNk_eofMdeJqZMgfJS0r5zXT6q_+4VRT9T+nsQ@mail.gmail.com \
    --to=john@jfloren.net \
    --cc=lm@mcvoy.com \
    --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).