All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: "open list:-----------------..." <qemu-devel@nongnu.org>,
	Sergey Fedorov <serge.fdrv@gmail.com>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] .travis.yml: Disable IRC build status updates from forks
Date: Tue, 28 Jun 2016 17:09:56 +0100	[thread overview]
Message-ID: <87bn2le1m3.fsf@linaro.org> (raw)
In-Reply-To: <CAJhHMCD_vfn4Cb=J0H3LUgoSnb0PcRcZLF3btY7qj0f78MJT=w@mail.gmail.com>


Pranith Kumar <bobby.prani@gmail.com> writes:

> On Tue, Jun 28, 2016 at 7:58 AM, Alex Bennée <alex.bennee@linaro.org> wrote:
>>>
>>> +# The channel name "irc.oftc.net#qemu" is encrypted against qemu/qemu
>>> +# to prevent IRC notifications from forks. This was created using:
>>> +# $ travis encrypt -r "qemu/qemu" "irc.oftc.net#qemu"
>>
>> Interesting. I didn't realise anyone outside the repository can still
>> create encrypted strings. I guess there is a repository secret that we
>> never see.
>
> Yes, there is a per-repo private key which is not disclosed to anyone
> and is used to decrypt this string. You can only have access to the
> public key of the repo to create the encrypted string as above.

Cool. Applied to travis/next.

Thanks.

--
Alex Bennée

      reply	other threads:[~2016-06-28 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 18:13 [Qemu-devel] [PATCH v2] .travis.yml: Disable IRC build status updates from forks Pranith Kumar
2016-06-28 11:58 ` Alex Bennée
2016-06-28 13:35   ` Pranith Kumar
2016-06-28 16:09     ` Alex Bennée [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=87bn2le1m3.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=bobby.prani@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=serge.fdrv@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.