You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Thilo Goetz <tw...@gmx.de> on 2007/01/25 15:45:43 UTC
Instructions for release verification
You may have noticed that I put some instructions on how to verify
release artifacts on the downloads page:
http://incubator.apache.org/uima/downloads.html#VerifyDownload
I would appreciate it if people could review the information there (as
I'm completely new to all this) and even try it out themselves. I have
put a distribution archive, together with the appropriate signature
files, on people (Apache committers only, I don't want to put this on a
public server). You can find the files in
/home/twgoetz/uimaTestDistribution. Please let me know if you find any
issues.
--Thilo
Re: Instructions for release verification
Posted by Mirko Jahn <mi...@gmail.com>.
Hi Thilo,
thanks for your clarification. That answered my questions. Apache does
it a little bit different than I was used to it, but that's fine for
me, as long as it is consistent (, which it is here).
The information on the FAQ seem to be very good. I haven't tried them
yet in practice, but as far as I recall my experiences with it, all
important points are mentioned there.
Thanks again.
-- Mirko
On 1/29/07, Thilo Goetz <tw...@gmx.de> wrote:
> Hi Mirko,
>
> thanks for your feedback. I guess my documentation was not as clear as
> I thought it was.
>
> Mirko Jahn wrote:
> > Hmm, I am not quite sure if I really understood how it will works or I
> > missed some explanations...
> >
> > You wrote on the UIMA website something like "[...] the UIMA
> > developers' public keys [...]" and referred to them as the keys with
> > which each jar is signed. I thought, there will be one key (associated
> > to an address like uima__at__apache.org), which will sign these jars.
> > Not an individual committer (well usually you use a special domain
> > certificate of the organization to sign such things).
>
> No, each release is signed by the current release manager, which is me
> for this release, and possibly somebody else for following releases. It
> is convenient for each developer who might sign a release to add his/her
> key to the KEYS file so that whoever signed the release, the appropriate
> key is in there.
>
> >
> > If I got it right and it was the intention to have the committers
> > signature, I think it is a good idea to have a distinct person
> > associated with that role, instead of having multiple signatures
> > flying around.
>
> See above.
>
> >
> > The third thing I can imagine is to let multiple committers sign the
> > jars. This might be more secure (not sure if this make sense), but is
> > not common. At least, I haven't seen it yet.
> >
> > Another thing is that the public key(s) can also be stored in official
> > pgp key servers (Just search for "pgp keyserver" to get examples).
> > This makes it easier to get for actual users and harder to fraud all
> > of them at once. Presenting the public key as a string on the website
> > might be a good idea as well.
>
> Yes, I do mention that actually.
>
> >
> > However, no matter which way you choose to talk, I think it is a good
> > idea to start signing the key(s). I remember several key signing
> > parties in Stuttgart or probably the apachecon is a good place to do
> > that, too. (Does anyone know anything about a general apache.org
> > recommendation concerning this?)
>
> Yes, one step at a time ;-) I only created my first key pair about a
> week ago.
>
> >
> > Well, if I missed some documents/threads discussing this, just let me
> > know. I just wanted to address some things, which look different for
> > me here than in other projects I know.
>
> I think we're following the standard procedure as far as Apache projects
> go. The best resource is the release signing FAQ, also referenced from
> the pages I created. I actually submitted patch for the FAQ last week
> with some additional info, which has since been applied.
>
> Since with the patch, the FAQ is now pretty complete (as far as I'm
> concerned), I will scale back the release signing info on the UIMA pages
> and mostly just point at the FAQ. I hope this will also help to avoid
> this kind of confusion.
>
> If you think the general Apache release signing FAQ
> (http://www.apache.org/dev/release-signing.html) is not clear or
> incomplete as well, let us know and we'll work on improving it.
>
> --Thilo
>
>
Re: Instructions for release verification
Posted by Thilo Goetz <tw...@gmx.de>.
Hi Mirko,
thanks for your feedback. I guess my documentation was not as clear as
I thought it was.
Mirko Jahn wrote:
> Hmm, I am not quite sure if I really understood how it will works or I
> missed some explanations...
>
> You wrote on the UIMA website something like "[...] the UIMA
> developers' public keys [...]" and referred to them as the keys with
> which each jar is signed. I thought, there will be one key (associated
> to an address like uima__at__apache.org), which will sign these jars.
> Not an individual committer (well usually you use a special domain
> certificate of the organization to sign such things).
No, each release is signed by the current release manager, which is me
for this release, and possibly somebody else for following releases. It
is convenient for each developer who might sign a release to add his/her
key to the KEYS file so that whoever signed the release, the appropriate
key is in there.
>
> If I got it right and it was the intention to have the committers
> signature, I think it is a good idea to have a distinct person
> associated with that role, instead of having multiple signatures
> flying around.
See above.
>
> The third thing I can imagine is to let multiple committers sign the
> jars. This might be more secure (not sure if this make sense), but is
> not common. At least, I haven't seen it yet.
>
> Another thing is that the public key(s) can also be stored in official
> pgp key servers (Just search for "pgp keyserver" to get examples).
> This makes it easier to get for actual users and harder to fraud all
> of them at once. Presenting the public key as a string on the website
> might be a good idea as well.
Yes, I do mention that actually.
>
> However, no matter which way you choose to talk, I think it is a good
> idea to start signing the key(s). I remember several key signing
> parties in Stuttgart or probably the apachecon is a good place to do
> that, too. (Does anyone know anything about a general apache.org
> recommendation concerning this?)
Yes, one step at a time ;-) I only created my first key pair about a
week ago.
>
> Well, if I missed some documents/threads discussing this, just let me
> know. I just wanted to address some things, which look different for
> me here than in other projects I know.
I think we're following the standard procedure as far as Apache projects
go. The best resource is the release signing FAQ, also referenced from
the pages I created. I actually submitted patch for the FAQ last week
with some additional info, which has since been applied.
Since with the patch, the FAQ is now pretty complete (as far as I'm
concerned), I will scale back the release signing info on the UIMA pages
and mostly just point at the FAQ. I hope this will also help to avoid
this kind of confusion.
If you think the general Apache release signing FAQ
(http://www.apache.org/dev/release-signing.html) is not clear or
incomplete as well, let us know and we'll work on improving it.
--Thilo
Re: Instructions for release verification
Posted by Marshall Schor <ms...@schor.com>.
Yes, ApacheCon 2006 had a key-signing "party".... -Marshall
Mirko Jahn wrote:
> Hmm, I am not quite sure if I really understood how it will works or I
> missed some explanations...
>
> You wrote on the UIMA website something like "[...] the UIMA
> developers' public keys [...]" and referred to them as the keys with
> which each jar is signed. I thought, there will be one key (associated
> to an address like uima__at__apache.org), which will sign these jars.
> Not an individual committer (well usually you use a special domain
> certificate of the organization to sign such things).
>
> If I got it right and it was the intention to have the committers
> signature, I think it is a good idea to have a distinct person
> associated with that role, instead of having multiple signatures
> flying around.
>
> The third thing I can imagine is to let multiple committers sign the
> jars. This might be more secure (not sure if this make sense), but is
> not common. At least, I haven't seen it yet.
>
> Another thing is that the public key(s) can also be stored in official
> pgp key servers (Just search for "pgp keyserver" to get examples).
> This makes it easier to get for actual users and harder to fraud all
> of them at once. Presenting the public key as a string on the website
> might be a good idea as well.
>
> However, no matter which way you choose to talk, I think it is a good
> idea to start signing the key(s). I remember several key signing
> parties in Stuttgart or probably the apachecon is a good place to do
> that, too. (Does anyone know anything about a general apache.org
> recommendation concerning this?)
>
> Well, if I missed some documents/threads discussing this, just let me
> know. I just wanted to address some things, which look different for
> me here than in other projects I know.
>
> -- Mirko
> btw.: this might be worth looking at: http://www.cacert.org/
>
> On 1/26/07, Thilo Goetz <tw...@gmx.de> wrote:
>> Yes, that is expected. I haven't gotten around to the whole
>> web-of-trust/certified keys thing yet.
>>
>> Adam Lally wrote:
>> > On 1/25/07, Thilo Goetz <tw...@gmx.de> wrote:
>> >> You may have noticed that I put some instructions on how to verify
>> >> release artifacts on the downloads page:
>> >> http://incubator.apache.org/uima/downloads.html#VerifyDownload
>> >>
>> >> I would appreciate it if people could review the information there
>> (as
>> >> I'm completely new to all this) and even try it out themselves. I
>> have
>> >> put a distribution archive, together with the appropriate signature
>> >> files, on people (Apache committers only, I don't want to put this
>> on a
>> >> public server). You can find the files in
>> >> /home/twgoetz/uimaTestDistribution. Please let me know if you
>> find any
>> >> issues.
>> >>
>> >
>> > +1.
>> >
>> > I tried it and it worked. Although I did get the (expected?) warning:
>> >
>> > gpg: WARNING: This key is not certified with a trusted signature!
>> > gpg: There is no indication that the signature belongs to the
>> > owner.
>> >
>> > -Adam
>>
>
>
Re: Instructions for release verification
Posted by Mirko Jahn <mi...@gmail.com>.
Hmm, I am not quite sure if I really understood how it will works or I
missed some explanations...
You wrote on the UIMA website something like "[...] the UIMA
developers' public keys [...]" and referred to them as the keys with
which each jar is signed. I thought, there will be one key (associated
to an address like uima__at__apache.org), which will sign these jars.
Not an individual committer (well usually you use a special domain
certificate of the organization to sign such things).
If I got it right and it was the intention to have the committers
signature, I think it is a good idea to have a distinct person
associated with that role, instead of having multiple signatures
flying around.
The third thing I can imagine is to let multiple committers sign the
jars. This might be more secure (not sure if this make sense), but is
not common. At least, I haven't seen it yet.
Another thing is that the public key(s) can also be stored in official
pgp key servers (Just search for "pgp keyserver" to get examples).
This makes it easier to get for actual users and harder to fraud all
of them at once. Presenting the public key as a string on the website
might be a good idea as well.
However, no matter which way you choose to talk, I think it is a good
idea to start signing the key(s). I remember several key signing
parties in Stuttgart or probably the apachecon is a good place to do
that, too. (Does anyone know anything about a general apache.org
recommendation concerning this?)
Well, if I missed some documents/threads discussing this, just let me
know. I just wanted to address some things, which look different for
me here than in other projects I know.
-- Mirko
btw.: this might be worth looking at: http://www.cacert.org/
On 1/26/07, Thilo Goetz <tw...@gmx.de> wrote:
> Yes, that is expected. I haven't gotten around to the whole
> web-of-trust/certified keys thing yet.
>
> Adam Lally wrote:
> > On 1/25/07, Thilo Goetz <tw...@gmx.de> wrote:
> >> You may have noticed that I put some instructions on how to verify
> >> release artifacts on the downloads page:
> >> http://incubator.apache.org/uima/downloads.html#VerifyDownload
> >>
> >> I would appreciate it if people could review the information there (as
> >> I'm completely new to all this) and even try it out themselves. I have
> >> put a distribution archive, together with the appropriate signature
> >> files, on people (Apache committers only, I don't want to put this on a
> >> public server). You can find the files in
> >> /home/twgoetz/uimaTestDistribution. Please let me know if you find any
> >> issues.
> >>
> >
> > +1.
> >
> > I tried it and it worked. Although I did get the (expected?) warning:
> >
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg: There is no indication that the signature belongs to the
> > owner.
> >
> > -Adam
>
Re: Instructions for release verification
Posted by Thilo Goetz <tw...@gmx.de>.
Yes, that is expected. I haven't gotten around to the whole
web-of-trust/certified keys thing yet.
Adam Lally wrote:
> On 1/25/07, Thilo Goetz <tw...@gmx.de> wrote:
>> You may have noticed that I put some instructions on how to verify
>> release artifacts on the downloads page:
>> http://incubator.apache.org/uima/downloads.html#VerifyDownload
>>
>> I would appreciate it if people could review the information there (as
>> I'm completely new to all this) and even try it out themselves. I have
>> put a distribution archive, together with the appropriate signature
>> files, on people (Apache committers only, I don't want to put this on a
>> public server). You can find the files in
>> /home/twgoetz/uimaTestDistribution. Please let me know if you find any
>> issues.
>>
>
> +1.
>
> I tried it and it worked. Although I did get the (expected?) warning:
>
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the
> owner.
>
> -Adam
Re: Instructions for release verification
Posted by Adam Lally <al...@alum.rpi.edu>.
On 1/25/07, Thilo Goetz <tw...@gmx.de> wrote:
> You may have noticed that I put some instructions on how to verify
> release artifacts on the downloads page:
> http://incubator.apache.org/uima/downloads.html#VerifyDownload
>
> I would appreciate it if people could review the information there (as
> I'm completely new to all this) and even try it out themselves. I have
> put a distribution archive, together with the appropriate signature
> files, on people (Apache committers only, I don't want to put this on a
> public server). You can find the files in
> /home/twgoetz/uimaTestDistribution. Please let me know if you find any
> issues.
>
+1.
I tried it and it worked. Although I did get the (expected?) warning:
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
-Adam