9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] mimetype: add entry for .patch extension
Date: Wed, 10 Feb 2021 13:18:03 +0100	[thread overview]
Message-ID: <CAFSF3XMTRDEpjMkGoVojWVJWxR8Oc6iqyeWwpoS8_BTuBVt-DQ@mail.gmail.com> (raw)
In-Reply-To: <339fdc13-8fbd-46bb-ac4e-69f44a8844b7@sirjofri.de>

i still want a virus encoded either into a filename or into some magic
bytes that file will stumble over hahaha :D

lyndon's point stands, also for webservers.

it's silly that webservers are expected to run filename heuristics
just so that it can lie to the browser about what filetype it might
be.

it breaks too often in practice, i don't like it.

and the browser never does what i want, i can't force it to just
DISPLAY the image even though the webserver claims it can only be
downloaded to disk.

maybe all this together is even more messy than that little itch with
mail content types that makes people feel so much more safe
doubleclicking on every attachment they get.

On 2/10/21, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>
> 09.02.2021 06:08:56 ori@eigenstate.org:
>> Quoth Michael Forney <mforney@mforney.org>:
>>> This way, upas/vf won't flag .patch files as suspicious by default.
>>>
>>> diff [...]
>>
>> Seems good, but for most purposes, it also seems
>> reasonable to just 'rm /mail/lib/validateattachment';
>> I don't think it really does anything useful for mail
>> on plan 9.
>
> If you don't think about mail, but http servers: at least rc-httpd uses
> it to construct content-type headers. It extends this list (which btw
> doesn't include css and js). I'm not sure about ip/httpd or tcp80.
>
> I have some extensions for rc-httpd I did for gridchat-web, that included
> basic range handling as well as POST. I wanted to prepare a patch. It's
> on https://github.com/sirjofri/gridchat-web, if someone else wants to do
> it (it's very easy, but contains one auxiliary native program for range
> handling. I can try some chain using cat file | {read -c $start
>>/dev/null; read -c $end} instead and see if it's faster than dd. Sorry
> for offtopic).
>
> sirjofri
>

  reply	other threads:[~2021-02-10 12:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 23:07 Michael Forney
2021-02-09  5:08 ` ori
2021-02-10  2:54   ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-02-10  7:31   ` sirjofri
2021-02-10 12:18     ` hiro [this message]
2021-02-10 21:59   ` Michael Forney

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=CAFSF3XMTRDEpjMkGoVojWVJWxR8Oc6iqyeWwpoS8_BTuBVt-DQ@mail.gmail.com \
    --to=23hiro@gmail.com \
    --cc=9front@9front.org \
    /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).