Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to [GNG] Gated, Filtered alt.comp.a...  <--  <--- Return to Home Page
   Networked Database  [GNG] Gated, Filtered alt.comp.a...   [477 / 759] RSS
 From   To   Subject   Date/Time 
Message   Virus    All   Re: Questions about Spectre / Meltdown CPU vulnerabilities   January 4, 2018
 1:18 AM *  

From: Virus <Virus@Guy.C0M>

David W. Hodgins wrote:

>> I'd like to see a complete breakdown of the status of all Intel CPU's,
>> going back to at least the SLOT-1 products and including socket 370,
>> socket 478 and socket 775.
> 
> Unlikely that there will be such a list. All cpus are affected. 

Well, they do say that anything prior to 1995, and (in the case of Intel 
Atom) prior to 2013.  I have some Atom-powered netbooks that would 
therefore not be vulnerable.

> It provides read access to tiny amounts of data at a time. Given the
> multi-processor/multi-threading of processors, the volume of data the
> exploit would have to sift through to find any thing of use, is massive.

That's one thing I don't understand, based on current reports.

Do operating systems of any or all sorts keep passwords in "special", 
strategic or universally-accepted locations in RAM such that sifting 
through gb worth of memory dump would not be required?

To just even go about excercising the vulnerability, would the required 
code be so specifically crafted such that the exact model/type of CPU 
AND the particular OS would both be needed to be known in order for the 
code to perform the intended memory dump operation?

Would there be any quirks of particular operating systems that would 
render this vulnerability of little or no value, because of workability 
issues?  I'm thinking of differences between, say, Win-9x/me vs any of 
the NT-based Windoze.  Differences in how memory is used by the kernel, 
etc.

I don't believe that win-9x/me has any notion or ability to separate 
memory access between applications, and I've never heard of any sort of 
"password" attack or comprimize that is specific to 9x/me that has any 
relavence to a user system.
--- NewsGate v1.0 gamma 2
 * Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to [GNG] Gated, Filtered alt.comp.a...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.083 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_c5lnbq4k1d39vkva5tjgi01vs3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_c5lnbq4k1d39vkva5tjgi01vs3, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_c5lnbq4k1d39vkva5tjgi01vs3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0