* Upstream Spectre CVE Patch Availability
@ 2018-01-19 1:45 Brian Inglis
2018-01-19 1:55 ` Brian Inglis
2018-01-19 7:21 ` Yaakov Selkowitz
0 siblings, 2 replies; 3+ messages in thread
From: Brian Inglis @ 2018-01-19 1:45 UTC (permalink / raw)
To: cygwin
Hi folks,
Not seen any posts here about the monster in the chip yet (although those who
might know may be busy dealing with the issues in their jobs), so has anyone any
idea if or when we might see upstream Spectre CVE patches available for the
following packages, whose bases have been mentioned in the many articles
published recently, and has anyone seen mention of any other packages likely to
be affected?
cygwin32-gcc-core 6.4.0-1
djgpp-gcc-core 5.4.0-1
gcc-core 6.4.0-4
libjavascriptcoregtk3.0_0 2.0.4-5
libvirt-common 3.6.0-1
libwebkitgtk3.0_0 2.0.4-5
mingw64-i686-gcc-core 6.4.0-1
mingw64-x86_64-gcc-core 6.4.0-2
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Upstream Spectre CVE Patch Availability
2018-01-19 1:45 Upstream Spectre CVE Patch Availability Brian Inglis
@ 2018-01-19 1:55 ` Brian Inglis
2018-01-19 7:21 ` Yaakov Selkowitz
1 sibling, 0 replies; 3+ messages in thread
From: Brian Inglis @ 2018-01-19 1:55 UTC (permalink / raw)
To: cygwin
On 2018-01-18 18:45, Brian Inglis wrote:
> Hi folks,
>
> Not seen any posts here about the monster in the chip yet (although those who
> might know may be busy dealing with the issues in their jobs), so has anyone any
> idea if or when we might see upstream Spectre CVE patches available for the
> following packages, whose bases have been mentioned in the many articles
> published recently, and has anyone seen mention of any other packages likely to
> be affected?
>
> cygwin32-gcc-core 6.4.0-1
> djgpp-gcc-core 5.4.0-1
> gcc-core 6.4.0-4
> libjavascriptcoregtk3.0_0 2.0.4-5
> libvirt-common 3.6.0-1
> libwebkitgtk3.0_0 2.0.4-5
> mingw64-i686-gcc-core 6.4.0-1
> mingw64-x86_64-gcc-core 6.4.0-2
Forgot about:
llvm 5.0.1-1
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Upstream Spectre CVE Patch Availability
2018-01-19 1:45 Upstream Spectre CVE Patch Availability Brian Inglis
2018-01-19 1:55 ` Brian Inglis
@ 2018-01-19 7:21 ` Yaakov Selkowitz
1 sibling, 0 replies; 3+ messages in thread
From: Yaakov Selkowitz @ 2018-01-19 7:21 UTC (permalink / raw)
To: cygwin
[-- Attachment #1.1: Type: text/plain, Size: 752 bytes --]
On 2018-01-18 19:45, Brian Inglis wrote:
> Not seen any posts here about the monster in the chip yet (although those who
> might know may be busy dealing with the issues in their jobs), so has anyone any
> idea if or when we might see upstream Spectre CVE patches available for the
> following packages, whose bases have been mentioned in the many articles
> published recently, and has anyone seen mention of any other packages likely to
> be affected?
The most important thing you can do is make sure you apply all Windows
updates. To whatever degree these can be mitigated in userspace, we're
all still waiting for code to land elsewhere (namely, Fedora); we simply
don't have the resources to work on this ourselves.
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-01-19 7:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-19 1:45 Upstream Spectre CVE Patch Availability Brian Inglis
2018-01-19 1:55 ` Brian Inglis
2018-01-19 7:21 ` Yaakov Selkowitz
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 read-only IMAP folder(s) and NNTP newsgroup(s).