lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 2 Apr 2021 13:57:38 +0000
From:   "Winkler, Tomas" <tomas.winkler@...el.com>
To:     "Enrico Weigelt, metux IT consult" <lkml@...ux.net>,
        Rajneesh Bhardwaj <irenic.rajneesh@...il.com>,
        "Box, David E" <david.e.box@...el.com>,
        "Hans de Goede" <hdegoede@...hat.com>,
        Mark Gross <mgross@...ux.intel.com>
CC:     "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Mashiah, Tamar" <tamar.mashiah@...el.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: RE: [PATCH] platform/x86: intel_pmc_core: export platform
 global_reset via sysfs.



> -----Original Message-----
> From: Enrico Weigelt, metux IT consult <lkml@...ux.net>
> Sent: Friday, April 02, 2021 16:32
> To: Winkler, Tomas <tomas.winkler@...el.com>; Rajneesh Bhardwaj
> <irenic.rajneesh@...il.com>; Box, David E <david.e.box@...el.com>; Hans
> de Goede <hdegoede@...hat.com>; Mark Gross <mgross@...ux.intel.com>
> Cc: platform-driver-x86@...r.kernel.org; linux-kernel@...r.kernel.org;
> Mashiah, Tamar <tamar.mashiah@...el.com>; Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com>
> Subject: Re: [PATCH] platform/x86: intel_pmc_core: export platform
> global_reset via sysfs.
> 
> On 01.04.21 23:31, Tomas Winkler wrote:
> 
> Hi,
> 
> > During PCH manufacturing a global reset has to be induced in order for
> > configuration changes take affect upon following platform reset.
> > This setting was commonly done by accessing PMC registers via /dev/mem
> > but due to security concern /dev/mem access is much restricted, hence
> > the reason for exposing this setting via dedicated sysfs interface.
> > To prevent post manufacturing abuse the register is protected by
> > hardware locking.
> 
> could you please define "manufacturing" ? The chip or board ?
Board
> 
> Is there any use for this, after the machine left the factory ?

Refurbishing, mostly, the register is hw locked after that.

> 
> 
> --mtx
> 
> --
> ---
> Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
> werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
> GPG/PGP-Schlüssel zu.
> ---
> Enrico Weigelt, metux IT consult
> Free software and Linux embedded engineering info@...ux.net -- +49-151-
> 27565287

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ