From: email@example.com To: firstname.lastname@example.org Subject: Re: [9front] git: use new /dev/drivers for privdrop Date: Sat, 28 May 2022 15:41:53 -0400 [thread overview] Message-ID: <FA4FA4789598BE723F7D8E68D7D8AA37@eigenstate.org> (raw) In-Reply-To: <6D0CAE9C3EDDCF15EF90F526821E14E6@smtp.pobox.com> Quoth email@example.com: > For example, say I want a sandboxing area for people to "try 9front". > With moody's recent work, it removes a big attack vector by > restricting certain drivers. But isn't it still possible to fork-bomb > a server, or to just cause unnecessary churn (i.e., computation), or > just open too many files, or fill a disk? Yes. I'm not aware of anyone trying to protect against denial of service with shared resources. This work mostly is about preventing data leakage.
next prev parent reply other threads:[~2022-05-28 19:43 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-28 16:51 ori 2022-05-28 19:23 ` unobe 2022-05-28 19:41 ` ori [this message] 2022-05-28 22:54 ` Jacob Moody 2022-05-29 0:23 ` Frank D. Engel, Jr. 2022-05-29 1:00 ` Jacob Moody 2022-05-28 21:47 ` covertusername967 2022-05-28 22:07 ` ori 2022-05-28 23:24 ` adr
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=FA4FA4789598BE723F7D8E68D7D8AA37@eigenstate.org \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [9front] git: use new /dev/drivers for privdrop' \ /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
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).