[openssl-project] Fwd: [openssl-commits] FAILED build of OpenSSL branch OpenSSL_1_1_0-stable with options -d --strict-warnings no-dgram

[Richard Levitte]

In message <4a502429-f83b-61e7-afb8-620ae683e80e at openssl.org> on Thu, 18 Jan 2018 14:34:00 +0000, Matt Caswell <matt at openssl.org> said:

matt> 
matt> 
matt> On 18/01/18 14:31, Richard Levitte wrote:
matt> > In message <a9e93af5-83c5-7d3a-92fd-117ec83ac317 at openssl.org> on Thu, 18 Jan 2018 13:57:12 +0000, Matt Caswell <matt at openssl.org> said:
matt> > 
matt> > matt> 
matt> > matt> 
matt> > matt> On 18/01/18 13:56, Richard Levitte wrote:
matt> > matt> > In message <684f6ef0-f626-72fe-46de-a304ca1f858f at openssl.org> on Thu, 18 Jan 2018 13:48:58 +0000, Matt Caswell <matt at openssl.org> said:
matt> > matt> > 
matt> > matt> > matt> On 18/01/18 13:40, Richard Levitte wrote:
matt> > matt> > matt> > In the mean time, I'm turning off run-checker, as these reports are
matt> > matt> > matt> > disruptive and not useful at all.
matt> > matt> > matt> 
matt> > matt> > matt> Why not just switch off the 1.1.0 run-checker for now?
matt> > matt> > 
matt> > matt> > Good point.  Done and disabled in crontab
matt> > matt> > 
matt> > matt> 
matt> > matt> How about we change the port numbers in 1.1.0!?
matt> > 
matt> > I'd say it's better to change them in master, then...
matt> > 
matt> > So does this mean we change the TLSProxy ports every minor release
matt> > then? ;-)
matt> > 
matt> 
matt> Yes...master would be better. Even nicer would be a way to configure it
matt> from the command line. :-)
matt> 
matt> make PROXYPORTS=12345 test

There are two ports to define, the s_server accept port as well.

But good idea, and all that's needed is a change in Proxy.pm, as far as I know.

-- 
Richard Levitte         levitte at openssl.org
OpenSSL Project         http://www.openssl.org/~levitte/