Re: How to help OpenSSL

I see. Thank you. 2014-04-28 0:48 GMT+08:00 Dr. Stephen Henson : > On Sun, Apr 27, 2014, Weibin Yao wrote: > >> Is it accessable for read (rt.openssl.org) ? I can't access it and >> don't know where to register. >> > > Read access is possible through the guest account: > > https://www.openssl.org/

Re: How to help OpenSSL

On Sun, Apr 27, 2014, Weibin Yao wrote: > Is it accessable for read (rt.openssl.org) ? I can't access it and > don't know where to register. > Read access is possible through the guest account: https://www.openssl.org/support/rt.html Steve. -- Dr Stephen N. Henson. OpenSSL project core develop

Re: How to help OpenSSL

Is it accessable for read (rt.openssl.org) ? I can't access it and don't know where to register. 2014-04-27 5:35 GMT+08:00 Matt Caswell : > On 25 April 2014 18:24, Kurt Roeckx wrote: >> On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote: >>> >>> 1. Triage RT (https://rt.openssl.org/). >>

Re: How to help OpenSSL

On 25 April 2014 18:24, Kurt Roeckx wrote: > On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote: >> >> 1. Triage RT (https://rt.openssl.org/). > > I think part of this means that you'll need to give some people > access to it so they can actually modify the tickets. I now have access to R

Re: How to help OpenSSL

On Sat, Apr 26, 2014 at 11:39:13AM +0100, Ben Laurie wrote: > On 24 April 2014 19:54, Kurt Roeckx wrote: > > On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote: > >> Note that this is just how to help me, not a consensus view from the > >> whole team, though I have no doubt much of it will

Re: How to help OpenSSL

Oh, absolutely I've verified it. :-) I'll get that turned around to you shortly. Mike On Sat, Apr 26, 2014 at 6:33 AM, Ben Laurie wrote: > On 24 April 2014 18:44, Mike Bland wrote: > > On Thu, Apr 24, 2014 at 1:31 PM, Ben Laurie wrote: > >> > >> 6. Write new tests > >> > >> Our test suite s

Re: How to help OpenSSL

On 24 April 2014 19:54, Kurt Roeckx wrote: > On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote: >> Note that this is just how to help me, not a consensus view from the >> whole team, though I have no doubt much of it will be helpful to the >> team, too. >> >> 1. Triage RT (https://rt.open

Re: How to help OpenSSL

On 25 April 2014 00:08, Matt Caswell wrote: > Ben - Is it possible for some of us to get RT users created? The above > assumes we can configure RT statuses - is this possible? I think you now have RT access, right? __ OpenSSL Pro

Re: How to help OpenSSL

On 24 April 2014 18:44, Mike Bland wrote: > On Thu, Apr 24, 2014 at 1:31 PM, Ben Laurie wrote: >> >> 6. Write new tests >> >> Our test suite sucks. More tests is better. > > > Shall I send a pull request for this: > > https://github.com/mbland/openssl/commit/a7a9e18b550edf059dfd54683ac1f45170ff9f

Re: How to help OpenSSL

I should've said: if a fix is for a potential security issue, please don't create a pull request (they are public), instead send a patch to openssl-secur...@openssl.org. You can create an appropriate patch file by doing something like this: $ git format-patch --stdout > your.patch On 24 April

Re: How to help OpenSSL

On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote: > > 1. Triage RT (https://rt.openssl.org/). I think part of this means that you'll need to give some people access to it so they can actually modify the tickets. Kurt ___

Fwd: How to help OpenSSL

On Fri, Apr 25, 2014 at 10:03 AM, Jeff Trawick wrote: > On Thu, Apr 24, 2014 at 7:08 PM, Matt Caswell wrote: > >> On 24 April 2014 18:31, Ben Laurie wrote: >> > Note that this is just how to help me, not a consensus view from the >> > whole team, though I have no doubt much of it will be helpfu

How to help OpenSSL

Note that this is just how to help me, not a consensus view from the whole team, though I have no doubt much of it will be helpful to the team, too. 1. Triage RT (https://rt.openssl.org/). RT has been neglected for a long time. People could usefully go through it and identify: a) Tickets that ca

Re: How to help OpenSSL

On Fri, Apr 25, 2014 at 10:03 AM, Jeff Trawick wrote: > On Thu, Apr 24, 2014 at 7:08 PM, Matt Caswell wrote: > >> On 24 April 2014 18:31, Ben Laurie wrote: >> > Note that this is just how to help me, not a consensus view from the >> > whole team, though I have no doubt much of it will be helpfu

Re: How to help OpenSSL

On Thu, Apr 24, 2014 at 7:08 PM, Matt Caswell wrote: > On 24 April 2014 18:31, Ben Laurie wrote: > > Note that this is just how to help me, not a consensus view from the > > whole team, though I have no doubt much of it will be helpful to the > > team, too. > > > > 1. Triage RT (https://rt.opens

Re: How to help OpenSSL

On 25 April 2014 00:56, Quanah Gibson-Mount wrote: > > > --On April 25, 2014 at 12:08:08 AM +0100 Matt Caswell > wrote: > >> 2) Any new RT entries coming in should get the very highest priority. >> We can only start to make progress if the problem doesn't continue to >> grow. > > > This may induc

Re: How to help OpenSSL

On 25 April 2014 01:58, Daniel Reynolds wrote: > I am not totally sure how many people would be working on this project, but > is seems to me like it would make sense to split up into 3 groups. > I would be concerned about spreading ourselves too thinly. I hope that my amendment to the process I

Re: How to help OpenSSL

On 25 April 2014 01:14, Viktor Dukhovni wrote: > On Thu, Apr 24, 2014 at 04:56:09PM -0700, Quanah Gibson-Mount wrote: > >> >> The problem with this approach are significant requests that have languished >> for years. One such example would be >>

Re: How to help OpenSSL

I am not totally sure how many people would be working on this project, but is seems to me like it would make sense to split up into 3 groups. One would do what Viktor suggested, and hunt down patches added in major OS platforms. Another would do what Matt suggested, and simply go from the newes

Re: How to help OpenSSL

On Thu, Apr 24, 2014 at 04:56:09PM -0700, Quanah Gibson-Mount wrote: > > The problem with this approach are significant requests that have languished > for years. One such example would be > , which is 8 years old > now. The best place to get t

Re: How to help OpenSSL

--On April 25, 2014 at 12:08:08 AM +0100 Matt Caswell wrote: I would suggest the following process to do as Ben has requested: 1) We start looking at the newest entries in RT first and work backwards in time. This is on the basis that the newest bugs are likely to still be present and most r

Re: How to help OpenSSL

That seems completely reasonable to me. On Thu, Apr 24, 2014 at 7:08 PM, Matt Caswell wrote: > On 24 April 2014 18:31, Ben Laurie wrote: > > Note that this is just how to help me, not a consensus view from the > > whole team, though I have no doubt much of it will be helpful to the > > team, t

Re: How to help OpenSSL

On 24 April 2014 18:31, Ben Laurie wrote: > Note that this is just how to help me, not a consensus view from the > whole team, though I have no doubt much of it will be helpful to the > team, too. > > 1. Triage RT (https://rt.openssl.org/). > > RT has been neglected for a long time. People could u

Re: How to help OpenSSL

Hi Ben, all, In the wake of the OpenSSL publicity (and controversy) I today signed up to the mailing lists to find out whether and what I could do to help. I had a look at http://rt.openssl.org/NoAuth/Buglist.html and got the impression it indeed is out of date to the point of absurdity. But th

Re: How to help OpenSSL

On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote: > Note that this is just how to help me, not a consensus view from the > whole team, though I have no doubt much of it will be helpful to the > team, too. > > 1. Triage RT (https://rt.openssl.org/). > > RT has been neglected for a long t

Re: How to help OpenSSL

On Thu, Apr 24, 2014 at 1:31 PM, Ben Laurie wrote: > 6. Write new tests > > Our test suite sucks. More tests is better. > Shall I send a pull request for this: https://github.com/mbland/openssl/commit/a7a9e18b550edf059dfd54683ac1f45170ff9fb2 Mike

How to help OpenSSL

Note that this is just how to help me, not a consensus view from the whole team, though I have no doubt much of it will be helpful to the team, too. 1. Triage RT (https://rt.openssl.org/). RT has been neglected for a long time. People could usefully go through it and identify: a) Tickets that ca