Re: [RFC PATCH 0/2] Add named reference to latest push cert
- From
Stefan Beller <sbeller@google.com>
- Date
- Sep 7, 2017, 17:21 UTC
- Message-ID
- <CAGZ79kb3vv0sfqRBjJwOb1vFGeRgztZRdbqinv89NmhQaAb9CA@mail.gmail.com>
- In-Reply-To
- <20170907070827.sysqmszdwduruwis@weakknees.security.iitk.ac.in>
On Thu, Sep 7, 2017 at 12:08 AM, Shikher Verma <root@shikherverma.com> wrote:
> Hey everyone, > > I felt like I should introduce myself since this is my first patch on > the git mailing list (or any mailing list actually) :D
Welcome to the list. :)
Show 11 quoted lines
> I am Shikher[1], currently in my 4th year undergrad at IIT Kanpur. > This summer I was lucky enough to intern at NYU Secure Systems Lab[2] > mentored by Santiago. We looked into how signed pushes work and how > we can use them to increase the security of git. We encountered a > strange error in tests which resulted in a patch[3] and I wrote a > python script to verify push certificates[4]. I was pretty surprised > to not find any push certificate on the remote repo after I did a > signed push, hence this RFC. > > Anyway this is my first time trying to contribute to a large OSS so > forgive me if I make any noob mistakes.
Patches are very welcome. Everyone was a noob once, but that changes quickly.
Thanks, Stefan