[PATCH] realtek: make Netgear GS108T v3 u-boot env partition writable

Signed-off-by: Stijn Segers --- target/linux/realtek/dts-5.10/rtl8380_netgear_gigabit_1xx.dtsi | 1 - 1 file changed, 1 deletion(-) diff --git a/target/linux/realtek/dts-5.10/rtl8380_netgear_gigabit_1xx.dtsi b/target/linux/realtek/dts-5.10/rtl8380_netgear_gigabit_1xx.dtsi index 7eccfcb5a2..fd44

Re: Query regd. rw rootfs

Hi, > As mentioned in https://openwrt.org/docs/techref/preinit_mount#failsafeBy, > rootfs is made rw via overlay. So, even a non-root user will have the > ability to modify (for e.g. delete dnsmasq entry in /etc/passwd). no, a non-root user will lack sufficient permission to modify these files.

[PATCH] ath79: add DT compatible property for all "u-boot-env" MTD partitions

From: Rafał Miłecki This allows operating systems to handle U-Boot environment variables (e.g. read them) if needed. This is useful e.g. for an upcoming Linux NVMEM driver. sed -i 's/^\(\s*\)\(label = "u-boot-env";\)/\1compatible = "u-boot,env";\n\1\2/' target/linux/ath79/dts/* Signed-off-by:

RE: Query regd. rw rootfs

> What is the actual problem you are trying to solve? If a user possesses > enough permissions to modify /etc/passwd) he might as well modify init > scripts, replace legitimate executables with malicious ones or simply replace > the running firmware altogether by reflashing another image. As men

Re: Query regd. rw rootfs

Not that I would know, being a user not a developer > On Jun 16, 2022, at 13:33, Ravi Paluri (QUIC) > wrote: > > Hi jo, > >>> it is not the same. There is no special handling for specific overlay file >>> paths in procd. > If the behavior is not same, can you let me know how "below" is

Re: Query regd. rw rootfs

Hi, > If the behavior is not same, can you let me know how "below" is > handled/taken care in OpenWRT? "changes made to sensitive files for e.g. > /etc/passwd (deleting a line. Deleting passwd file etc.) will have adverse > impact on security and some init scripts may not start etc." OpenWrt d

RE: Query regd. rw rootfs

Hi jo, >> it is not the same. There is no special handling for specific overlay file >> paths in procd. If the behavior is not same, can you let me know how "below" is handled/taken care in OpenWRT? "changes made to sensitive files for e.g. /etc/passwd (deleting a line. Deleting passwd fi

Re: Query regd. rw rootfs

Hi, > [...] > Is this behavior the same with procd? it is not the same. There is no special handling for specific overlay file paths in procd. ~ Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lis

Re: [PATCH v2 0/6] ath79: convert QCA955x-based D-Link DAP-2xxx to nvmem

Hi Sebastian, On Mon, 2022-06-13 at 22:15 +0200, Sander Vanheule wrote: > Convert the QCA955x based devices to nvmem-cell based calibration data > extraction, so this can be removed from the init scripts. > > Changes in v2: > - Put nvmem cell definition directly into partition node > > Sander Va

Query regd. rw rootfs

Hi All, I'm new to OpenWRT development. I see below text from OpenWRT documentation @ https://openwrt.org/docs/techref/preinit_mount#failsafe. "The root file system is actually an overlay which can be consisted of a read-only SquashFS file system (mounted at /rom) and a writable JFFS2 partiti