| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
| |
Closes: https://bugs.gentoo.org/666588
|
|
|
|
| |
Closes: https://bugs.gentoo.org/666588
|
|
|
|
| |
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
| |
- Updated Microcodes:
sig 0x00030678, pf_mask 0x0c, 2018-01-10, rev 0x0836 -> 2018-01-25, rev 0x0837
sig 0x000906ec, pf_mask 0x22, 2018-05-31, rev 0x0098 -> 2018-08-26, rev 0x009e
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
| |
Also restirct mirror and bindist
Closes: https://bugs.gentoo.org/664134
Package-Manager: Portage-2.3.48, Repoman-2.3.10
RepoMan-Options: --force
|
|
|
|
|
|
|
| |
...and logging improved
Closes: https://bugs.gentoo.org/656992
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Changed package version schema [Bug 662098#c3]:
Main version will now be based on latest Intel snapshot date.
Patch version will now be based on latest collection snapshot date.
- Updated Microcodes:
sig 0x000506c2, pf_mask 0x01, 2017-06-06, rev 0x000e -> 2018-05-11, rev 0x0014
sig 0x000506f1, pf_mask 0x01, 2017-11-22, rev 0x0020 -> 2018-05-11, rev 0x0024
sig 0x000706a1, pf_mask 0x01, 2017-12-26, rev 0x0022 -> 2018-05-22, rev 0x0028
Bug: https://bugs.gentoo.org/662098
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Updated Microcodes:
sig 0x000106e5, pf_mask 0x13, 2018-01-24, rev 0x0009 -> 2018-05-08, rev 0x000a
sig 0x00020652, pf_mask 0x12, 2018-02-04, rev 0x0010 -> 2018-05-08, rev 0x0011
sig 0x00020655, pf_mask 0x92, 2018-01-23, rev 0x0006 -> 2018-04-23, rev 0x0007
sig 0x000506ca, pf_mask 0x03, 2017-11-22, rev 0x0008 -> 2018-05-11, rev 0x000c
sig 0x000906ec, pf_mask 0x22, 2018-05-08, rev 0x0096 -> 2018-05-31, rev 0x0098
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
|
|
|
|
| |
- Updated Microcodes:
sig 0x00050653, pf_mask 0x97, 2018-01-29, rev 0x1000140 -> 2018-04-20, rev 0x1000144
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Downgraded Microcodes:
sig 0x000706a1, pf_mask 0x01, 2018-05-11, rev 0x0026 -> 2017-12-26, rev 0x0022
"This MCU has been reverted to a previous version while Intel
investigates a sighting related to this MCU. This error is currently
under investigation and no workaround has been identified. Intel
currently is recommending to stop deployment of version 0x26 and revert
to the previous production version 0x22. Intel will provide an update on
progress in 2 weeks." [Link 1]
- Updated Microcodes:
sig 0x000106a5, pf_mask 0x03, 2018-01-24, rev 0x001c -> 2018-05-11, rev 0x001d
sig 0x000206c2, pf_mask 0x03, 2018-01-23, rev 0x001e -> 2018-05-08, rev 0x001f
sig 0x000206e6, pf_mask 0x04, 2018-01-18, rev 0x000c -> 2018-05-15, rev 0x000d
sig 0x000206f2, pf_mask 0x05, 2018-01-19, rev 0x003a -> 2018-05-16, rev 0x003b
sig 0x00050662, pf_mask 0x10, 2018-01-22, rev 0x0015 -> 2018-05-25, rev 0x0017
sig 0x00050663, pf_mask 0x10, 2018-01-22, rev 0x7000012 -> 2018-04-20, rev 0x7000013
sig 0x00050664, pf_mask 0x10, 2018-01-22, rev 0xf000011 -> 2018-04-20, rev 0xf000012
sig 0x00050665, pf_mask 0x10, 2018-01-22, rev 0xe000009 -> 2018-04-20, rev 0xe00000a
sig 0x00060663, pf_mask 0x80, 2018-01-25, rev 0x0016 -> 2018-04-17, rev 0x002a
sig 0x000806eb, pf_mask 0xc0, 2018-02-11, rev 0x0084 -> 2018-05-30, rev 0x0098
sig 0x000906ec, pf_mask 0x22, 2018-02-19, rev 0x0084 -> 2018-05-08, rev 0x0096
Link 1: https://www.intel.com/content/dam/www/public/us/en/documents/sa00115-microcode-update-guidance.pdf
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|