emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andrea <agiugliano@live.it>
To: bzg@gnu.org
Cc: hj-orgmode-1@hj.proberto.com, emacs-orgmode@gnu.org, tecosaur@gmail.com
Subject: Re: Shower thought: submit an IETF RFC to register Org as a MIME type
Date: Thu, 24 Sep 2020 22:25:04 +0200	[thread overview]
Message-ID: <AM7P189MB06966A5BFAFC2ECF82BC5184C7390@AM7P189MB0696.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: 87r1qt9cf0.fsf@gnu.org


What are the pros?

About the cons: maybe we need to look more into the requirements.

I am looking at https://tools.ietf.org/html/rfc2048 and the one that
concerns me a little is 2.2.6: I guess somebody would need to write a
bit of docs about security concerns. Or you can go the way Markdown did
it: from https://tools.ietf.org/html/rfc7763#section-2

"Security considerations:

      Markdown interpreted as plain text is relatively harmless.  A text
      editor need only display the text.  The editor SHOULD take care to
      handle control characters appropriately and to limit the effect of
      the Markdown to the text-editing area itself; malicious Unicode-
      based Markdown could, for example, surreptitiously change the
      directionality of the text.  An editor for normal text would
      already take these control characters into consideration, however.

      Markdown interpreted as a precursor to other formats, such as
      HTML, carries all of the security considerations as the target
      formats.  For example, HTML can contain instructions to execute
      scripts, redirect the user to other web pages, download remote
      content, and upload personally identifiable information.  Markdown
      also can contain islands of formal markup, such as HTML.  These
      islands of formal markup may be passed as they are, transformed,
      or ignored (perhaps because the islands are conditional or
      incompatible) when the Markdown is processed.  Since Markdown may
      have different interpretations depending on the tool and the
      environment, a better approach is to analyze (and sanitize or
      block) the output markup, rather than attempting to analyze the

Do they have an org-babel?



             reply	other threads:[~2020-09-24 20:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 20:25 Andrea [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-22  1:21 Shower thought: submit an IETF RFC to register Org as a MIME type Carlos Pita
2021-10-23  6:45 ` Ihor Radchenko
2021-10-23  8:34   ` Carlos Pita
2021-10-23  8:36     ` Timothy
2020-09-24 20:25 Andrea
2020-09-04 14:44 TEC
2020-09-04 16:14 ` Gustav Wikström
2020-09-05  5:30 ` stardiviner
2020-09-05  5:50   ` Bastien
2020-09-05  5:53     ` TEC
2020-09-17  7:09       ` TEC
2020-09-17  7:18         ` hj-orgmode-1
2020-09-23  7:31           ` Bastien
2020-10-01  3:40             ` TEC
2020-10-01  5:21               ` Bastien
2020-10-01  5:48                 ` TEC
2020-10-01  6:46                   ` Bastien
2020-10-01 15:39               ` Wes Hardaker
2020-10-01 15:45                 ` TEC
2020-10-06 18:03                   ` Wes Hardaker
2020-10-06 19:03                     ` TEC
2020-10-06 20:39                       ` Palak Mathur
2020-10-24 12:09                     ` Bastien
2020-10-24 12:28                       ` Palak Mathur
2020-10-24 12:50                         ` Bastien
2020-10-24 13:09                           ` Leo Vivier
2020-10-24 13:38                             ` Bastien
2020-10-24 13:49                               ` Leo Vivier
2020-10-24 15:12                                 ` Bastien
2020-10-24 15:00                           ` Palak Mathur
2020-10-24 15:40                             ` Bastien
2020-10-24 15:57                               ` Palak Mathur
2020-10-14  9:52               ` Lennart C. Karssen
2020-10-14 14:22                 ` Nicolas Goaziou
2021-03-23  3:00 ` Timothy

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM7P189MB06966A5BFAFC2ECF82BC5184C7390@AM7P189MB0696.EURP189.PROD.OUTLOOK.COM \
    --to=agiugliano@live.it \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=hj-orgmode-1@hj.proberto.com \
    --cc=tecosaur@gmail.com \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).