From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: CPU upgrade and LVM questions.
Date: Mon, 10 Dec 2018 22:14:12 +0000 [thread overview]
Message-ID: <20181210221412.2097b809@digimed.co.uk> (raw)
In-Reply-To: <aa01ed61-b2df-aa0b-eebd-4dbef2e8f594@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
On Mon, 10 Dec 2018 16:33:10 -0500, Taiidan@gmx.com wrote:
> > Not sure which country would be a reliable location though, I
> > wouldn't trust Western European countries either.
>
> USA is currently the best option since there have never been proven
> backdoors in made in usa hardware but plenty in chinese made hardware
> such as the recent motherboard hack chip scandal.
So that proves that US manufacturers are better at hiding their back
doors?
Or is it a numbers game, there are a hell of a lot more systems made in
China, so the chances of a backdoor being discovered is higher.
Either way, lack of evidence of insecurity is not proof of security.
--
Neil Bothwick
Secret hacker rule #11: hackers read manuals.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-10 22:14 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 9:27 [gentoo-user] CPU upgrade and LVM questions Dale
2018-12-06 10:03 ` Neil Bothwick
2018-12-06 15:17 ` Dale
2018-12-06 16:51 ` J. Roeleveld
2018-12-06 18:36 ` Corbin Bird
2018-12-06 20:58 ` Dale
2018-12-06 21:24 ` Jack
2018-12-06 21:55 ` Dale
2018-12-07 1:06 ` Corbin Bird
2018-12-07 1:17 ` Dale
2018-12-07 5:10 ` Dale
2018-12-07 6:22 ` [gentoo-user] " Nikos Chantziaras
2018-12-07 7:30 ` Dale
2018-12-07 10:49 ` Alec Ten Harmsel
2018-12-07 23:47 ` Nikos Chantziaras
2018-12-07 23:59 ` Dale
2018-12-09 18:23 ` Taiidan
2018-12-09 18:57 ` J. Roeleveld
2018-12-09 22:41 ` Dale
2018-12-10 21:33 ` Taiidan
2018-12-10 22:14 ` Neil Bothwick [this message]
2018-12-10 22:54 ` Dale
2018-12-11 2:00 ` Taiidan
2018-12-11 8:49 ` Neil Bothwick
2018-12-11 9:23 ` Mick
2018-12-11 10:48 ` Dale
2018-12-11 15:14 ` J. Roeleveld
2018-12-11 22:46 ` Adam Carter
2018-12-11 23:56 ` Dale
2018-12-12 2:15 ` Adam Carter
2018-12-11 10:20 ` Alan Mackenzie
2018-12-11 15:03 ` J. Roeleveld
2018-12-07 8:47 ` [gentoo-user] " Neil Bothwick
2018-12-07 8:58 ` Dale
2018-12-06 21:02 ` [gentoo-user] " Nikos Chantziaras
2018-12-06 21:45 ` Dale
2018-12-06 22:22 ` Nikos Chantziaras
2018-12-06 23:23 ` Dale
2018-12-06 23:40 ` Nikos Chantziaras
2018-12-07 0:19 ` Dale
2018-12-07 10:01 ` Peter Humphrey
2018-12-07 12:41 ` Dale
2018-12-07 16:51 ` Peter Humphrey
2018-12-08 1:01 ` Dale
2018-12-08 2:51 ` Nikos Chantziaras
2018-12-08 4:39 ` Dale
2018-12-08 5:33 ` David Haller
2018-12-08 5:45 ` Dale
2018-12-08 6:00 ` Nikos Chantziaras
2018-12-08 6:28 ` David Haller
2018-12-08 4:23 ` David Haller
2018-12-08 5:35 ` Dale
2018-12-08 6:06 ` David Haller
2018-12-08 5:38 ` David Haller
2018-12-08 9:40 ` Peter Humphrey
2018-12-08 9:50 ` Peter Humphrey
2018-12-06 21:03 ` [gentoo-user] " Grant Taylor
2018-12-09 22:45 ` Dale
2018-12-10 1:35 ` Grant Taylor
2018-12-10 2:38 ` Dale
2018-12-10 3:37 ` Grant Taylor
2018-12-10 9:27 ` Neil Bothwick
2018-12-10 16:00 ` Dale
2018-12-08 17:49 ` Alexander Puchmayr
2018-12-08 18:23 ` Dale
2018-12-08 19:09 ` J. Roeleveld
2018-12-08 20:48 ` Dale
2018-12-11 10:41 ` Dale
2018-12-22 23:58 ` Dale
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=20181210221412.2097b809@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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