| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First batch of fixes for: Intel SA-00115, CVE-2018-3639, CVE-2018-3640
- New Microcodes:
sig 0x00050655, pf_mask 0xb7, 2018-03-14, rev 0x3000009
- Updated Microcodes:
sig 0x000206a7, pf_mask 0x12, 2018-02-07, rev 0x002d -> 2018-04-10, rev 0x002e
sig 0x000206d6, pf_mask 0x6d, 2018-01-30, rev 0x061c -> 2018-05-08, rev 0x061d
sig 0x000206d7, pf_mask 0x6d, 2018-01-26, rev 0x0713 -> 2018-05-08, rev 0x0714
sig 0x000306a9, pf_mask 0x12, 2018-02-07, rev 0x001f -> 2018-04-10, rev 0x0020
sig 0x000306d4, pf_mask 0xc0, 2018-01-18, rev 0x002a -> 2018-03-22, rev 0x002b
sig 0x000306e4, pf_mask 0xed, 2018-01-25, rev 0x042c -> 2018-04-25, rev 0x042d
sig 0x00040651, pf_mask 0x72, 2018-01-18, rev 0x0023 -> 2018-04-02, rev 0x0024
sig 0x00040671, pf_mask 0x22, 2018-01-21, rev 0x001d -> 2018-04-03, rev 0x001e
sig 0x00050665, pf_mask 0x10, 2018-01-22, rev 0xe000009 -> 2018-04-20, rev 0xe00000a
sig 0x000506c9, pf_mask 0x03, 2017-11-22, rev 0x002e -> 2018-05-11, rev 0x0032
sig 0x00060662, pf_mask 0x80, 2017-09-27, rev 0x001a -> 2017-11-29, rev 0x0022
sig 0x000706a1, pf_mask 0x01, 2017-12-26, rev 0x0022 -> 2018-05-11, rev 0x0026
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- New Microcodes:
sig 0x000806eb, pf_mask 0xc0, 2018-02-11, rev 0x0084
- Updated Microcodes:
sig 0x000306c3, pf_mask 0x32, 2018-01-21, rev 0x0024 -> 2018-04-02, rev 0x0025
sig 0x000306e7, pf_mask 0xed, 2018-02-16, rev 0x0713 -> 2018-04-25, rev 0x0714
sig 0x000306f2, pf_mask 0x6f, 2018-01-19, rev 0x003c -> 2018-04-20, rev 0x003d
sig 0x000306f4, pf_mask 0x80, 2018-01-22, rev 0x0011 -> 2018-04-20, rev 0x0012
sig 0x00040661, pf_mask 0x32, 2018-01-21, rev 0x0019 -> 2018-04-02, rev 0x001a
sig 0x000406e3, pf_mask 0xc0, 2017-11-16, rev 0x00c2 -> 2018-04-17, rev 0x00c6
sig 0x000406f1, pf_mask 0xef, 2018-03-21, rev 0xb00002c -> 2018-04-19, rev 0xb00002e
sig 0x00050654, pf_mask 0xb7, 2018-03-27, rev 0x2000049 -> 2018-05-15, rev 0x200004d
sig 0x000506e3, pf_mask 0x36, 2017-11-16, rev 0x00c2 -> 2018-04-17, rev 0x00c6
sig 0x000806ea, pf_mask 0xc0, 2018-01-21, rev 0x0084 -> 2018-05-15, rev 0x0096
sig 0x000906ea, pf_mask 0x22, 2018-04-26, rev 0x0094 -> 2018-05-02, rev 0x0096
sig 0x000906eb, pf_mask 0x02, 2018-01-21, rev 0x0084 -> 2018-03-24, rev 0x008e
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/657100
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- We now install splitted ucode(s) into the correct directory.
- Fixed an issue when emerge failed when no microcode was selected.
- "minimal" USE flag was renamed to "hostonly" and disabled per
default to avoid confusion.
- Additional sanity checks were added to show a warning if no
microcode update was installed (can be the case when user
set "hostonly" USE flag or uses MICROCODE_SIGNATURES environment
variable).
Closes: https://bugs.gentoo.org/654638
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed microcodes (due to updates):
- sig 0x000806e9, pf_mask 0xc0, 2018-01-21, rev 0x0084, size 98304
- sig 0x000906e9, pf_mask 0x2a, 2018-01-21, rev 0x0084, size 98304
Added microcodes:
- sig 0x000806e9, pf_mask 0xc0, 2018-03-24, rev 0x008e, size 98304
- sig 0x000906e9, pf_mask 0x2a, 2018-03-24, rev 0x008e, size 98304
- sig 0x000906ec, pf_mask 0x22, 2018-02-19, rev 0x0084, size 96256
Closes: https://bugs.gentoo.org/654638
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to previous change (commit eb9036f6f998c91c6bc021f73bc10ca1b5240ae7),
this package can become very large (or the resulting initramfs).
While the already introduced environment variable "MICROCODE_SIGNATURES" is
allowing you to set iucode_tool's "--scan-system" parameter to only
install ucode(s) supported by the currently available (=online) processor(s),
this doesn't work for binary package user(s).
The now added "minimal" USE flag (enabled by default) will set "--scan-system"
parameter for you. This will still allow you to select/blacklist ucode(s)
for all your hosts on your central build host using the "MICROCODE_SIGNATURES"
variable like before while giving each host the opportunity to only install
really supported ucode(s) which will reduces the file size of the resulting
initramfs.
Bug: https://bugs.gentoo.org/654638
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...{BLACKLIST,SIGNATURES}
Especially now, since we are shipping a lot of microcodes,
initramfs can become very large and users might want to install
only specific microcode updates for their processor via
MICROCODE_SIGNATURES="-S" option.
However, this would overwrite our default BLACKLIST.
To allow users to use "-S" option without the burden to manually
maintain a BLACKLIST, we introduced a new MICROCODE_BLACKLIST
environment variable to split things.
In addition, there was a typo is previous blacklisted
signature which was corrected to blacklist the correct microcode.
Bug: https://bugs.gentoo.org/654638
Package-Manager: Portage-2.3.38, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ebuild changes:
===============
- Based on Intel's microcode tarball from 2018-04-25.
- Added 210+ additional microcode updates (for production, no beta release!),
which are signed by Intel and publicly available but are not distributed
via Intel's microcode tarball for marketing/product phase out reasons.
You can prevent the usage of these microcode updates and stick with
content from Intel's official release tarball via new "vanilla"
USE flag.
- Blacklisted microcode 0x000604f1 aka 06-4f-01 aka CPUID 406F1 which
requires a newer microcode loader in kernel which is only available
in kernel >=4.14.34.
It is blacklisted because loading via older loader could crash the
system. A news item with instructions will follow.
Closes: https://github.com/gentoo/gentoo/pull/8532
Bug: https://bugs.gentoo.org/654638
Package-Manager: Portage-2.3.38, Repoman-2.3.9
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/8199
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
| |
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/650772
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/650428
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
- port to EAPI=6
- add USE=binary use flag to be compatible with all other sys-firmware
packages that qemu depends on
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
| |
No changes that would require a new stabilization process. Simple
internal ebuild maintenance.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/484886
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/628354
Closes: https://bugs.gentoo.org/638532
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/617232
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
| |
Ebuild uses microcodes from 2017-11-17 but ebuild code changes
from recent ebuilds were backported.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19_p11, Repoman-2.3.6_p45
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Use the Intel upstream 'iucode_tool' to process all of the input
microcode, from both the text-format microcode.dat file and other
inputs, then generate a clean set of split outputs & optionally also
initramfs output.
- Allows easy inclusion of any future split-ucode releases for single
CPUs.
- No longer uses intel-microcode2ucode.c from $FILESDIR.
- Expert users can use the new MICROCODE_SIGNATURES variable to install
only a subset of microcodes on their system, as requested by bug
643786.
- Avoids accidently bloated split-ucode files per bug #644100.
- USE=monolithic is no longer supported, please see iucode_tool for any
fallback.
- USE=initramfs now writes to /boot/intel-uc.img (8.3-safe naming).
Fixes: https://bugs.gentoo.org/643786
Fixes: https://bugs.gentoo.org/644100
Package-Manager: Portage-2.3.16, Repoman-2.3.6
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added:
(06-3c-03): 0x0022 -> 0x0023
(06-3d-04): 0x0025 -> 0x0028
(06-45-01): 0x0020 -> 0x0021
(06-4e-03): 0x00ba -> 0x00c2
(06-5c-09): 0x002c -> 0x002e
(06-8e-09): 0x0062 -> 0x007c
(06-9e-09): 0x005e -> 0x007c
Bug: https://bugs.gentoo.org/643794
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|