Petr Štetiar <[email protected]> writes: Dear Maintainers,
> Unless there is a good reason to have this enabled, it should stay > disabled in official builds and "but Debian has it enabled" is not > valid argument either. Now that it's being decided that macro CONFIG_DEVMEM shall not be enabled by default, why can't bug ID FS#3461 be closed? Regards, Supriya Mane On Thu, Mar 11, 2021 at 6:24 PM Supriya Shekhar Mane <[email protected]> wrote: > > Hi Petr, > > As CONFIG_DEVMEM shall not be enabled by default, then this ticket can be > moved to closure. > Please suggest the closing procedure. > > Regards, > Supriya Mane > > On Sun, Feb 14, 2021 at 8:39 PM Petr Štetiar <[email protected]> wrote: >> >> Bjørn Mork <[email protected]> [2021-02-14 10:33:15]: >> >> Hi, >> >> > And it's already enabled for the ipq807x and rockchip targets, so you can't >> > really claim that it's not available in OpenWrt either. >> >> thanks to bringing this to my attention, but I tend to believe, that this is >> not intentional. >> >> > I do hope you don't think OpenWrt is somehow more secure than a current >> > Debian installation because you arbitrarily remove kernel features like >> > this one? >> >> Unless there is a good reason to have this enabled, it should stay disabled >> in >> official builds and "but Debian has it enabled" is not valid argument either. >> >> > The security issues in OpenWrt are caused by almost every process running >> > as >> > root. >> >> Thanks to Daniel, this is getting reduced like dnsmasq, logd, ntp, ubus to >> name a few. >> >> Cheers, >> >> Petr >> >> _______________________________________________ >> openwrt-devel mailing list >> [email protected] >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Disclaimer:This message is intended only for the designated recipient(s). It may contain confidential or proprietary information and may be subject to other confidentiality protections. If you are not a designated recipient, you may not review, copy or distribute this message. Please notify the sender by e-mail and delete this message. GlobalEdge does not accept any liability for virus infected mails. _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
