unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>,
	Ronak B <ronakworks@gmail.com>,
	56512@debbugs.gnu.org
Subject: bug#56512: gnu.org does not redirect http to https
Date: Tue, 12 Jul 2022 17:03:53 +0600	[thread overview]
Message-ID: <87czea1tk6.fsf@disroot.org> (raw)
In-Reply-To: <A1E852D6-E452-4EE8-816A-CBB3256B461E@lepiller.eu>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

Julien Lepiller <julien@lepiller.eu> writes:

> Guix does not control the infrastructure behind the GNU project. You need to contact the GNU sysadmins, though I don't know how :)

Check out <https://www.gnu.org/contact/>, it contains some information
that might be interesting to you.

Quoting from that page:

> Security reports 
> for gnu.org or one of its subdomains
> 
> * If you have GnuPG setup, send encrypted email the FSF Executive
>   Director, Deputy Director, Web Developer, and Senior Sysadmins
>   listed on our Staff and Board page.
> * If you don't have GnuPG setup, write to <sysadmin@gnu.org>.

And obviously, there is Richard Stallman <rms@gnu.org>.

-- 
Akib Azmain Turja

This message is signed by me with my GnuPG key.  It's fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-07-12 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  0:45 bug#56512: gnu.org does not redirect http to https Ronak B
2022-07-12 10:19 ` Julien Lepiller
2022-07-12 11:03   ` Akib Azmain Turja via Bug reports for GNU Guix [this message]
2022-07-12 12:13     ` Ronak B
2022-07-12 20:19       ` Csepp
2022-07-14  1:56       ` Maxim Cournoyer

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=87czea1tk6.fsf@disroot.org \
    --to=bug-guix@gnu.org \
    --cc=56512@debbugs.gnu.org \
    --cc=akib@disroot.org \
    --cc=julien@lepiller.eu \
    --cc=ronakworks@gmail.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).