Hi Kees,
On Thursday 25 April 2013 02:15 AM, Kees Cook wrote:
On Tue, Apr 23, 2013 at 11:19 PM, Aruna Balakrishnaiah
wrote:
Currently the kernel provides the contents of p-series NVRAM only as a
simple stream of bytes via /dev/nvram, which must be interpreted in user
space by the nvram
On Tue, Apr 23, 2013 at 11:19 PM, Aruna Balakrishnaiah
wrote:
> Currently the kernel provides the contents of p-series NVRAM only as a
> simple stream of bytes via /dev/nvram, which must be interpreted in user
> space by the nvram command in the powerpc-utils package. This patch set
> exploits
Currently the kernel provides the contents of p-series NVRAM only as a
simple stream of bytes via /dev/nvram, which must be interpreted in user
space by the nvram command in the powerpc-utils package. This patch set
exploits the pstore subsystem to expose each partition in NVRAM as a
separate file
Currently the kernel provides the contents of p-series NVRAM only as a
simple stream of bytes via /dev/nvram, which must be interpreted in user
space by the nvram command in the powerpc-utils package. This patch set
exploits the pstore subsystem to expose each partition in NVRAM as a
separate file
On Tue, Apr 23, 2013 at 11:19 PM, Aruna Balakrishnaiah
ar...@linux.vnet.ibm.com wrote:
Currently the kernel provides the contents of p-series NVRAM only as a
simple stream of bytes via /dev/nvram, which must be interpreted in user
space by the nvram command in the powerpc-utils package. This
Hi Kees,
On Thursday 25 April 2013 02:15 AM, Kees Cook wrote:
On Tue, Apr 23, 2013 at 11:19 PM, Aruna Balakrishnaiah
ar...@linux.vnet.ibm.com wrote:
Currently the kernel provides the contents of p-series NVRAM only as a
simple stream of bytes via /dev/nvram, which must be interpreted in user
6 matches
Mail list logo
