From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org
Subject: Re: Random GitHub Actions added to git/git???
Date: Wed, 21 Apr 2021 16:05:08 -0700 [thread overview]
Message-ID: <xmqqlf9bxmqj.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2104211437040.54@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 21 Apr 2021 14:38:06 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Tue, 20 Apr 2021, Junio C Hamano wrote:
>
>> How well are our refs protected from these random "Actions"? Can
>> somebody spam us with a pull request with a new "workflow" that
>> advances one of our integration branches ;-)?
>
> The GITHUB_TOKEN that is used by the GitHub workflows is generated in two
> ways, depending whether a PR originated from the same repository or from a
> fork. If it came from a fork, the token has only read permissions.
>
> So I'd say we're still safe.
Yeah, their blog post came to my inbox, which was quite timely, this
morning ;-).
https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/
prev parent reply other threads:[~2021-04-21 23:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 0:29 Random GitHub Actions added to git/git??? Junio C Hamano
2021-04-20 0:41 ` Taylor Blau
2021-04-20 16:23 ` Taylor Blau
2021-04-20 9:48 ` Bagas Sanjaya
2021-04-20 15:55 ` Johannes Schindelin
2021-04-20 15:51 ` Johannes Schindelin
2021-04-20 20:23 ` Junio C Hamano
2021-04-21 12:38 ` Johannes Schindelin
2021-04-21 23:05 ` Junio C Hamano [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=xmqqlf9bxmqj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).