From john.ackerley at oracle.com Tue Jun 8 15:39:44 2021 From: john.ackerley at oracle.com (John Ackerley) Date: Tue, 8 Jun 2021 11:39:44 -0400 Subject: [buildbot-admin] Fwd: FW: [External] : Re: Oracle Build Bot Workers In-Reply-To: <3ff403b0-fc21-cd9b-0dae-2fb24df55d0c@oracle.com> References: <3ff403b0-fc21-cd9b-0dae-2fb24df55d0c@oracle.com> Message-ID: Hi Chris, Jan, Do you have the master buildbot credentials for the ILOM buildbot worker? Thanks, -John > On 5/27/2021 12:15 PM, Grace Hopkins wrote: >> Hello Richard, >> I am setting up the Oracle X5 Buildbot Worker for OpenSSL. I need the >> Buildbot Worker credentials (worker name and password) so I can run >> buildbot-worker create-worker. Can you help me with this? If you are >> not the correct person to ask about the Buildbot Worker credentials, >> can you recommend someone else? >> >> Thank you, >> Grace Hopkins >> >> >> -------- Forwarded Message -------- >> Subject: FW: [External] : Re: [buildbot-admin] Oracle Build Bot Workers >> Date: Thu, 27 May 2021 10:21:50 -0400 >> From: Chris Brych >> To: Grace Hopkins , John Ackerley >> , Tom Dwyer >> >> >> >> FYI.? I think you need these certificates on the machine to run build >> bot. >> >> *From:* Chris Brych >> *Sent:* May 6, 2021 11:29 AM >> *To:* Ales Cernosek ; Steve McKinty >> ; John Ackerley ; >> Tom Dwyer ; Jennifer Brady >> >> *Subject:* FW: [External] : Re: [buildbot-admin] Oracle Build Bot Workers >> >> HI Ales, >> >> I received certificates from OpenSSL needed for use with Build bot.? >> I?ve attached them. >> >> Cheers, >> >> Chris >> >> -----Original Message----- >> From: Richard Levitte [mailto:levitte at openssl.org >> ] >> Sent: May 4, 2021 3:20 AM >> To: Chris Brych > >> Cc: buildbot-admin at openssl.org ; >> Shane Lontis > >; Jennifer Brady >> > >> Subject: [External] : Re: [buildbot-admin] Oracle Build Bot Workers >> >> An attachment in the email has been found to contain executable code >> and has been removed. >> >> File removed : isrg-root-x1.pem, diff,pem >> >> ---------------------------------------------------------------------- >> >> I have set up the solaris worker, the other two will need a >> conversation, which I'm taking separately. >> >> Thank you for offering workers to us! >> >> To be able to set up your worker, you must use version 3.0 or >> higher.? Older version do not support TLS-protected connections. >> >> Please see these instructions for installing the buildbot worker >> >> software: >> >> https://urldefense.com/v3/__http://docs.buildbot.net/latest/manual/installation/worker.html__;!!GqivPVa7Brio!LJqMxflBlaYCVWIutYLFLeDGtfGkNQRcUvx2kKGZjq9oTHcw2EwDMkfO9rXthZkesg$ >> >> >> >> When buildbot has been installed on the platform where the buildbot >> worker is to be run, this is how a worker is created: >> >> ??? $ buildbot-worker create-worker --use-tls BASEDIR \ >> >> ??????? buildbot.openssl.org:9989 Oracle-Solaris-Sparc-M8 '> >> where BASEDIR is determined by you. See further down for a few notes >> on TLS. >> >> To run a buildbot worker, you do this: >> >> ??? $ buildbot-worker start BASEDIR >> >> Apart from the software needed to run a buildbot worker, and the >> utilities that are the normal part of the operating system, you also >> need to ensure that the following components are available: >> >> -?? toolchains, i.e. C compiler, linker, make.? If you have specified >> >> ??? toolchains in the worker request form, you need to ensure that all >> >> ??? of them are installed. >> >> -?? git >> >> Regarding TLS, it may be that the buildbot worker platform doesn't >> have the appropriate certification verification roots set up.? In >> that case, you may need to apply the attached buildbot.tac patch, and >> store the attached PEM files in a directory of your choice.? Finish >> up by find the string '/PATH/TO/ssl-roots-dir' and replace its >> contents with the path of directory where you stored the PEM files. >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.brych at oracle.com Tue Jun 8 19:56:41 2021 From: chris.brych at oracle.com (Chris Brych) Date: Tue, 8 Jun 2021 19:56:41 +0000 Subject: [buildbot-admin] FW: Oracle Build Bot Workers In-Reply-To: References: Message-ID: Hi Matt Richard Pauli, I had sent some questions about our ILOM build bot workers a while ago and never did get a response to our questions. Can you take a minute and provide some answers to us as it will help us in understanding how to build buildbot for our Linux platform and port to ARM? Thanks. Cheers, Chris From: Chris Brych Sent: April 26, 2021 4:32 PM To: buildbot-admin at openssl.org Cc: Jennifer Brady ; Shane Lontis Subject: Oracle Build Bot Workers Hi Richard and Tim, Attached you will find some build bot configuration details as best we know. Oracle teams have been trying to ramp up and learn a little about build bot so be patient if we are missing some details. 1. Because ILOM is an embedded device that runs on ARM, the team builds on an X86 machine and then tests within its ARM platform. Does this mean that they will require 2 build bot workers? ie one to build and one to test? We assume the answer is yes. 2. It would be very convenient for Oracle if they will allow our arm worker to run in a qemu VM rather than real arm hardware. Is this possible? 3. Although ILOM runs oracle linux, the "command line utilities [that] can be expected" are severely limited (and most of those are busybox, not OL native--that means they work differently and/or have limited functionality). Can you elaborate on which command line utilities that are required? 4. "Necessary environment variables". We set dozens of them for ILOM builds. I don't know which (if any) are required for building OpenSSL standalone. Are there any environment variables that are necessary for building OpenSSL 3.0? Thanks. Cheers, Chris [Oracle] Chris Brych | Senior Principal Security Analyst Oracle Security Evaluations - Global Product Security Ottawa, Ontario | Canada +1-905-267-9352 (O) | +1-613-867-1241 (M) [Green Oracle] Oracle is committed to developing practices and products that help protect the environment -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 1296 bytes Desc: image005.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 866 bytes Desc: image006.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ILOM-Build-worker-request-form.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ILOM-Test-worker-request-form.txt URL: From tjh at openssl.org Wed Jun 9 10:19:35 2021 From: tjh at openssl.org (Tim Hudson) Date: Wed, 9 Jun 2021 20:19:35 +1000 Subject: [buildbot-admin] FW: Oracle Build Bot Workers In-Reply-To: References: Message-ID: As discussed previously (where these items were covered off) you need to get an operational environment together with a worker that allows us to build and run items. In a cross-compilation environment that means you need to figure out how 'make test' will work - and it is up to you to determine that strategy - if that means automating transfer of programs or remote shell access or whatever set of steps are required in your environment to make this happen. We don't care about the implementation details at all in terms of how you make it work. We do need to be able to compile programs and have them run and be able to get the output. If you want to risk operating this in an emulation of your environment, then that is up to you - but if that doesn't work identically to the real environment and issues arise then you run the risk of us dropping the platform out of the testing. We will not hesitate to drop out any platform that causes issues where the prework hasn't been performed or where it may impact other platforms. You should be fully aware that the CVMP do not allow use of CPU emulation environments as representative of a testing platform. I expect we will need to have some level of adjustment to run remote tests where we have a launcher program that does that work - however first you need to figure out how to actually make that work - which means how to go from a linked executable to something running on the host where we capture its output and where command line arguments are handled (as a lot of our testing is precisely that - using command line arguments to control exercising a variety of options). The 'ask' always was that make test operates correctly for all the fips sponsor platforms and the responsibility for meeting that condition resides with the fips sponsors. That requirement has not changed and has been known about since the beginning of this effort. For setting up environment variables for builds - with a buildbot worker you can do that before you fire up the worker or load in the required settings in python code in the buildbot.tac file that is effectively the 'main' of the worker process. Tim. On Wed, Jun 9, 2021 at 7:19 PM Dr Paul Dale wrote: > > FYI > > -------- Forwarded Message -------- > Subject: FW: Oracle Build Bot Workers > Date: Tue, 8 Jun 2021 19:56:41 +0000 > From: Chris Brych > To: buildbot-admin at openssl.org > > CC: Shane Lontis , > John Ackerley , Matt > Caswell , Richard Levitte > , pauli at openssl.org > > > Hi Matt Richard Pauli, > > > > I had sent some questions about our ILOM build bot workers a while ago and > never did get a response to our questions. Can you take a minute and > provide some answers to us as it will help us in understanding how to build > buildbot for our Linux platform and port to ARM? Thanks. > > > > Cheers, > > > > Chris > > > > *From:* Chris Brych > *Sent:* April 26, 2021 4:32 PM > *To:* buildbot-admin at openssl.org > *Cc:* Jennifer Brady > ; Shane Lontis > > *Subject:* Oracle Build Bot Workers > > > > Hi Richard and Tim, > > > > Attached you will find some build bot configuration details as best we > know. Oracle teams have been trying to ramp up and learn a little about > build bot so be patient if we are missing some details. > > > > 1. Because ILOM is an embedded device that runs on ARM, the team > builds on an X86 machine and then tests within its ARM platform. Does this > mean that they will require 2 build bot workers? ie one to build and one to > test? We assume the answer is yes. > > 2. It would be very convenient for Oracle if they will allow our arm > worker to run in a qemu VM rather than real arm hardware. Is this possible? > > 3. Although ILOM runs oracle linux, the "command line utilities [that] > can be expected" are severely limited (and most of those are busybox, not > OL native--that means they work differently and/or have limited > functionality). Can you elaborate on which command line utilities that are > required? > > 4. "Necessary environment variables". We set dozens of them for ILOM > builds. I don't know which (if any) are required for building OpenSSL > standalone. Are there any environment variables that are necessary for > building OpenSSL 3.0? > > > > Thanks. > > > > Cheers, > > > > Chris > > > > [image: Oracle] > Chris Brych | Senior Principal Security Analyst > Oracle Security Evaluations - Global Product Security > Ottawa, Ontario | Canada > > +1-905-267-9352 (O) | +1-613-867-1241 (M) > > [image: Green Oracle] > > Oracle is committed to developing practices and products that help protect > the environment > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 1296 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 866 bytes Desc: not available URL: From chris.brych at oracle.com Thu Jun 10 16:11:14 2021 From: chris.brych at oracle.com (Chris Brych) Date: Thu, 10 Jun 2021 16:11:14 +0000 Subject: [buildbot-admin] Oracle Buildbot Build Worker Credentials for ILOM Message-ID: Hello, Can you provide details for accessing the buildbot master for an ILOM builder worker? We believe we are in a place now where we can test the builder functionality of build bot and would like credentials for accessing the build bot master. Thanks. Cheers, Chris From: Chris Brych Sent: June 8, 2021 3:34 PM To: Richard Levitte ; Matt Caswell Cc: Shane Lontis Subject: RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build Bot Workers Hi, I should have mentioned that we will probably need 2 workers configured for now but that could change. Can you send us a builder credentials and also a tester login credentials and details as to how to log into these? Cheers, Chris From: Chris Brych Sent: June 8, 2021 2:58 PM To: Richard Levitte >; Matt Caswell > Cc: Shane Lontis > Subject: RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build Bot Workers Hi Richard and Matt, The ILOM team are now ready to connect to buildbot master. Can you provide the details on how to do this? Thanks. Cheers, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at openssl.org Thu Jun 10 16:16:05 2021 From: matt at openssl.org (Matt Caswell) Date: Thu, 10 Jun 2021 17:16:05 +0100 Subject: [buildbot-admin] Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: References: Message-ID: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> Hi Chris Did you fill in the worker request form (attachhed) for the ILOM platform? If so can you resend? If not can you fill it in? Thanks Matt On 10/06/2021 17:11, Chris Brych wrote: > Hello, > > Can you provide details for accessing the buildbot master for an ILOM > builder worker?? We believe we are in a place now where we can test the > builder functionality of build bot and would like credentials for > accessing the build bot master.? Thanks. > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 3:34 PM > *To:* Richard Levitte ; Matt Caswell > *Cc:* Shane Lontis > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi, > > I should have mentioned that we will probably need 2 workers configured > for now but that could change.? Can you send us a builder credentials > and also a tester login credentials and details as to how to log into these? > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 2:58 PM > *To:* Richard Levitte >; Matt Caswell > > *Cc:* Shane Lontis > > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi Richard and Matt, > > The ILOM team are now ready to connect to buildbot master.? Can you > provide the details on how to do this?? Thanks. > > Cheers, > > Chris > > > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin > -------------- next part -------------- Details we need or want from you ================================ * Worker tag [OPTIONAL]: * Worker platform type [MANDATORY]: (accepted values: 'unix', 'windows') * Worker platform identity [OPTIONAL]: (examples: 'ubuntu', 'ios', 'android', 'win10') * Worker platform architecture [OPTIONAL]: (examples: 'x86', 'x86_64', 'arm', 'ppc') * Worker Purpose [MANDATORY, more than one choice allowed]: (accepted values: 'build+test', 'build', 'test') * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') * Necessary environment variables [OPTIONAL]: * Necessary configuration target name [OPTIONAL]: * Necessary configuration options [OPTIONAL]: * Max number of concurrent builds [OPTIONAL]: What can be expected next ========================= For each form that we receive, we will assign you a full worker name and a passphrase, and respond to you by email informing you of this and additional information, such as basic instructions for creating and starting the worker, what the buildbot status page is, and more. About the details we ask from you ================================= * Worker tag: Short mnemonic. This will be included in the full name of the worker. If you're not giving us one, we may make one for you. * Worker platform type: this is MANDATORY, because the buildbot master needs that to determine what command line shell is used (/bin/sh is assumed for 'unix', cmd.exe is assumed for 'windows') and what command line utilities can be expected. * Worker platform identity: a finer grained identity token, like 'ubuntu', 'ios', ... this is used to segregates between builds on these different platforms. If this isn't present, the platform type ('unix' or 'windows') are used for this segregation. * Worker platform architecture: just like the worker platform identity, this is used to segregate between different builds where it may be important. This is only necessary if OpenSSL has corresponding config targets. * Worker purpose: What this worker should be used for. This can be used to have different workers work together with different tasks, for various reasons. The accepted values are: build+test This denotes a "do everything" worker, i.e. it will get to do 'Configure', 'make' and 'make test'. build This denotes a worker that will only build, but not test. In other words, only 'Configure' and 'make' will be performed. If there is any matching worker that's denoted 'test', the programs and libraries created by this 'build' worker will be shipped to the worker that is assigned to perform the test. test This denotes a worker that will only test, but not build. In other words, only 'make test' will be performed. The separate 'build' and 'test' purposes can be used to have one worker cross compile for some target architecture, and shipping the result to a worker that is of that architecture and that will perform the tests. The separate 'build' and 'test' purposes can be also be used to separate workers that are quick builders from others that don't build as quickly, allowing quicker developer turnaround when something needs to be fixed. Matching 'build' and 'test' workers are found on the basis of the worker tag, the platform type or platform identity and the platform architecture, by forming strings as follows from the worker information, and simply comparing strings: "{worker-tag}-{platform-id}-{platform-arch}" "{worker-tag}-{platform-type}-{platform-arch}" If no matching 'test' workers are found, then only the build will be performed. NOTE: NOT CURRENTLY IMPLEMENTED! 'test' workers are currently not implemented, so those works will currently remain idle. However, we do work on making transfer of files work smoothly, so they may start to do actual work at some point in the near future. * Worked toolchains for building: This allows a worker to be used for multiple known building configurations, and is specified as a list of mnemonics. Multiple choices may be specified. If no choice is given, 'default' is assumed. The current available choices are: - 'default' This uses whatever happens to be considered default by OpenSSL's Configure script. On Unix, that's normally the default C compiler 'cc' and 'make'. On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. This toolchain choice expects all the compiling and linking tools to be set up correctly in the worker. $PATH or %PATH% and other environment variables must be set up correctly when the worker is started. - 'gcc' and 'clang' This uses specific compilers instead of the default 'cc', but works otherwise like 'default'. - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', 'vs2019e', 'vs2019p' These all cover different versions and editions of Microsoft Visual Studio C, as follows: - 'vs2017', 'vs2017c' Microsoft Visual Studio 2017, Community edition - 'vs2017e' Microsoft Visual Studio 2017, Enterprise edition - 'vs2017p Microsoft Visual Studio 2017, Professional edition - 'vs2019', 'vs2019c' Microsoft Visual Studio 2019, Community edition - 'vs2019e' Microsoft Visual Studio 2019, Enterprise edition - 'vs2019p Microsoft Visual Studio 2019, Professional edition OpenSSL's buildbot setup adds extra support for these choices, by calling the appropriate Visual Studio setup script for each of them when building, assuming that the setup script is installed in default places. More toolchain choices may be added over time, as the need arises. * Necessary environment variables: Environment variables that are necessary to build properly on the target platform. This should normally not be needed, but could be in some cases. An example is Android, where it's necessary to specify the Android root with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see NOTES-ANDROID.md in the OpenSSL 3.0 source) * Necessary configuration target name: Explicit configuration target name. This should normally not be needed, as OpenSSL's configuration script should be able to detect the target platform automatically. This is however not always possible, for example when cross compilation is needed, or when OpenSSL's configuration script doesn't know how to automatically detect the target platform. NOTE: The OpenSSL developers would appreciate if you could tell us how to automatically detect the configuration target for your platform, if OpenSSL's configuration script doesn't currently do that. * Necessary configuration options: Additional configuration options necessary to correctly build OpenSSL for the target platform. This should normally not be needed, but could be in some cases. An example is Android, where it's necessary to specify the desired Android API version number using the C macro __ANDROID_API__. * Max number of concurrent builds: A limitation for how many builds are allowed to happen concurrently on this worker. This is suitable when too many resources would otherwise be used. By default, there is no limit. From chris.brych at oracle.com Thu Jun 10 16:21:14 2021 From: chris.brych at oracle.com (Chris Brych) Date: Thu, 10 Jun 2021 16:21:14 +0000 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> Message-ID: Hi Matt, We did fill out the form but we may need to modify it as we were assuming that we would be building on Oracle Linux but that may change now to Solaris. I'm not sure it matters but let me check and get back to you. I've attached what we previously sent you. Cheers, Chris -----Original Message----- From: Matt Caswell [mailto:matt at openssl.org] Sent: June 10, 2021 12:16 PM To: Chris Brych ; buildbot-admin at openssl.org Cc: Grace Hopkins ; Tom Dwyer ; John Ackerley Subject: [External] : Re: [buildbot-admin] Oracle Buildbot Build Worker Credentials for ILOM Hi Chris Did you fill in the worker request form (attachhed) for the ILOM platform? If so can you resend? If not can you fill it in? Thanks Matt On 10/06/2021 17:11, Chris Brych wrote: > Hello, > > Can you provide details for accessing the buildbot master for an ILOM > builder worker?? We believe we are in a place now where we can test > the builder functionality of build bot and would like credentials for > accessing the build bot master.? Thanks. > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 3:34 PM > *To:* Richard Levitte ; Matt Caswell > > *Cc:* Shane Lontis > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi, > > I should have mentioned that we will probably need 2 workers > configured for now but that could change.? Can you send us a builder > credentials and also a tester login credentials and details as to how to log into these? > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 2:58 PM > *To:* Richard Levitte >; Matt Caswell > > *Cc:* Shane Lontis > > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi Richard and Matt, > > The ILOM team are now ready to connect to buildbot master.? Can you > provide the details on how to do this?? Thanks. > > Cheers, > > Chris > > > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://urldefense.com/v3/__https://mta.openssl.org/mailman/listinfo/b > uildbot-admin__;!!GqivPVa7Brio!IMCuTt0ZwwvAM989YhG_b1KJc5bfMRWmUoH_43v > eKGGzhF4rPeSrhllDwSdy0tOuiQ$ > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ILOM-Build-worker-request-form.txt URL: From chris.brych at oracle.com Thu Jun 10 17:28:41 2021 From: chris.brych at oracle.com (Chris Brych) Date: Thu, 10 Jun 2021 17:28:41 +0000 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> Message-ID: Hi Matt, The information I sent you in the form is correct. We are building on Oracle Linux. Cheers, Chris -----Original Message----- From: Chris Brych Sent: June 10, 2021 12:21 PM To: Matt Caswell ; buildbot-admin at openssl.org Cc: Grace Hopkins ; Tom Dwyer ; John Ackerley Subject: RE: [External] : Re: [buildbot-admin] Oracle Buildbot Build Worker Credentials for ILOM Hi Matt, We did fill out the form but we may need to modify it as we were assuming that we would be building on Oracle Linux but that may change now to Solaris. I'm not sure it matters but let me check and get back to you. I've attached what we previously sent you. Cheers, Chris -----Original Message----- From: Matt Caswell [mailto:matt at openssl.org] Sent: June 10, 2021 12:16 PM To: Chris Brych ; buildbot-admin at openssl.org Cc: Grace Hopkins ; Tom Dwyer ; John Ackerley Subject: [External] : Re: [buildbot-admin] Oracle Buildbot Build Worker Credentials for ILOM Hi Chris Did you fill in the worker request form (attachhed) for the ILOM platform? If so can you resend? If not can you fill it in? Thanks Matt On 10/06/2021 17:11, Chris Brych wrote: > Hello, > > Can you provide details for accessing the buildbot master for an ILOM > builder worker?? We believe we are in a place now where we can test > the builder functionality of build bot and would like credentials for > accessing the build bot master.? Thanks. > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 3:34 PM > *To:* Richard Levitte ; Matt Caswell > > *Cc:* Shane Lontis > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi, > > I should have mentioned that we will probably need 2 workers > configured for now but that could change.? Can you send us a builder > credentials and also a tester login credentials and details as to how to log into these? > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 2:58 PM > *To:* Richard Levitte >; Matt Caswell > > *Cc:* Shane Lontis > > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi Richard and Matt, > > The ILOM team are now ready to connect to buildbot master.? Can you > provide the details on how to do this?? Thanks. > > Cheers, > > Chris > > > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://urldefense.com/v3/__https://mta.openssl.org/mailman/listinfo/b > uildbot-admin__;!!GqivPVa7Brio!IMCuTt0ZwwvAM989YhG_b1KJc5bfMRWmUoH_43v > eKGGzhF4rPeSrhllDwSdy0tOuiQ$ > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ILOM-Build-worker-request-form.txt URL: From chris.brych at oracle.com Fri Jun 11 13:07:52 2021 From: chris.brych at oracle.com (Chris Brych) Date: Fri, 11 Jun 2021 13:07:52 +0000 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> Message-ID: Hi Matt, See Attached. We only need credentials for a builder worker at this time. Thanks. Cheers, Chris -----Original Message----- From: Matt Caswell [mailto:matt at openssl.org] Sent: June 10, 2021 12:16 PM To: Chris Brych ; buildbot-admin at openssl.org Cc: Grace Hopkins ; Tom Dwyer ; John Ackerley Subject: [External] : Re: [buildbot-admin] Oracle Buildbot Build Worker Credentials for ILOM Hi Chris Did you fill in the worker request form (attachhed) for the ILOM platform? If so can you resend? If not can you fill it in? Thanks Matt On 10/06/2021 17:11, Chris Brych wrote: > Hello, > > Can you provide details for accessing the buildbot master for an ILOM > builder worker?? We believe we are in a place now where we can test > the builder functionality of build bot and would like credentials for > accessing the build bot master.? Thanks. > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 3:34 PM > *To:* Richard Levitte ; Matt Caswell > > *Cc:* Shane Lontis > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi, > > I should have mentioned that we will probably need 2 workers > configured for now but that could change.? Can you send us a builder > credentials and also a tester login credentials and details as to how to log into these? > > Cheers, > > Chris > > *From:* Chris Brych > *Sent:* June 8, 2021 2:58 PM > *To:* Richard Levitte >; Matt Caswell > > *Cc:* Shane Lontis > > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > Bot Workers > > Hi Richard and Matt, > > The ILOM team are now ready to connect to buildbot master.? Can you > provide the details on how to do this?? Thanks. > > Cheers, > > Chris > > > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://urldefense.com/v3/__https://mta.openssl.org/mailman/listinfo/b > uildbot-admin__;!!GqivPVa7Brio!IMCuTt0ZwwvAM989YhG_b1KJc5bfMRWmUoH_43v > eKGGzhF4rPeSrhllDwSdy0tOuiQ$ > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ILOM-Build-worker-request-form.txt URL: From levitte at openssl.org Fri Jun 11 14:17:13 2021 From: levitte at openssl.org (Richard Levitte) Date: Fri, 11 Jun 2021 16:17:13 +0200 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> Message-ID: <87fsxoa3km.wl-levitte@openssl.org> Hi, Thank you for offering workers to us! To be able to set up your worker, you must use version 2.6.0 or higher. Older version do not support TLS-protected connections. Please see these instructions for installing the buildbot worker software: http://docs.buildbot.net/latest/manual/installation/worker.html When buildbot has been installed on the platform where the buildbot worker is to be run, this is how a worker is created: $ buildbot-worker create-worker --use-tls BASEDIR \ buildbot.openssl.org:9989 Oracle-ILOM 'Cu;Dryt8' where BASEDIR is determined by you. See further down for a few notes on TLS. To run a buildbot worker, you do this: $ buildbot-worker start BASEDIR Apart from the software needed to run a buildbot worker, and the utilities that are the normal part of the operating system, you also need to ensure that the following components are available: - toolchains, i.e. C compiler, linker, make. If you have specified toolchains in the worker request form, you need to ensure that all of them are installed. - git Regarding TLS, it may be that the buildbot worker platform doesn't have the appropriate certification verification roots set up. In that case, you may need to apply the attached buildbot.tac patch, and store the attached PEM files in a directory of your choice. Finish up by find the string '/PATH/TO/ssl-roots-dir' and replace its contents with the path of directory where you stored the PEM files. -------------- next part -------------- A non-text attachment was scrubbed... Name: buildbot.tac.diff Type: application/octet-stream Size: 938 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: isrg-root-x1.pem Type: application/octet-stream Size: 1939 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: lets-encrypt-r3.pem Type: application/octet-stream Size: 1826 bytes Desc: not available URL: -------------- next part -------------- Cheers, Richard On Fri, 11 Jun 2021 15:07:52 +0200, Chris Brych wrote: > > Hi Matt, > > See Attached. We only need credentials for a builder worker at this time. Thanks. > > Cheers, > > Chris > > -----Original Message----- > From: Matt Caswell [mailto:matt at openssl.org] > Sent: June 10, 2021 12:16 PM > To: Chris Brych ; buildbot-admin at openssl.org > Cc: Grace Hopkins ; Tom Dwyer ; John Ackerley > Subject: [External] : Re: [buildbot-admin] Oracle Buildbot Build Worker Credentials for ILOM > > Hi Chris > > Did you fill in the worker request form (attachhed) for the ILOM platform? If so can you resend? If not can you fill it in? > > Thanks > > Matt > > > > On 10/06/2021 17:11, Chris Brych wrote: > > Hello, > > > > Can you provide details for accessing the buildbot master for an ILOM > > builder worker?? We believe we are in a place now where we can test > > the builder functionality of build bot and would like credentials for > > accessing the build bot master.? Thanks. > > > > Cheers, > > > > Chris > > > > *From:* Chris Brych > > *Sent:* June 8, 2021 3:34 PM > > *To:* Richard Levitte ; Matt Caswell > > > > *Cc:* Shane Lontis > > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > > Bot Workers > > > > Hi, > > > > I should have mentioned that we will probably need 2 workers > > configured for now but that could change.? Can you send us a builder > > credentials and also a tester login credentials and details as to how to log into these? > > > > Cheers, > > > > Chris > > > > *From:* Chris Brych > > *Sent:* June 8, 2021 2:58 PM > > *To:* Richard Levitte > >; Matt Caswell > > > > *Cc:* Shane Lontis > > > > *Subject:* RE: Fwd: FW: [External] : Re: [buildbot-admin] Oracle Build > > Bot Workers > > > > Hi Richard and Matt, > > > > The ILOM team are now ready to connect to buildbot master.? Can you > > provide the details on how to do this?? Thanks. > > > > Cheers, > > > > Chris > > > > > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > https://urldefense.com/v3/__https://mta.openssl.org/mailman/listinfo/b > > uildbot-admin__;!!GqivPVa7Brio!IMCuTt0ZwwvAM989YhG_b1KJc5bfMRWmUoH_43v > > eKGGzhF4rPeSrhllDwSdy0tOuiQ$ > > > [2 ILOM-Build-worker-request-form.txt ] > Details we need or want from you > ================================ > > * Worker tag [OPTIONAL]: ILOM_build > > * Worker platform type [MANDATORY]: unix > > (accepted values: 'unix', 'windows') > > * Worker platform identity [OPTIONAL]: oracle linux > > (examples: 'ubuntu', 'ios', 'android', 'win10') > > * Worker platform architecture [OPTIONAL]: x86_64 > > (examples: 'x86', 'x86_64', 'arm', 'ppc') > > * Worker Purpose [MANDATORY, more than one choice allowed]: build (x86_64) > > (accepted values: 'build+test', 'build', 'test') > > * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: gcc > > (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') > > * Necessary environment variables [OPTIONAL]: > > * Necessary configuration target name [OPTIONAL]: linux-generic32 > > * Necessary configuration options [OPTIONAL]: -DL_ENDIAN -DOPENSSL_NO_COMP shared --prefix=/usr --openssldir=/conf/openssl no-zlib no-comp > > * Max number of concurrent builds [OPTIONAL]: > > > What can be expected next > ========================= > > For each form that we receive, we will assign you a full worker name and a > passphrase, and respond to you by email informing you of this and additional > information, such as basic instructions for creating and starting the worker, > what the buildbot status page is, and more. > > > About the details we ask from you > ================================= > > * Worker tag: Short mnemonic. > This will be included in the full name of the worker. If you're not > giving us one, we may make one for you. > > * Worker platform type: this is MANDATORY, because the buildbot master > needs that to determine what command line shell is used (/bin/sh is > assumed for 'unix', cmd.exe is assumed for 'windows') and what command > line utilities can be expected. > > * Worker platform identity: a finer grained identity token, like 'ubuntu', > 'ios', ... this is used to segregates between builds on these different > platforms. If this isn't present, the platform type ('unix' or 'windows') > are used for this segregation. > > * Worker platform architecture: just like the worker platform identity, > this is used to segregate between different builds where it may be > important. This is only necessary if OpenSSL has corresponding config > targets. > > * Worker purpose: What this worker should be used for. This can be used > to have different workers work together with different tasks, for > various reasons. The accepted values are: > > build+test This denotes a "do everything" worker, i.e. it will > get to do 'Configure', 'make' and 'make test'. > > build This denotes a worker that will only build, but not > test. In other words, only 'Configure' and 'make' > will be performed. > If there is any matching worker that's denoted > 'test', the programs and libraries created by this > 'build' worker will be shipped to the worker that is > assigned to perform the test. > > test This denotes a worker that will only test, but not > build. In other words, only 'make test' will be > performed. > > The separate 'build' and 'test' purposes can be used to have one worker > cross compile for some target architecture, and shipping the result to a > worker that is of that architecture and that will perform the tests. > > The separate 'build' and 'test' purposes can be also be used to separate > workers that are quick builders from others that don't build as quickly, > allowing quicker developer turnaround when something needs to be fixed. > > Matching 'build' and 'test' workers are found on the basis of the worker > tag, the platform type or platform identity and the platform architecture, > by forming strings as follows from the worker information, and simply > comparing strings: > > "{worker-tag}-{platform-id}-{platform-arch}" > > "{worker-tag}-{platform-type}-{platform-arch}" > > If no matching 'test' workers are found, then only the build will be > performed. > > NOTE: NOT CURRENTLY IMPLEMENTED! > 'test' workers are currently not implemented, so those works will > currently remain idle. However, we do work on making transfer of files > work smoothly, so they may start to do actual work at some point in the > near future. > > * Worked toolchains for building: This allows a worker to be used > for multiple known building configurations, and is specified as a > list of mnemonics. Multiple choices may be specified. If no > choice is given, 'default' is assumed. > > The current available choices are: > > - 'default' > > This uses whatever happens to be considered default by > OpenSSL's Configure script. > On Unix, that's normally the default C compiler 'cc' and 'make'. > On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. > > This toolchain choice expects all the compiling and linking > tools to be set up correctly in the worker. $PATH or %PATH% > and other environment variables must be set up correctly when > the worker is started. > > - 'gcc' and 'clang' > > This uses specific compilers instead of the default 'cc', but > works otherwise like 'default'. > > - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', > 'vs2019e', 'vs2019p' > > These all cover different versions and editions of Microsoft > Visual Studio C, as follows: > > - 'vs2017', 'vs2017c' > > Microsoft Visual Studio 2017, Community edition > > - 'vs2017e' > > Microsoft Visual Studio 2017, Enterprise edition > > - 'vs2017p > > Microsoft Visual Studio 2017, Professional edition > > - 'vs2019', 'vs2019c' > > Microsoft Visual Studio 2019, Community edition > > - 'vs2019e' > > Microsoft Visual Studio 2019, Enterprise edition > > - 'vs2019p > > Microsoft Visual Studio 2019, Professional edition > > OpenSSL's buildbot setup adds extra support for these choices, > by calling the appropriate Visual Studio setup script for each > of them when building, assuming that the setup script is > installed in default places. > > More toolchain choices may be added over time, as the need arises. > > * Necessary environment variables: Environment variables that are > necessary to build properly on the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the Android root > with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see > NOTES-ANDROID.md in the OpenSSL 3.0 source) > > * Necessary configuration target name: Explicit configuration target name. > This should normally not be needed, as OpenSSL's configuration script > should be able to detect the target platform automatically. This is > however not always possible, for example when cross compilation is > needed, or when OpenSSL's configuration script doesn't know how to > automatically detect the target platform. > > NOTE: The OpenSSL developers would appreciate if you could tell us how > to automatically detect the configuration target for your platform, if > OpenSSL's configuration script doesn't currently do that. > > * Necessary configuration options: Additional configuration options > necessary to correctly build OpenSSL for the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the desired Android > API version number using the C macro __ANDROID_API__. > > * Max number of concurrent builds: A limitation for how many builds are > allowed to happen concurrently on this worker. This is suitable when > too many resources would otherwise be used. By default, there is no > limit. > [3 ] > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From chris.brych at oracle.com Fri Jun 11 14:19:45 2021 From: chris.brych at oracle.com (Chris Brych) Date: Fri, 11 Jun 2021 14:19:45 +0000 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: <87fsxoa3km.wl-levitte@openssl.org> References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> <87fsxoa3km.wl-levitte@openssl.org> Message-ID: Hi Richard, Our firewall stripped your attachments. Can you send them again zipped or encrypted with my GPG key? I sent you my key before. If you need it, let me know. Cheers, Chris -----Original Message----- From: Richard Levitte [mailto:levitte at openssl.org] Sent: June 11, 2021 10:17 AM To: Chris Brych Cc: Matt Caswell ; buildbot-admin at openssl.org; Grace Hopkins ; Tom Dwyer ; John Ackerley Subject: Re: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM An attachment in the email has been found to contain executable code and has been removed. File removed : isrg-root-x1.pem, diff,pem ---------------------------------------------------------------------- Hi, Thank you for offering workers to us! To be able to set up your worker, you must use version 2.6.0 or higher. Older version do not support TLS-protected connections. Please see these instructions for installing the buildbot worker software: https://urldefense.com/v3/__http://docs.buildbot.net/latest/manual/installation/worker.html__;!!GqivPVa7Brio!Lw1faZX0RDOK-pG_8utIgS3npoCr748v3t1oTqPbzxlt-GO8UbSUqN-6Od04kEvA9g$ When buildbot has been installed on the platform where the buildbot worker is to be run, this is how a worker is created: $ buildbot-worker create-worker --use-tls BASEDIR \ buildbot.openssl.org:9989 Oracle-ILOM 'Cu;Dryt8' where BASEDIR is determined by you. See further down for a few notes on TLS. To run a buildbot worker, you do this: $ buildbot-worker start BASEDIR Apart from the software needed to run a buildbot worker, and the utilities that are the normal part of the operating system, you also need to ensure that the following components are available: - toolchains, i.e. C compiler, linker, make. If you have specified toolchains in the worker request form, you need to ensure that all of them are installed. - git Regarding TLS, it may be that the buildbot worker platform doesn't have the appropriate certification verification roots set up. In that case, you may need to apply the attached buildbot.tac patch, and store the attached PEM files in a directory of your choice. Finish up by find the string '/PATH/TO/ssl-roots-dir' and replace its contents with the path of directory where you stored the PEM files. From matt at openssl.org Fri Jun 11 14:41:46 2021 From: matt at openssl.org (Matt Caswell) Date: Fri, 11 Jun 2021 15:41:46 +0100 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> <87fsxoa3km.wl-levitte@openssl.org> Message-ID: Hi Chris Here are the attachments as a zip. Matt On 11/06/2021 15:19, Chris Brych wrote: > Hi Richard, > > Our firewall stripped your attachments. Can you send them again zipped or encrypted with my GPG key? I sent you my key before. If you need it, let me know. > > Cheers, > > Chris > > -----Original Message----- > From: Richard Levitte [mailto:levitte at openssl.org] > Sent: June 11, 2021 10:17 AM > To: Chris Brych > Cc: Matt Caswell ; buildbot-admin at openssl.org; Grace Hopkins ; Tom Dwyer ; John Ackerley > Subject: Re: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM > > An attachment in the email has been found to contain executable code and has been removed. > > File removed : isrg-root-x1.pem, diff,pem > > ---------------------------------------------------------------------- > Hi, > > Thank you for offering workers to us! > > To be able to set up your worker, you must use version 2.6.0 or higher. Older version do not support TLS-protected connections. > > Please see these instructions for installing the buildbot worker > software: > > https://urldefense.com/v3/__http://docs.buildbot.net/latest/manual/installation/worker.html__;!!GqivPVa7Brio!Lw1faZX0RDOK-pG_8utIgS3npoCr748v3t1oTqPbzxlt-GO8UbSUqN-6Od04kEvA9g$ > > When buildbot has been installed on the platform where the buildbot worker is to be run, this is how a worker is created: > > $ buildbot-worker create-worker --use-tls BASEDIR \ > buildbot.openssl.org:9989 Oracle-ILOM 'Cu;Dryt8' > > where BASEDIR is determined by you. See further down for a few notes on TLS. > > To run a buildbot worker, you do this: > > $ buildbot-worker start BASEDIR > > Apart from the software needed to run a buildbot worker, and the utilities that are the normal part of the operating system, you also need to ensure that the following components are available: > > - toolchains, i.e. C compiler, linker, make. If you have specified > toolchains in the worker request form, you need to ensure that all > of them are installed. > > - git > > Regarding TLS, it may be that the buildbot worker platform doesn't have the appropriate certification verification roots set up. In that case, you may need to apply the attached buildbot.tac patch, and store the attached PEM files in a directory of your choice. Finish up by find the string '/PATH/TO/ssl-roots-dir' and replace its contents with the path of directory where you stored the PEM files. > -------------- next part -------------- A non-text attachment was scrubbed... Name: buildbot.zip Type: application/zip Size: 3807 bytes Desc: not available URL: From chris.brych at oracle.com Fri Jun 11 16:14:14 2021 From: chris.brych at oracle.com (Chris Brych) Date: Fri, 11 Jun 2021 16:14:14 +0000 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> <87fsxoa3km.wl-levitte@openssl.org> Message-ID: Hi Matt, Sorry but I still could not receive the files as our server stripped it. Can you gpg encrypt it? Below is my public key block. -----BEGIN PGP PUBLIC KEY BLOCK----- mQGNBFON1AABDACuXFw/dthDKz0kuTSLPADnouvnzabfjA/m8wLrVfLjOgl6LH57 fw+Cy4R5h6WY+IUD2qF4LMd2fVDB2WQBnDz73vcB5ynFQ69GkhWS8hhawe00nopn AS2uTydgBnesdgcuaGw6ZnPgP3ogCcaTOW65c0hu8xQh1GTfWXD27GTacul7fv0R Ta7sgTQt2JGcnJuK5WLCqYq5rKRCTE11yHp8NJ+byp37zfZ7lOTvOn3Va2UD1hiE QR5lQBgPAw9GDzSpUKBBFleOuzbGyJKtp9CC3hBc6lq8K4r6GSYQk58mFEMWMDNl HOMr7H6WSonWvWMgiCulfDbtcYUP6o7T/m7czZRyKY3NlqBxv3TMaRapmnRXw5uO Q/2iBGVXPNhJIEkG5BbcMNo6aga368YPQ8rWp3MdCNG2w6Sxi7pwrlI98WKgSMD+ AvRd/zfnUwKrlNapY6fsDF959PjbhrcTTVjtlpOghXAJLEH2H64qSXisAk0O7AWf lH/A5NKDlGWqaFMAEQEAAbQyQ2hyaXMgQnJ5Y2ggKEdQRyBLZXkgU2V0KSA8Y2hy aXMuYnJ5Y2hAb3JhY2xlLmNvbT6JAbkEEwECACMFAlON1AACGy8HCwkIBwMCAQYV CAIJCgsEFgIDAQIeAQIXgAAKCRB/DoGvuY3hI+3wC/9JVCnZJcijMvuJnUaNM2q9 p+octKK2aPlBorknn48JZdpetj/Ug8of4GFqNeaMMVsEv0W8dIjyZom5dCVPnVrT LaERzCQH+wp4LQpxLflPJ/eehVbs3cu3imaOOWetjcPbACl6JQOIfBvfVLWN9k8B 6VFL9CUKnt2rk7F/+TubjMApbhezAPW9nVHzem2ICGUn03R85JOvFvBhu0YnnoQo wB+ZaJJyLlw5NxovCdWF9dFrrpW1XAEYo4t2tIZ/L0GLy4u0GNtPeL2gxgcDo3fJ eikXktsiCiLi9DPIJFHd060XhADEQAqDqUsBSvYzfM+ImF3IM/mn1dnqqEK7Jyma hEORrGNOKpLw8+Kb8VEqhSziCJ1sNvgHHp7h4NXqmqKBAEYCWzJ4JQP3tGSULdWf qW/8n+ua3msJxVtrn1jrGzF4ryOy5IOv8AHBm3qsu3ldAilf8weSBGlgujZ9Jdnh GM1KHl7YJZyu9OyZMAeP/nVBmvsViD2bnQtHydW91Fg= =qEmn -----END PGP PUBLIC KEY BLOCK----- Cheers, Chris -----Original Message----- From: Matt Caswell [mailto:matt at openssl.org] Sent: June 11, 2021 10:42 AM To: Chris Brych ; Richard Levitte Cc: buildbot-admin at openssl.org; Grace Hopkins ; Tom Dwyer ; John Ackerley Subject: Re: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM An attachment in the email has been found to contain executable code and has been removed. File removed : buildbot.zip, zip,pem ---------------------------------------------------------------------- Hi Chris Here are the attachments as a zip. Matt On 11/06/2021 15:19, Chris Brych wrote: > Hi Richard, > > Our firewall stripped your attachments. Can you send them again zipped or encrypted with my GPG key? I sent you my key before. If you need it, let me know. > > Cheers, > > Chris > > -----Original Message----- > From: Richard Levitte [mailto:levitte at openssl.org] > Sent: June 11, 2021 10:17 AM > To: Chris Brych > Cc: Matt Caswell ; buildbot-admin at openssl.org; Grace Hopkins ; Tom Dwyer ; John Ackerley > Subject: Re: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM > > An attachment in the email has been found to contain executable code and has been removed. > > File removed : isrg-root-x1.pem, diff,pem > > ---------------------------------------------------------------------- > Hi, > > Thank you for offering workers to us! > > To be able to set up your worker, you must use version 2.6.0 or higher. Older version do not support TLS-protected connections. > > Please see these instructions for installing the buildbot worker > software: > > https://urldefense.com/v3/__http://docs.buildbot.net/latest/manual/installation/worker.html__;!!GqivPVa7Brio!Lw1faZX0RDOK-pG_8utIgS3npoCr748v3t1oTqPbzxlt-GO8UbSUqN-6Od04kEvA9g$ > > When buildbot has been installed on the platform where the buildbot worker is to be run, this is how a worker is created: > > $ buildbot-worker create-worker --use-tls BASEDIR \ > buildbot.openssl.org:9989 Oracle-ILOM 'Cu;Dryt8' > > where BASEDIR is determined by you. See further down for a few notes on TLS. > > To run a buildbot worker, you do this: > > $ buildbot-worker start BASEDIR > > Apart from the software needed to run a buildbot worker, and the utilities that are the normal part of the operating system, you also need to ensure that the following components are available: > > - toolchains, i.e. C compiler, linker, make. If you have specified > toolchains in the worker request form, you need to ensure that all > of them are installed. > > - git > > Regarding TLS, it may be that the buildbot worker platform doesn't have the appropriate certification verification roots set up. In that case, you may need to apply the attached buildbot.tac patch, and store the attached PEM files in a directory of your choice. Finish up by find the string '/PATH/TO/ssl-roots-dir' and replace its contents with the path of directory where you stored the PEM files. > -------------- next part -------------- A non-text attachment was scrubbed... Name: openpgp-digital-signature.asc Type: application/pgp-signature Size: 660 bytes Desc: not available URL: From chris.brych at oracle.com Fri Jun 11 18:42:43 2021 From: chris.brych at oracle.com (Chris Brych) Date: Fri, 11 Jun 2021 18:42:43 +0000 Subject: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM In-Reply-To: References: <58028df0-3ed0-09d9-8fe9-a08054c6e178@openssl.org> <87fsxoa3km.wl-levitte@openssl.org> Message-ID: I got the file, thanks. Cheers, Chris -----Original Message----- From: Matt Caswell [mailto:matt at openssl.org] Sent: June 11, 2021 10:42 AM To: Chris Brych ; Richard Levitte Cc: buildbot-admin at openssl.org; Grace Hopkins ; Tom Dwyer ; John Ackerley Subject: Re: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM An attachment in the email has been found to contain executable code and has been removed. File removed : buildbot.zip, zip,pem ---------------------------------------------------------------------- Hi Chris Here are the attachments as a zip. Matt On 11/06/2021 15:19, Chris Brych wrote: > Hi Richard, > > Our firewall stripped your attachments. Can you send them again zipped or encrypted with my GPG key? I sent you my key before. If you need it, let me know. > > Cheers, > > Chris > > -----Original Message----- > From: Richard Levitte [mailto:levitte at openssl.org] > Sent: June 11, 2021 10:17 AM > To: Chris Brych > Cc: Matt Caswell ; buildbot-admin at openssl.org; Grace Hopkins ; Tom Dwyer ; John Ackerley > Subject: Re: [buildbot-admin] [External] : Re: Oracle Buildbot Build Worker Credentials for ILOM > > An attachment in the email has been found to contain executable code and has been removed. > > File removed : isrg-root-x1.pem, diff,pem > > ---------------------------------------------------------------------- > Hi, > > Thank you for offering workers to us! > > To be able to set up your worker, you must use version 2.6.0 or higher. Older version do not support TLS-protected connections. > > Please see these instructions for installing the buildbot worker > software: > > https://urldefense.com/v3/__http://docs.buildbot.net/latest/manual/installation/worker.html__;!!GqivPVa7Brio!Lw1faZX0RDOK-pG_8utIgS3npoCr748v3t1oTqPbzxlt-GO8UbSUqN-6Od04kEvA9g$ > > When buildbot has been installed on the platform where the buildbot worker is to be run, this is how a worker is created: > > $ buildbot-worker create-worker --use-tls BASEDIR \ > buildbot.openssl.org:9989 Oracle-ILOM 'Cu;Dryt8' > > where BASEDIR is determined by you. See further down for a few notes on TLS. > > To run a buildbot worker, you do this: > > $ buildbot-worker start BASEDIR > > Apart from the software needed to run a buildbot worker, and the utilities that are the normal part of the operating system, you also need to ensure that the following components are available: > > - toolchains, i.e. C compiler, linker, make. If you have specified > toolchains in the worker request form, you need to ensure that all > of them are installed. > > - git > > Regarding TLS, it may be that the buildbot worker platform doesn't have the appropriate certification verification roots set up. In that case, you may need to apply the attached buildbot.tac patch, and store the attached PEM files in a directory of your choice. Finish up by find the string '/PATH/TO/ssl-roots-dir' and replace its contents with the path of directory where you stored the PEM files. > From chris.brych at oracle.com Mon Jun 28 21:50:32 2021 From: chris.brych at oracle.com (Chris Brych) Date: Mon, 28 Jun 2021 21:50:32 +0000 Subject: [buildbot-admin] Buildbot Master Cert Expiration Message-ID: Hi OMC Team, Our ILOM team came across this information while trying to connect back in June. See below: Certificate: Data: Version: 3 (0x2) Serial Number: 03:f2:44:b8:77:d0:0a:c6:a5:fa:cc:96:a4:d2:af:0d:f4:86 Signature Algorithm: sha256WithRSAEncryption Issuer: C=US, O=Let's Encrypt, CN=R3 Validity Not Before: Mar 18 10:14:56 2021 GMT Not After : Jun 16 10:14:56 2021 GMT Subject: CN=buildbot.openssl.org Can you provide us with a new certificate if it is available. Thanks. Cheers, Chris [Oracle] Chris Brych | Senior Principal Security Analyst Oracle Security Evaluations - Global Product Security Ottawa, Ontario | Canada +1-905-267-9352 (O) | +1-613-867-1241 (M) [Green Oracle] Oracle is committed to developing practices and products that help protect the environment -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1296 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 866 bytes Desc: image004.jpg URL: From tjh at cryptsoft.com Mon Jun 28 22:02:14 2021 From: tjh at cryptsoft.com (Tim Hudson) Date: Tue, 29 Jun 2021 08:02:14 +1000 Subject: [buildbot-admin] buildbot master cert expired Message-ID: openssl s_client -state -debug -showcerts -connect buildbot.openssl.org:9989 If there is an automated letsencrypt update process in place it will also need to restart the master. If there isn't an automated update process in place it needs to be put in place along with an automatic master restart. That is the "fun" of using short-lived certificates. Certificate chain 0 s:CN = buildbot.openssl.org i:C = US, O = Let's Encrypt, CN = R3 a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: Mar 18 10:14:56 2021 GMT; NotAfter: Jun 16 10:14:56 2021 GMT -----BEGIN CERTIFICATE----- MIIFSTCCBDGgAwIBAgISA/JEuHfQCsal+syWpNKvDfSGMA0GCSqGSIb3DQEBCwUA MDIxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQD EwJSMzAeFw0yMTAzMTgxMDE0NTZaFw0yMTA2MTYxMDE0NTZaMB8xHTAbBgNVBAMT FGJ1aWxkYm90Lm9wZW5zc2wub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEA3xWpyaSZANRIiEA6gJMnGlyvVOjBlJuoMWqJD1mPsbMtjD880TXTeCci ERR2QcSxJjc3znNw4ECfVmejlaURudptsh5BOJ9gq7tA6p8Bi4B3h/peb1GPyoGN fM5668ArEjvXvBT5vFcq42xJ0Mu9EvbHvVaJnnW+EA0SRYMzyisJ/8sJ0Qg+/NaS ZZVXyn9CjNSMNiqjmtCoJxd47Xk8QUbV+cLRjM3hoI8kAO2rQ97L4WgE8KX7+KZM FUJEwVsz7ZUczPKfHEjd7XqSHIbcvJivCuJ2bKSym1hOE7X/0iS9piq0psVwXud1 ICOLBAofPdMfH3yrj83VcEotjpFWuQIDAQABo4ICajCCAmYwDgYDVR0PAQH/BAQD AgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMBBggrBgEFBQcDAjAMBgNVHRMBAf8EAjAA MB0GA1UdDgQWBBQ/w+DHYy/EcqRAGuHVpQs2veYgATAfBgNVHSMEGDAWgBQULrMX t1hWy65QCUDmH6+dixTCxjBVBggrBgEFBQcBAQRJMEcwIQYIKwYBBQUHMAGGFWh0 dHA6Ly9yMy5vLmxlbmNyLm9yZzAiBggrBgEFBQcwAoYWaHR0cDovL3IzLmkubGVu Y3Iub3JnLzA6BgNVHREEMzAxghRidWlsZGJvdC5vcGVuc3NsLm9yZ4IZZmlwcy5i dWlsZGJvdC5vcGVuc3NsLm9yZzBMBgNVHSAERTBDMAgGBmeBDAECATA3BgsrBgEE AYLfEwEBATAoMCYGCCsGAQUFBwIBFhpodHRwOi8vY3BzLmxldHNlbmNyeXB0Lm9y ZzCCAQQGCisGAQQB1nkCBAIEgfUEgfIA8AB3AESUZS6w7s6vxEAH2Kj+KMDa5oK+ 2MsxtT/TM5a1toGoAAABeEULrVQAAAQDAEgwRgIhAI77JzgQQoEwMjjyNgKR6edX Nm4zJbDVKIMFaOB5o1HBAiEA5umG+jVeyX/HVbXOQ+JVR6yxqFVkkxz+Ce5PmyaB 5q4AdQB9PvL4j/+IVWgkwsDKnlKJeSvFDngJfy5ql2iZfiLw1wAAAXhFC62FAAAE AwBGMEQCIEl8cbcQ33QqX81KQfs00v8WhFGsJjzMA6IPy+Q34tgmAiB9Cq1a9X6P o4OBaSoCM+sfcmLrVhjqfqv1NRufKM4YCDANBgkqhkiG9w0BAQsFAAOCAQEAkZZ4 rQNT5r5IAZ518/Wd2VUGgE0/aKQZ0hm+BSIdAQ7XVHEecy0uxAgNLgioF8fX8owB EfNPUSBHX+B3lEbm5/YXR+PLdHxx05VbJYVDOyMh1dSizW+V6cLd5+QbmR8qDnG/ 2K4AannabWnrN+QLhhpTVPawR5VjI1srrePFl/ESIl+UeXm9qjfzEn0IdO/1bZbV 8ftQM5D2mj0tNoYeYJFeKO7PD1K32eDtBnADYVFOMWGy6ozfkZ2NT7y9CXACIlZv RJ+giNWzLLxOfUOYERoBwk6KjSpJKoZxL4UVVH6U7X2Ue8hbCfRGs79vaK4S2zJT aGT2bTKE3NYfp0pRGA== -----END CERTIFICATE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: