user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: meta@public-inbox.org
Subject: Re: Add "generator" information to HTML pages
Date: Sun, 8 Jan 2023 19:47:38 +0000	[thread overview]
Message-ID: <20230108194738.M225235@dcvr> (raw)
In-Reply-To: <20230108190404.nghzrip46oh4wl3p@snowball.t-8ch.de>

Thomas Weißschuh <thomas@t-8ch.de> wrote:
> Hi,
> 
> it would be nice if public-inbox could extend the HTML pages it
> generates with the "generator" meta tag [0].
> Especially the version would be useful.
> 
> This would help users during debugging to see the specific version of
> public-inbox they are looking at.

What would users be debugging?
Admins would be the only ones who care, I think...

Version info becomes worthless if an admin blocks/alters certain
endpoints via nginx/varnish or just editing the code.

> For example:
> 
> <head>
>   <title>Some page</title>
>   <meta name="generator" content="public-inbox 1.9.0" />
> </head>

I prefer to disclose as little information as possible in case
vulnerabilities are found.  Alone, security by obscurity doesn't work,
but obscurity does make things more difficult for attackers
(same reason camouflage exists).

I also don't like wasting memory+bandwidth on things most users
won't see or care about.  This is especially true for stuff at
the beginnning of the output since that's most likely to succeed
in being transferred.

> [0] https://html.spec.whatwg.org/multipage/semantics.html#meta-generator
> 
> Thanks,
> Thomas

  reply	other threads:[~2023-01-08 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-08 19:04 Add "generator" information to HTML pages Thomas Weißschuh
2023-01-08 19:47 ` Eric Wong [this message]
2023-01-08 20:02   ` Thomas Weißschuh
2023-01-08 20:58     ` Eric Wong
2023-01-08 21:54       ` Thomas Weißschuh

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

  List information: https://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20230108194738.M225235@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=thomas@t-8ch.de \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).