patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH] GPU acceleration
Date: Thu, 29 Jan 2026 14:11:22 +0100	[thread overview]
Message-ID: <87ecn84l8l.fsf@alyssa.is> (raw)
In-Reply-To: <20260120-gpu-accel-2-v1-1-ab80ef58d44e@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

Demi Marie Obenour <demiobenour@gmail.com> writes:

> I used an empty string for the hashes in 'gitfetch' and
> 'buildRustPackage'.  This is, of course, incorrect.  The correct value
> according to my own testing is
> "sha256-EOMkQ0aPRjsowdGuZjy5K1yKyKEzd5AVYxaECTz7n6k=" (git hash) and
> "sha256-k3dmxIuCQoOrn/VwauTdzuRw/XKQB6LPLgO5ql0rE7E=" (cargoHash).
> However, these should be validated before applying them, which is why I
> didn't include them in the patch themselves.  This is a security
> precaution: anyone who wants to inject malicious content must serve it
> to multiple people, not just one.

Even if you had included the hashes, I'd still have had to download the
resources myself, so they'd still have had to serve the malicious
content to me, too.  I don't have access to your cached downloads.  If
anything, including the hashes would have been of benefit, because then
I'd have had something to compare mine too.

(Not that it's a substantial threat in any case.)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2026-01-29 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21  3:26 [PATCH] GPU acceleration Demi Marie Obenour
2026-01-29 13:11 ` Alyssa Ross [this message]
2026-01-29 14:10 ` Alyssa Ross
2026-02-01 19:38   ` Demi Marie Obenour
2026-02-02 10:56     ` Alyssa Ross

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=87ecn84l8l.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=demiobenour@gmail.com \
    --cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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).