From: Aditya Garg <gargaditya08@live.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: "chyishian.jiang@gmail.com" <chyishian.jiang@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"dmitry.kasatkin@gmail.com" <dmitry.kasatkin@gmail.com>,
"paul@paul-moore.com" <paul@paul-moore.com>,
"jmorris@namei.org" <jmorris@namei.org>,
"serge@hallyn.com" <serge@hallyn.com>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"keyrings@vger.kernel.org" <keyrings@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Orlando Chamberlain <redecorating@protonmail.com>
Subject: Re: [PATCH] efi: Add iMac Pro 2017 to uefi skip cert quirk
Date: Tue, 1 Nov 2022 14:06:29 +0000 [thread overview]
Message-ID: <9D46D92F-1381-4F10-989C-1A12CD2FFDD8@live.com> (raw)
In-Reply-To: <cee0b0176edc942ecc0ce6f4d585c239f9b7c425.camel@linux.ibm.com>
Hi Mimi
> I found this list of computers with the Apple T2 Security Chip -
> https://support.apple.com/en-us/HT208862, but not a list that
> correlates them to the system ID. With this update, is this the entire
> list?
As per the link you sent me, the following are the system IDs of the T2 Macs mentioned in the list
1. iMac (Retina 5K, 27-inch, 2020) - iMac20,1, iMac20,2
2. iMac Pro - iMacPro1,1
3. Mac Pro (2019) - MacPro7,1
4. Mac Pro (Rack, 2019) - MacPro7,1
5. Mac mini (2018) - Macmini8,1
6. MacBook Air (Retina, 13-inch, 2020) - MacBookAir9,1
7. MacBook Air (Retina, 13-inch, 2019) - MacBookAir8,2
8. MacBook Air (Retina, 13-inch, 2018) - MacBookAir8,1
9. MacBook Pro (13-inch, 2020, Two Thunderbolt 3 ports) - MacBookPro16,3
10. MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports) - MacBookPro16,2
11. MacBook Pro (16-inch, 2019) - MacBookPro16,1, MacBookPro16,4
12. MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports) - MacBookPro15,4
13. MacBook Pro (15-inch, 2019) - MacBookPro15,1, MacBookPro15,3
14. MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports) - MacBookPro15,2
15. MacBook Pro (15-inch, 2018) - MacBookPro15,1
16. MacBook Pro (13-inch, 2018, Four Thunderbolt 3 ports) - MacBookPro15,2
The system IDs of the Macs can be seen from official Apple’s documentation form the links below :-
https://support.apple.com/en-in/HT201634 - For iMac
https://support.apple.com/en-in/HT202888 - For Mac Pro
https://support.apple.com/en-in/HT201894 - For Mac mini
https://support.apple.com/en-in/HT201862 - For MacBook Air
https://support.apple.com/en-in/HT201300 - For MacBook Pro
After cross-checking only iMacPro1,1 seems to be missing.
Thanks
Aditya
next prev parent reply other threads:[~2022-11-01 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 10:01 [PATCH] efi: Add iMac Pro 2017 to uefi skip cert quirk Aditya Garg
2022-11-01 11:57 ` Mimi Zohar
2022-11-01 14:06 ` Aditya Garg [this message]
2022-11-01 21:07 ` Mimi Zohar
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=9D46D92F-1381-4F10-989C-1A12CD2FFDD8@live.com \
--to=gargaditya08@live.com \
--cc=chyishian.jiang@gmail.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=redecorating@protonmail.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=zohar@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.