From: Kurt H Maier <firstname.lastname@example.org> To: email@example.com Subject: Re: [9front] 4chan hacked rc-httpd Date: Thu, 31 Mar 2022 13:17:48 -0700 [thread overview] Message-ID: <YkYMbLjSN0+XYyxM@wopr> (raw) In-Reply-To: <firstname.lastname@example.org> On Thu, Mar 31, 2022 at 07:35:37PM +0000, sirjofri wrote: > Hey, > > doesn't rc-httpd bind /usr/web / like tcp80 and httpd does? At least, it > could mkdir /usr/web/bin && bind /bin /usr/web/bin and then bind /usr/web > /. > > At least that's what I'd do. > > I tested on my web server which runs tcp80 and I didn't have an issue > like that. > > sirjofri Patches welcome -- currently we're just kicking out errors for requests with this crap in the url. khm
next prev parent reply other threads:[~2022-03-31 20:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-31 18:10 sl 2022-03-31 19:35 ` sirjofri 2022-03-31 20:17 ` Kurt H Maier [this message] 2022-03-31 20:26 ` Stanley Lieber 2022-04-03 3:26 ` sl 2022-04-03 18:05 ` adr 2022-03-31 20:29 ` ori 2022-03-31 23:54 ` Avalon Williams 2022-04-01 0:38 ` Kurt H Maier
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=YkYMbLjSN0+XYyxM@wopr \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [9front] 4chan hacked rc-httpd' \ /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).