Re: Call for participation
No firm dates yet, we’ll make sure everyone has ample time ahead of, and communicate session schedules when determined > On 4 Sep 2021, at 12:59 am, Shawn Webb wrote: > > On Thu, Sep 02, 2021 at 08:43:21AM -0600, Warner Losh wrote: >> Greetings, >> >> As teased on twitter, now that summer is over, it's a good time to start >> working on the next steps with git. When we moved to git, we knew a number >> of things would come in phase 2 since phase 1 was limited to moving away >> from subversion and to git. >> >> Now's the time for phase 2. The deferred items included better CI >> pipelines, better integration with popular hosting sites like github and >> gitlab, a look at the tools we have today and how they fit together, and a >> bunch of other items that were less well defined. I've spent the last >> several months looking at the different practices in open source, >> looking at our tools, etc. We have bits and pieces of many of these items, >> but are missing some glue between what we have. Other areas need more >> extensive work. >> >> To coordinate this work, I'll be leading a team to look at what we can do >> in the short term, the medium term and where we think we want to be in the >> long term. I plan on having bi-weekly meetings to discuss different issues >> that come up, to coordinate work and experiments and to give some structure >> to encouragement for progress to be made. >> >> This will be a collaborative effort between the developers and the user >> community that contributes patches to any part of FreeBSD (the base, ports >> and docs). If you are interested in participating, please drop me a line. >> We'll have a core office hours to talk about this soon, and I'd like to >> start discussions with those that are interested before hand, as well as >> invite people to participate in the office hours. After that, we'll have a >> kick off meeting that's open to everybody who can respectfully contribute. >> >> Looking forward to hearing from you. > > Hey Warner, > > I'd be happy to talk about HardenedBSD's switch from GitHub to Gitea > and finally to GitLab. We had a lot of troubles with Gitea and ended > up with GitLab. > > When are you thinking of holding that meeting? > > Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc
Re: FreeBSD-13-STABLE: lib/libsecureboot/verify_file.c: error: use of undeclared identifier 'SOPEN_MAX'
> On 3. Sep 2021, at 18:59, FreeBSD User wrote:
>
> Hello,
>
> enabling
>
> WITH_BEARSSL
>
> in src.conf renders buildworld on 13-STABLE to fail, but not on
> 14-CURRENT.
>
>
>
> This is the difference between the sources, obviously 14-CURRENT contains the
> correct
> definition of SOPEN_MAX, while 13-STABLE not (undefinied SOPNE_MAX triggers
> the compiler to
> fail,
> /usr/src/lib/libsecureboot/verify_file.c:59:22: error: use of undeclared
> identifier
> 'SOPEN_MAX'), see
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258211
>
>
> [...]
> 13-STABLE
> :/pool/sources/13-STABLE/src # grep -r SOPEN_MAX .
> ./lib/libsecureboot/tests/Makefile:XCFLAGS.verify_file += -DSOPEN_MAX=64
> ./lib/libsecureboot/verify_file.c:static int ve_status[SOPEN_MAX+1];
> ./lib/libsecureboot/verify_file.c: if (fd >= 0 && fd < SOPEN_MAX) {
> ./lib/libsecureboot/verify_file.c: ve_status[SOPEN_MAX] = ves;
> ./lib/libsecureboot/verify_file.c: *@li ve_status[SOPEN_MAX] if
> ve_status_state is none
> ./lib/libsecureboot/verify_file.c: fd >= 0 && fd < SOPEN_MAX)
> ./lib/libsecureboot/verify_file.c: return (ve_status[SOPEN_MAX]); /*
> most recent */
>
> [...]
> 14-CURRENT
> ./lib/libsecureboot/tests/Makefile:XCFLAGS.verify_file += -DSOPEN_MAX=64
> ./lib/libsecureboot/verify_file.c:#ifndef SOPEN_MAX
> ./lib/libsecureboot/verify_file.c:#define SOPEN_MAX 64
> ./lib/libsecureboot/verify_file.c:static int ve_status[SOPEN_MAX+1];
> ./lib/libsecureboot/verify_file.c: if (fd >= 0 && fd < SOPEN_MAX) {
> ./lib/libsecureboot/verify_file.c: ve_status[SOPEN_MAX] = ves;
> ./lib/libsecureboot/verify_file.c: *@li ve_status[SOPEN_MAX] if
> ve_status_state is none
> ./lib/libsecureboot/verify_file.c: fd >= 0 && fd < SOPEN_MAX)
> ./lib/libsecureboot/verify_file.c: return (ve_status[SOPEN_MAX]); /*
> most recent */
>
>
>
>
> --
> O. Hartmann
>
Hi!
Sorry, it is fixed now. Missed one cherry-pick.
rgds,
toomas
FreeBSD-13-STABLE: lib/libsecureboot/verify_file.c: error: use of undeclared identifier 'SOPEN_MAX'
Hello,
enabling
WITH_BEARSSL
in src.conf renders buildworld on 13-STABLE to fail, but not on
14-CURRENT.
This is the difference between the sources, obviously 14-CURRENT contains the
correct
definition of SOPEN_MAX, while 13-STABLE not (undefinied SOPNE_MAX triggers the
compiler to
fail,
/usr/src/lib/libsecureboot/verify_file.c:59:22: error: use of undeclared
identifier
'SOPEN_MAX'), see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258211
[...]
13-STABLE
:/pool/sources/13-STABLE/src # grep -r SOPEN_MAX .
./lib/libsecureboot/tests/Makefile:XCFLAGS.verify_file += -DSOPEN_MAX=64
./lib/libsecureboot/verify_file.c:static int ve_status[SOPEN_MAX+1];
./lib/libsecureboot/verify_file.c: if (fd >= 0 && fd < SOPEN_MAX) {
./lib/libsecureboot/verify_file.c: ve_status[SOPEN_MAX] = ves;
./lib/libsecureboot/verify_file.c: *@li ve_status[SOPEN_MAX] if
ve_status_state is none
./lib/libsecureboot/verify_file.c: fd >= 0 && fd < SOPEN_MAX)
./lib/libsecureboot/verify_file.c: return (ve_status[SOPEN_MAX]); /* most
recent */
[...]
14-CURRENT
./lib/libsecureboot/tests/Makefile:XCFLAGS.verify_file += -DSOPEN_MAX=64
./lib/libsecureboot/verify_file.c:#ifndef SOPEN_MAX
./lib/libsecureboot/verify_file.c:#define SOPEN_MAX 64
./lib/libsecureboot/verify_file.c:static int ve_status[SOPEN_MAX+1];
./lib/libsecureboot/verify_file.c: if (fd >= 0 && fd < SOPEN_MAX) {
./lib/libsecureboot/verify_file.c: ve_status[SOPEN_MAX] = ves;
./lib/libsecureboot/verify_file.c: *@li ve_status[SOPEN_MAX] if
ve_status_state is none
./lib/libsecureboot/verify_file.c: fd >= 0 && fd < SOPEN_MAX)
./lib/libsecureboot/verify_file.c: return (ve_status[SOPEN_MAX]); /* most
recent */
--
O. Hartmann
Re: Call for participation
On Thu, Sep 02, 2021 at 08:43:21AM -0600, Warner Losh wrote: > Greetings, > > As teased on twitter, now that summer is over, it's a good time to start > working on the next steps with git. When we moved to git, we knew a number > of things would come in phase 2 since phase 1 was limited to moving away > from subversion and to git. > > Now's the time for phase 2. The deferred items included better CI > pipelines, better integration with popular hosting sites like github and > gitlab, a look at the tools we have today and how they fit together, and a > bunch of other items that were less well defined. I've spent the last > several months looking at the different practices in open source, > looking at our tools, etc. We have bits and pieces of many of these items, > but are missing some glue between what we have. Other areas need more > extensive work. > > To coordinate this work, I'll be leading a team to look at what we can do > in the short term, the medium term and where we think we want to be in the > long term. I plan on having bi-weekly meetings to discuss different issues > that come up, to coordinate work and experiments and to give some structure > to encouragement for progress to be made. > > This will be a collaborative effort between the developers and the user > community that contributes patches to any part of FreeBSD (the base, ports > and docs). If you are interested in participating, please drop me a line. > We'll have a core office hours to talk about this soon, and I'd like to > start discussions with those that are interested before hand, as well as > invite people to participate in the office hours. After that, we'll have a > kick off meeting that's open to everybody who can respectfully contribute. > > Looking forward to hearing from you. Hey Warner, I'd be happy to talk about HardenedBSD's switch from GitHub to Gitea and finally to GitLab. We had a lot of troubles with Gitea and ended up with GitLab. When are you thinking of holding that meeting? Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc signature.asc Description: PGP signature
Re: Call for participation
Hi, > On Sep 2, 2021, at 07:44, Warner Losh wrote: > > Greetings, > > As teased on twitter, now that summer is over, it's a good time to start > working on the next steps with git. When we moved to git, we knew a number > of things would come in phase 2 since phase 1 was limited to moving away > from subversion and to git. > > Now's the time for phase 2. The deferred items included better CI > pipelines, better integration with popular hosting sites like github and > gitlab, a look at the tools we have today and how they fit together, and a > bunch of other items that were less well defined. I've spent the last > several months looking at the different practices in open source, > looking at our tools, etc. We have bits and pieces of many of these items, > but are missing some glue between what we have. Other areas need more > extensive work. > > To coordinate this work, I'll be leading a team to look at what we can do > in the short term, the medium term and where we think we want to be in the > long term. I plan on having bi-weekly meetings to discuss different issues > that come up, to coordinate work and experiments and to give some structure > to encouragement for progress to be made. > > This will be a collaborative effort between the developers and the user > community that contributes patches to any part of FreeBSD (the base, ports > and docs). If you are interested in participating, please drop me a line. > We'll have a core office hours to talk about this soon, and I'd like to > start discussions with those that are interested before hand, as well as > invite people to participate in the office hours. After that, we'll have a > kick off meeting that's open to everybody who can respectfully contribute. > > Looking forward to hearing from you. This is potentially good timing. If anyone is interested in following up with pre-commit, or working with me on a PoC, please let me know. I have worked with it somewhat extensively and have found it to be a wonderful developer companion infrastructure and tool paired well with git. I bring this up because some of the items which could be handled prior to hitting CR could be done via pre-commit, client side. Cheers, -Enji
Re: Call for participation
Count me in On 2021-09-02 7:43, Warner Losh wrote: Greetings, As teased on twitter, now that summer is over, it's a good time to start working on the next steps with git. When we moved to git, we knew a number of things would come in phase 2 since phase 1 was limited to moving away from subversion and to git. Now's the time for phase 2. The deferred items included better CI pipelines, better integration with popular hosting sites like github and gitlab, a look at the tools we have today and how they fit together, and a bunch of other items that were less well defined. I've spent the last several months looking at the different practices in open source, looking at our tools, etc. We have bits and pieces of many of these items, but are missing some glue between what we have. Other areas need more extensive work. To coordinate this work, I'll be leading a team to look at what we can do in the short term, the medium term and where we think we want to be in the long term. I plan on having bi-weekly meetings to discuss different issues that come up, to coordinate work and experiments and to give some structure to encouragement for progress to be made. This will be a collaborative effort between the developers and the user community that contributes patches to any part of FreeBSD (the base, ports and docs). If you are interested in participating, please drop me a line. We'll have a core office hours to talk about this soon, and I'd like to start discussions with those that are interested before hand, as well as invite people to participate in the office hours. After that, we'll have a kick off meeting that's open to everybody who can respectfully contribute. Looking forward to hearing from you. Warner
Re: Call for participation
Hey Warner, Count me in, please. Cheers, Faraz On Thu, Sep 02, 2021 at 08:43:21AM -0600, Warner Losh wrote: > Greetings, > > As teased on twitter, now that summer is over, it's a good time to start > working on the next steps with git. When we moved to git, we knew a number > of things would come in phase 2 since phase 1 was limited to moving away > from subversion and to git. > > Now's the time for phase 2. The deferred items included better CI > pipelines, better integration with popular hosting sites like github and > gitlab, a look at the tools we have today and how they fit together, and a > bunch of other items that were less well defined. I've spent the last > several months looking at the different practices in open source, > looking at our tools, etc. We have bits and pieces of many of these items, > but are missing some glue between what we have. Other areas need more > extensive work. > > To coordinate this work, I'll be leading a team to look at what we can do > in the short term, the medium term and where we think we want to be in the > long term. I plan on having bi-weekly meetings to discuss different issues > that come up, to coordinate work and experiments and to give some structure > to encouragement for progress to be made. > > This will be a collaborative effort between the developers and the user > community that contributes patches to any part of FreeBSD (the base, ports > and docs). If you are interested in participating, please drop me a line. > We'll have a core office hours to talk about this soon, and I'd like to > start discussions with those that are interested before hand, as well as > invite people to participate in the office hours. After that, we'll have a > kick off meeting that's open to everybody who can respectfully contribute. > > Looking forward to hearing from you. > > Warner signature.asc Description: PGP signature
