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]
Message-ID: <CAKYAXd9=KE6wwcCQ+Khfy0N6uBizQEvoLCiu9vzbskGHtmsS4A@mail.gmail.com>
Date:	Mon, 19 Sep 2011 12:56:16 +0900
From:	NamJae Jeon <linkinjeon@...il.com>
To:	Chris Ball <cjb@...top.org>
Cc:	Linus Walleij <linus.ml.walleij@...il.com>,
	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: RFC : mmc : boot partition is set as a read-write.

2011/9/19 Chris Ball <cjb@...top.org>:
> Hi,
>
> On Sun, Sep 18 2011, NamJae Jeon wrote:
>> mmc : boot partition is set as a read-write.
>>
>> There is a case that user directly update boot partition through mmcblk0boot0,1.
>> However, the current boot partition is set as a read-only.
>> I suggest that boot partition is set as a read-write if there is no
>> reason that it should be read-only.
>
> There is a reason.
>
> Documentation/mmc/mmc-dev-parts.txt:
>
> MMC Boot Partitions
> ===================
>
> Read and write access is provided to the two MMC boot partitions. Due to
> the sensitive nature of the boot partition contents, which often store
> a bootloader or bootloader configuration tables crucial to booting the
> platform, write access is disabled by default to reduce the chance of
> accidental bricking.
>
> To enable write access to /dev/mmcblkXbootY, disable the forced read-only
> access with:
>
> echo 0 > /sys/block/mmcblkXbootY/force_ro
>
> ==
> - Chris.
> --
> Chris Ball   <cjb@...top.org>   <http://printf.net/>
> One Laptop Per Child
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Hi. Chris.

There is the way you are.

Thanks a lot.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ