/etc/burp/clientconfdir/testclient contains a well known password
(it's simmilar to the combination on my luggage).
So on installation I remove that file.
An upgrade puts it back. That seems... unwise.
The way I understand things anyone who can connect to the burp server
can request a cert with that password for CN testclient and then force
a backup run.
Can we maybe not do that?
Thanks,
Florian
--
I'm not entirely sure you are real.
Thursday, November 29, 2018
Re: powerpc bulk build report
On Thu, Nov 29, 2018 at 03:19:49PM -0700, landry@openbsd.org wrote:
> bulk build on macppc-1.ports.openbsd.org
> started on Tue Nov 20 01:17:37 MST 2018
> finished at Thu Nov 29 15:19:14 MST 2018
> lasted 10D07h01m
> done with kern.version=OpenBSD 6.4-current (GENERIC.MP) #282: Mon Nov 19 20:42:01 MST 2018
>
> built packages:7017
> Nov 20:748
> Nov 21:580
> Nov 22:675
> Nov 23:402
> Nov 24:463
> Nov 25:375
> Nov 26:527
> Nov 27:581
> Nov 28:388
> Nov 29:2277
>
>
>
> critical path missing pkgs: http://build-failures.rhaalovely.net//powerpc/2018-11-20/summary.log
Same thing as sparc64, this bulk was done with the gcc6 diff (and some
others..) - failure logs are available for anyone to poke - i'll revert
back to a "no diff" portstree for the upcoming bulks.
Landry
> bulk build on macppc-1.ports.openbsd.org
> started on Tue Nov 20 01:17:37 MST 2018
> finished at Thu Nov 29 15:19:14 MST 2018
> lasted 10D07h01m
> done with kern.version=OpenBSD 6.4-current (GENERIC.MP) #282: Mon Nov 19 20:42:01 MST 2018
>
> built packages:7017
> Nov 20:748
> Nov 21:580
> Nov 22:675
> Nov 23:402
> Nov 24:463
> Nov 25:375
> Nov 26:527
> Nov 27:581
> Nov 28:388
> Nov 29:2277
>
>
>
> critical path missing pkgs: http://build-failures.rhaalovely.net//powerpc/2018-11-20/summary.log
Same thing as sparc64, this bulk was done with the gcc6 diff (and some
others..) - failure logs are available for anyone to poke - i'll revert
back to a "no diff" portstree for the upcoming bulks.
Landry
Subscribe to:
Posts (Atom)