XEROF

 

Flaw in kernel priviledge memory access ?


I am a bit troubled by the announce that most CPUs out there have a flaw related to kernel mode and priviledge access to memory. The reason why is why should applications store data in memory in the clear? Why shouldn't modern applications store hash and/or encrypted data anytime they are dealing with sensitive data?
So we are supposed to be let known that servers out there host different websites using the same memory base, i.e. shared memory. I think any such website should be shut for endangering their users. Any website worth its salt, pardon the irony (NB : salt is a crypto keyword), should host sensitive data, if in the clear, using non-shared memory, period. And of course, sensitive data should not be stored in the clear, not in the hard drive, not in memory either : it is a matter of good principle.

With those principles implemented, today's cataclismic revelation is just a non-story.

Posted on 04-January-2018 12:07 | Category: News | comment[0] | trackback[0]

 

 

<-- previous page

< July >
0102030405
0607080910
1112131415
1617181920
2122232425
2627282930
31



 

 

This site
Home
Articles

DevTools
CPU-Z
EditPlus
ExplorerXP
Kill.exe
OllyDbg
DependencyWalker
Process Explorer
autoruns.exe
Araxis
COM Trace injection
CodeStats
NetBrute
FileMon/Regmon
BoundsChecker
AQTime profiler
Source monitor
GDI leaks tracking
Rootkit revealer
Rootkit removal
RunAsLimitedUser(1)
RunAsLimitedUser(2)

 

 

Liens
Le Plan B
Un jour à Paris
Meneame
Rezo.net (aggr)
Reseau voltaire
Cuba solidarity project
Le grand soir
L'autre journal
Le courrier suisse
L'Orient, le jour
Agoravox (aggr)