From: ludo@gnu.org (Ludovic Courtès)
To: Jean Louis <guix@rcdrun.com>
Cc: 22972@debbugs.gnu.org
Subject: bug#22972: insecure content on: https://gnu.org/software/guix/packages/
Date: Fri, 25 Mar 2016 13:35:17 +0100 [thread overview]
Message-ID: <87k2kqpwfu.fsf@gnu.org> (raw)
In-Reply-To: <20160325094356.GK5051@protected.rcdrun.com> (Jean Louis's message of "Fri, 25 Mar 2016 10:43:56 +0100")
Jean Louis <guix@rcdrun.com> skribis:
> The content is insecure as shown by Icecat.
IceCat doesn’t “show” me this. What are you referring to?
> That happens because either scripts are included (did not check it)
> which are with http:// or images (I did check it).
Right, project logos come from different places, and not necessarily
https. I understand that this can be a problem. However, at least for
now, we don’t copy those logos to www.gnu.org, so it seems there’s not
much we can do.
> Small remark to the page with packages: it is in few lines,
> which makes editing, even with Emacs harder. There shall be new lines or
> indenting after > or after each package. Otherwise it makes editing the
> HTML very hard (I know there is source, but looking inside of HTML is
> difficult).
As you write, this is not meant to be edited, so… :-)
> The package descriptions shall not be opened by Javascript but on the
> long run, each package shall get its own page, and of course there shall
> be search engine, just like with Debian. This all becomes totally easy
> with guix being Guile module, and exciting.
Yes, definitely. Dave’s guix-web¹ does that and more. I think we
should consider running it with actions disabled (i.e., no
installing/removing/upgrading), probably behind nginx to cache things a
bit.
Any takers?
Thanks,
Ludo’.
¹ https://git.dthompson.us/guix-web.git
next prev parent reply other threads:[~2016-03-25 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 0:10 bug#22972: insecure content on: https://gnu.org/software/guix/packages/ Jean Louis
2016-03-25 8:28 ` Ludovic Courtès
2016-03-25 9:43 ` Jean Louis
2016-03-25 12:35 ` Ludovic Courtès [this message]
2018-02-05 21:46 ` Andreas Enge
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2kqpwfu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22972@debbugs.gnu.org \
--cc=guix@rcdrun.com \
/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://git.savannah.gnu.org/cgit/guix.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).