unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-sysadmin <guix-sysadmin@gnu.org>,
	Altadil <Altadil@protonmail.com>,
	65056@debbugs.gnu.org
Subject: bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor
Date: Sun, 13 Aug 2023 02:25:51 +0200	[thread overview]
Message-ID: <877cpzbxf4.fsf@gnu.org> (raw)
In-Reply-To: <10e9eb490471d421fa709eaa36bdec83@tobias.gr> (Tobias Geerinckx-Rice's message of "Fri, 04 Aug 2023 21:21:33 +0200")

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

Hi,

(Cc: guix-sysadmin.)

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> On 2023-08-04 18:57, Altadil via Bug reports for GNU Guix wrote:

[...]

>> The result is an error message saying: "The connection has timed out".
>> It looks like a general block of Tor rather than a block of specific
>> IPs, since attempting with different Tor circuits does not change the
>
> The Guix project does not block Tor.  If the datacentre has decided to
> block Tor like it blocked most of Russia, there is little we can do
> but ask them to reconsider.

I think it’s worse than this.  I noticed that ci.guix.gnu.org (same
machine) would occasionally time out on my side, without Tor, starting
from this week (I was on vacation before, so I don’t know exactly when
it started).  From a browser, I get this “DoS attack” HTML page:


[-- Attachment #2: The "DoS attack" page. --]
[-- Type: image/png, Size: 37908 bytes --]

[-- Attachment #3: Type: text/plain, Size: 860 bytes --]


The HTML doesn’t contain clues as to where it originates from.

--8<---------------cut here---------------start------------->8---
$ wget -qO- http://ci.guix.gnu.org | tail
        </style>
        <title>Attack Detected</title>
    </head>
    <body><div class="message-container">
    <div class="logo"></div>
    <h1>Blocked because of DoS Attack</h1>
    <p>Your computer has been blocked because a DoS attack originating from your system was detected. For more information, contact the system administrator.</p>
</div></body>
</html>
--8<---------------cut here---------------end--------------->8---

Some firewall-ish network equipment must be sitting right before our
machine.  It’s a problem because fetching narinfos and nars is likely to
count as a “DoS attack”.

Could it be some change at the MDC?

Thanks,
Ludo’.

  parent reply	other threads:[~2023-08-13  0:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 16:57 bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor Altadil via Bug reports for GNU Guix
2023-08-04 19:21 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-08-04 19:29   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-08-13  0:25   ` Ludovic Courtès [this message]
2023-08-13 11:46     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-08-14  9:07       ` Ricardo Wurmus
2023-09-08 20:24         ` Ludovic Courtès
2023-09-12  8:02           ` Ricardo Wurmus
2023-09-12 13:06             ` Maxim Cournoyer
2023-09-14 21:25             ` Ludovic Courtès
2023-09-15  7:41               ` Ricardo Wurmus
2023-09-18  9:51                 ` Ludovic Courtès
2023-09-20 21:31                   ` Giovanni Biscuolo
2023-09-20 22:45                     ` Ricardo Wurmus
2023-09-21  6:27                       ` Giovanni Biscuolo
2023-10-02  8:48                       ` Ludovic Courtès
2023-09-18 20:31 ` bug#65056: https://issues.guix.gnu.org available through Tor again Altadil via Bug reports for GNU Guix
2023-09-21  6:29   ` Giovanni Biscuolo

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=877cpzbxf4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=65056@debbugs.gnu.org \
    --cc=Altadil@protonmail.com \
    --cc=guix-sysadmin@gnu.org \
    --cc=me@tobias.gr \
    /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).