public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Vulnerability info in /sys
Date: Thu, 15 Feb 2018 03:22:37 +0200	[thread overview]
Message-ID: <p62n7b$ca$1@blaine.gmane.org> (raw)
In-Reply-To: <d3336d73-bcce-3f0a-7745-ad08d4b73401@gmail.com>

On 15/02/18 02:57, Daniel Frey wrote:
> On 02/14/18 09:29, Nikos Chantziaras wrote:
>> On 14/02/18 04:38, Daniel Frey wrote:
>>> On 02/12/18 19:39, Ian Zimmerman wrote:
>>>> On 2018-02-12 19:24, Daniel Frey wrote:
>>>>
>>>>> I've read online that there should be vulnerability info (Meltdown,
>>>>> Spectre) in /sys under /sys/devices/system/cpu/vulnerabilities but this
>>>>> doesn't exist on my PC.
>>>>> [...]
>>>>
>>>> See the other threads: you need at least 4.9.79 for the /sys bits.
>>>> [...]
>>>
>>> I'm surprised I missed those threads, I read all messages on here.
>>> According to the thread I found it's actually starts on 4.9.77, I'm just
>>> on the latest stable (.76).
>>
>> During "special emergencies" like this one, it would be a good idea to
>> use the latest 4.9.x, regardless of whether portage marked it "stable"
>> or not. At least for a while and until the situation has settled down
>> again.
>>
>>
> 
> Nah, I like stability over everything else. I recall lots of pain and
> instability in January when everyone rushed to patch the flaws (both
> Windows and linux.)
> 
> These are my personal computers, not a work environment.

Personal preference of course, but I prefer to risk some instability 
compared to risking having a bitcoin miner infesting my PC or some 
botnet worm.

That's just me though.



      reply	other threads:[~2018-02-15  1:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13  3:24 [gentoo-user] Vulnerability info in /sys Daniel Frey
2018-02-13  3:39 ` [gentoo-user] " Ian Zimmerman
2018-02-14  2:38   ` Daniel Frey
2018-02-14  3:19     ` Ian Zimmerman
2018-02-14 17:29     ` Nikos Chantziaras
2018-02-15  0:57       ` Daniel Frey
2018-02-15  1:22         ` Nikos Chantziaras [this message]

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='p62n7b$ca$1@blaine.gmane.org' \
    --to=realnc@gmail.com \
    --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