From: valdis.kletnieks@vt.edu
To: Lev Olshvang <levonshe@yandex.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: mount /proc at boot as read-only
Date: Sun, 06 Jan 2019 17:45:33 -0500 [thread overview]
Message-ID: <11334.1546814733@turing-police.cc.vt.edu> (raw)
In-Reply-To: <28484691546798406@myt4-415a3339794b.qloud-c.yandex.net>
On Sun, 06 Jan 2019 21:13:26 +0300, Lev Olshvang said:
> I am trying to harden the embedded system.
> I have embedded system with systemd .....
OK, you've already got a problem right there.
It's an embedded system. Therefor, you know everything that should be running,
and what order it should start in. If you don't already know that, you have bigger
design issues.
So you probably want to reduce system complexity and save both RAM and flash
memory space by heaving systemd over the side and using something simpler
(sysvinit, or upstart, or even use '/bin/make' if you want to guarantee that
certain tasks don't start till others have actually launched successfully, or
use a custom-written system launcher).
That's going to do more to reduce the attack surface than any amount of monkeying
around with the permissions in /proc will do.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-01-06 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 18:13 mount /proc at boot as read-only Lev Olshvang
2019-01-06 22:45 ` valdis.kletnieks [this message]
2019-01-07 8:35 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11334.1546814733@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=levonshe@yandex.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).