From: "Frank Ch. Eigler via Gdb" <gdb@sourceware.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>,
Christophe Lyon <christophe.lyon@linaro.org>,
binutils@sourceware.org, elfutils-devel@sourceware.org,
gcc@gcc.gnu.org, gdb@sourceware.org, libc-alpha@sourceware.org,
libabigail@sourceware.org, newlib@sourceware.org
Subject: Re: scraperbot protection - Patchwork and Bunsen behind Anubis
Date: Wed, 23 Apr 2025 13:49:23 -0400 [thread overview]
Message-ID: <aAkoI9v_N5tgjED7@elastic.org> (raw)
In-Reply-To: <CAPS5khZh78WSrjokQe1o9C8M8qDFiYbxUur8yxnGnBAPTHHCzg@mail.gmail.com>
Hi -
> We were wondering if it would be possible / suitable to have https
> requests served by one container,
> and ssh ones by another? Maybe that's already the case though...
SSH stuff is already (un)contained.
> [...]
> so maybe it would help if we switched to ssh access for our CI user
> when cloning GCC / binuitls / etc sources?
What you'd need is a ssh identity with logon access for the bots.
That's not something we normally do (sourceware accounts are personal
and usually have read-write access to -some- git repos.) But we could
support read-only ssh accounts for bots. (read-only for safety, i.e.,
not member of any particular git unix-group/project.)
- FChE
prev parent reply other threads:[~2025-04-23 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 15:59 Mark Wielaard
2025-04-22 12:34 ` Guinevere Larsen via Gdb
2025-04-22 13:06 ` Jonathan Wakely via Gdb
2025-04-22 13:17 ` Guinevere Larsen via Gdb
2025-04-22 14:44 ` Jonathan Wakely via Gdb
2025-04-22 21:39 ` Aurelien Jarno via Gdb
2025-04-23 3:52 ` Chris Packham via Gdb
2025-04-23 16:56 ` Christophe Lyon via Gdb
2025-04-23 17:49 ` Frank Ch. Eigler via Gdb [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aAkoI9v_N5tgjED7@elastic.org \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=libabigail@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=newlib@sourceware.org \
--cc=overseers@sourceware.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox