We have a nice guide linked off the website that I think Andy wrote:
https://nifi.apache.org/gpg.html
>From the perspective of Github verified commits, I think it only
really relies on you having added the public GPG key into your account
under settings "SSH and GPG keys", and the fact that the
I tried once to publish a GPG key I generated on my MBP, but didn't seem to
be able to get far with it. Are there any good ASF-centric resources for
setting up a GPG key?
Thanks,
Mike
On Wed, Jun 12, 2019 at 2:20 AM Koji Kawamura
wrote:
> Thanks Bryan for the heads up.
>
> My GPG key had been
Thanks Bryan for the heads up.
My GPG key had been expired. I've renewed my KEY by extending expiration.
Now I confirmed that my commits is marked as 'verified' on Github.
Koji
On Wed, Jun 12, 2019 at 5:43 AM Andy LoPresto wrote:
>
> Peter,
>
> If you have specific issues setting it up, I’m
Peter,
If you have specific issues setting it up, I’m happy to help debug. I haven’t
done it recently but am willing to investigate with you.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jun 11, 2019,
I will admit I've never setup GPG signing on Linux. I'm sure there are
some additional challenges there.
Not sure if it is helpful, but there are a few things related to Linux
that are mentioned on this Github page:
https://help.github.com/en/articles/telling-git-about-your-signing-key
On Tue,
Yep, I support these suggestions.
Setting up GPG does have a learning curve for folks that haven't done
it before, but I think our community would be helpful in assisting
folks on the mailing list and Apache NiFi Slack where they run into
trouble. It's a good practice to learn and once setup
I like having signed commits. I develop on both Windows and Linux, but have
only had success getting signing working on Windows (which was a bit
complicated as it was). You can see when I switched from mostly Windows to
mostly Linux by when I stopped signing commits...
Thanks,
Peter
