The part I find really scary with all of this, as Keith is saying, we
are fixing hardware with software, meaning someone can "unpatch" the
change.
I don't believe that processor microcode can be "unpatched" nor can it
easily be patched again to undo what was done.
However, what I see as the rea
http://www.dw.com/en/new-security-flaw-detected-in-intel-hardware/a-42122823
New flaw in intel amt. again
Also. The new fix for spdctre and meltdown causes uncontrolled reboots in some
haswell and broadwell processors.
> On Jan 12, 2018, at 2:09 PM, Nathan O'Brennan wrote:
>
>
> Would SELi
I am fairly sure selinux does not have any protection against this.
> On Jan 12, 2018, at 2:09 PM, Nathan O'Brennan wrote:
>
>
> Would SELinux protect in any way against either of these vulnerabilities?
>
>
>> On 2018-01-12 00:18, Joseph Sinclair wrote:
>> Feel free to repost anywhere. I do
What you point out is great in a sterile / lab environment, but not in
the wild. I am hoping the courts will find the chip manufactures liable
for not doing more QA. These chips are used in banking, government, all
sorts of business, and by consumers. We have become so dependent on
compute
hah! with my ears, I don't care how bloody silent they make the things, I can
still hear those blades slicing the air at 5 miles.
-eric
from the central offices of the Technomage Guild, Sensors Dept.
On Jan 12, 2018, at 3:53 AM, Aaron Jones wrote:
> https://www.airspacemag.com/military-aviation
https://www.airspacemag.com/military-aviation/air-americas-black-helicopter-24960500/
This article says they flew Laos to NV. But I swear the first time I heard this
story the teller said Cambodia. The pilot on this did a really cool writeup I
can’t find any more about his experience.
I would
Yes. There were a couple of details I wanted but was not finding. Thank
you.
On Jan 11, 2018 7:24 PM, "Aaron Jones" wrote:
Thanks Joe.
You should blog an article about this cuz that was the best explanation for
the issue I have read so far.
> On Jan 11, 2018, at 6:42 PM, Joseph Sinclair
wrote
Feel free to repost anywhere. I don't have a blog site I use; so no real place
to post a full article...
On 2018-01-11 07:24 PM, Aaron Jones wrote:
> Thanks Joe.
>
> You should blog an article about this cuz that was the best explanation for
> the issue I have read so far.
>
>> On Jan 11, 2
On Thu, 11 Jan 2018 10:29:33 -0700
Aaron Jones wrote:
> We had a silent helicopter we used in Vietnam to tap wires in
> cambodia.
>
> We tapped wires miles under water during the cold war.
[snip]
>
> But you don't believe someone could be tasked with purposefully
> adding a back door to som
Thanks Joe.
You should blog an article about this cuz that was the best explanation for the
issue I have read so far.
> On Jan 11, 2018, at 6:42 PM, Joseph Sinclair
> wrote:
>
> There seems to be a lot of confusion surrounding the recently disclosed CPU
> hardware issues...
> A few points
lol, spell check is no match for my vocabulary!
I meant brutal. This group can be brutal.
On 2018-01-11 15:59, Mark Phillips wrote:
> Hmmmviscous, as in we are all a little dense? or vicious as in brutal?
> Perhaps a little bit of both?? ;)
>
> Nathan - my apologies if I have offended y
There seems to be a lot of confusion surrounding the recently disclosed CPU
hardware issues...
A few points to consider:
1) This is a cache timing attack using speculative execution (a key performance
feature in the hardware) that exposes data (i.e. it's not an exploit to "take
over" a system);
The management engine has it's own issues, including not allowing non-signed
software to be installed or executed (read the FSF article for further details).
-eric
from the central offices of the Technomage Guild, the "just the facts, Ma'am"
Dept.
On Jan 11, 2018, at 8:47 AM, Stephen Partington
Hmmmviscous, as in we are all a little dense? or vicious as in brutal?
Perhaps a little bit of both?? ;)
Nathan - my apologies if I have offended you, because that was not my
intentionjust trying to lighten the mood a little.
Mark
On Thu, Jan 11, 2018 at 3:23 PM, Nathan O'Brennan
wrote:
Wow, this group is viscous. Remind me never again to post *any* form of
opinion.
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinf
While you may not be an agent for Kim Jong-un, it's completely within
the realm of possibilities. This is a huge problem and there may be
HUGE consequences.
Not so fun when YOU'RE the target of accusations masked as ambiguity,
is it?
There's a reason we were taught at the age of 10 not to spread
> Original Message
>Subject: Re: Post : INTEL’S SECURITY FLAW IS NO FLAW
>Local Time: January 11, 2018 10:36 AM
>UTC Time: January 11, 2018 5:36 PM
>From: techli...@phpcoderusa.com
>To: Main PLUG discussion list
>
>This is basic stuff. Kernel memory mus
This is basic stuff. Kernel memory must be segregated and each
application's memory must be segregated. These are the basics of CPU
functionality. That is why I find theses issues perplexing. And it
leads me to one basic question. If these problems persisted since 1995,
how could these issue go
effectively
>>>> insane, since your owner is actually many people, all with different and
>>>> often diametrically opposing goals for the company).
>>>>
>>>> Anyway, tell you what - go read the Intel hardware docs and see if you can
>>>>
ed to put together to see the bug. And this with
>> prior knowledge of where to look.
>>
>> I will say that this doesn't excuse much, but realize that being a public
>> company drives you insane ;-)
>>
>> Rusty
>>
>> -Original Message-
&
ompany drives you insane ;-)
>>
>> Rusty
>>
>> -----Original Message-
>> From: PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] On
>> Behalf Of techli...@phpcoderusa.com
>> Sent: Thursday, January 11, 2018 8:42 AM
>> To: Main PLUG d
ompany drives you insane ;-)
>>
>> Rusty
>>
>> -----Original Message-
>> From: PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] On
>> Behalf Of techli...@phpcoderusa.com
>> Sent: Thursday, January 11, 2018 8:42 AM
>> To: Main PLUG d
s.phxlinux.org] On
> Behalf Of techli...@phpcoderusa.com
> Sent: Thursday, January 11, 2018 8:42 AM
> To: Main PLUG discussion list
> Subject: Re: Post : INTEL’S SECURITY FLAW IS NO FLAW
>
> ...
>
> I've read these issues may have persisted as far back as 1995. How does
&
you insane ;-)
Rusty
-Original Message-
From: PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] On Behalf
Of techli...@phpcoderusa.com
Sent: Thursday, January 11, 2018 8:42 AM
To: Main PLUG discussion list
Subject: Re: Post : INTEL’S SECURITY FLAW IS NO FLAW
...
I've read t
Two is one and one is none. A single flaw can get patched. Multiple flaws and
over lapping issues can be pointed out as mistakes and at least one method
might still work.
Other than dlink, no one is stupid enough to declare their vulnerabilities and
attacks. Right?
#Super secret anti iran fla
Something to consider is the the meltdown and spectre flaws are entirely
seperate than the management engine. Which has known vulnerabilities.
On Jan 11, 2018 8:41 AM, wrote:
>
>
> While this article may not be factual, it is completely within the realm
> of possibilities. This is a huge problem
While this article may not be factual, it is completely within the realm
of possibilities. This is a huge problem and there may be HUGE
consequences.
What I'd like to know is how these issues persisted for over 20 years
without detection. I assume Intel, AMD and the other chip manufactures
On Wed, 10 Jan 2018 09:39:54 -0700
techli...@phpcoderusa.com wrote:
> Hi,
>
> Who knows if this is true, however here it is:
>
> https://www.reddit.com/r/CBTS_Stream/comments/7pb7pv/intels_security_flaw_is_no_flaw/?st=jc9a2mp7&sh=7ef2e2c1
I would hope people smart enough and possessing enou
gt; think they also tried to build more than one hardware system, so that a bug
> wouldn’t take the whole thing down. Pretty hard to do something like that,
> back then, but quite impossible today.
> __
>
> On 20180110, at 12:15, Matthew Crews wrote:
>
> ---- Origin
offices of the Technomage Guild, the "poking the eye of the
powers-that-be" Dept.
On Jan 10, 2018, at 12:15 PM, Matthew Crews wrote:
>> Original Message ----
>> Subject: Re: Post : INTEL’S SECURITY FLAW IS NO FLAW
>> Local Time: January 10, 2018 10:
ct: Re: Post : INTEL’S SECURITY FLAW IS NO FLAW
> Local Time: January 10, 2018 10:33 AM
> UTC Time: January 10, 2018 5:33 PM
> From: retro64...@gmail.com
> To: Main PLUG discussion list
>
>
> I thought we all knew that intel has hardware level access points baked into
> t
> Original Message
>Subject: Re: Post : INTEL’S SECURITY FLAW IS NO FLAW
>Local Time: January 10, 2018 10:33 AM
>UTC Time: January 10, 2018 5:33 PM
>From: retro64...@gmail.com
>To: Main PLUG discussion list
>
>
>I thought we all knew that intel has h
I thought we all knew that intel has hardware level access points baked into
the system specifically for the INTELigence agencies.
See what I did there? Hah!
But seriously... If its not baked in, they just intercept devices in the mail
and solder in their own goodies. So what does it REALLY ma
Hi,
Who knows if this is true, however here it is:
https://www.reddit.com/r/CBTS_Stream/comments/7pb7pv/intels_security_flaw_is_no_flaw/?st=jc9a2mp7&sh=7ef2e2c1---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubsc
34 matches
Mail list logo
