Re: burp 2.2.12

2018-11-28 Thread Stuart Henderson
On 2018/11/28 16:06, Florian Obser wrote:
> On Wed, Nov 28, 2018 at 09:49:28AM -0500, Brian Callahan wrote:
> > Hi Florian --
> > 
> > On 11/25/18 5:40 AM, Florian Obser wrote:
> > > I started to use burp 2.1 the other day and has the shortcoming that
> > > it can only listen on one port. And :: means IPv6 in OpenBSD, you
> > > don't magically get a v4 socket, too.
> > > 
> > > 2.2.12 gained the feature of listening on multiple sockets, but the 
> > > syntax changed:
> > > 
> > > -address = ::
> > > -port = 4971
> > > +listen = 0.0.0.0:4971
> > > +listen = :::4971
> > >   max_children = 5
> > > -status_address = localhost
> > > -status_port = 4972
> > > +listen_status = 127.0.0.1:5972
> > > +listen_status = ::1:5972
> > >   max_status_children = 5
> > > 
> > > I tried these combinations:
> > > 
> > > server: 2.1.28
> > > client: 2.2.12
> > > 
> > > server: 2.2.12
> > > client: 2.1.28 (it warns that the client should be updated)
> > > 
> > > server: 2.2.12
> > > client: 2.2.12
> > > 
> > > So it seems like we could drop 2.1 once this is in.
> > > 
> > > OKs, further tests?
> > > 
> > > 
> > > 
> > 
> > When I ran `make update-plist', I got the following message:
> > Can't put into any plist (no applicable prefix):
> >     /var/run/burp

That can be ignored.

> > Additionally, the PLIST changed, more than just cosmetic rearranging of
> > entries.
> 
> Thanks for looking. That's why they don't let me bring my aura near
> anything important. Nevermind then.

Definitely seems a useful addition - I'll regenerate PLISTs for 2.0 and 2.1
to make it a bit clearer ("make plist" changed the order of what it outputs
since they were added), OK to add 2.2 with the attached PLIST.
@comment $OpenBSD: PLIST,v 1.1 2018/03/08 14:41:02 sthen Exp $
@option is-branch
@conflict burp-*
@newgroup _burp:794
@newuser _burp:794:794:daemon:BackUp and Recovery 
Daemon:/var/empty:/sbin/nologin
@rcscript ${RCDIR}/burp
@bin bin/vss_strip
@man man/man8/bedup.8
@man man/man8/bsigs.8
@man man/man8/bsparse.8
@man man/man8/burp.8
@man man/man8/burp_ca.8
@man man/man8/vss_strip.8
sbin/bedup
sbin/bsigs
sbin/bsparse
@bin sbin/burp
sbin/burp_ca
share/burp/
share/burp/scripts/
share/burp/scripts/backup_tool_script
share/burp/scripts/notify_script
share/burp/scripts/ssl_extra_checks_script
share/burp/scripts/summary_script
share/burp/scripts/timer_script
share/doc/burp/
share/doc/burp/CHANGELOG
share/doc/burp/CONTRIBUTORS
share/doc/burp/DONATIONS
share/doc/burp/LICENSE
share/doc/burp/README
share/doc/burp/UPGRADING
share/doc/burp/add-remove.txt
share/doc/burp/autoupgrade.txt
share/doc/burp/backup_phases.txt
share/doc/burp/backup_tool_script.txt
share/doc/burp/baremetal-windows2008.txt
share/doc/burp/baremetal-windows7-hirens.txt
share/doc/burp/baremetal-windows7.txt
share/doc/burp/baremetal-windows7and8.txt
share/doc/burp/burp_ca.txt
share/doc/burp/debug.txt
share/doc/burp/readwrite.txt
share/doc/burp/retention.txt
share/doc/burp/security-models.txt
share/doc/burp/server-basics.txt
share/doc/burp/shuffling.txt
share/doc/burp/status-monitor.txt
share/doc/burp/tests.txt
share/doc/burp/timer_script.txt
share/doc/burp/working_dir.txt
share/examples/burp/
share/examples/burp/CA-client/
@mode 750
@owner _burp
@group _burp
@sample ${SYSCONFDIR}/
@mode
share/examples/burp/CA.cnf
@sample ${SYSCONFDIR}/CA.cnf
share/examples/burp/burp-server.conf
@sample ${SYSCONFDIR}/burp-server.conf
share/examples/burp/burp.conf
@sample ${SYSCONFDIR}/burp.conf
@owner
@group
share/examples/burp/clientconfdir/
share/examples/burp/clientconfdir/incexc/
share/examples/burp/clientconfdir/incexc/example
@owner _burp
@group _burp
@sample ${SYSCONFDIR}/clientconfdir/incexc/example
share/examples/burp/clientconfdir/testclient
@sample ${SYSCONFDIR}/clientconfdir/testclient
@mode 750
@sample ${LOCALSTATEDIR}/spool/burp/
@sample ${SYSCONFDIR}/CA-client/
@sample ${SYSCONFDIR}/clientconfdir/
@sample ${SYSCONFDIR}/clientconfdir/incexc/


Re: burp 2.2.12

2018-11-28 Thread Florian Obser
On Wed, Nov 28, 2018 at 09:49:28AM -0500, Brian Callahan wrote:
> Hi Florian --
> 
> On 11/25/18 5:40 AM, Florian Obser wrote:
> > I started to use burp 2.1 the other day and has the shortcoming that
> > it can only listen on one port. And :: means IPv6 in OpenBSD, you
> > don't magically get a v4 socket, too.
> > 
> > 2.2.12 gained the feature of listening on multiple sockets, but the syntax 
> > changed:
> > 
> > -address = ::
> > -port = 4971
> > +listen = 0.0.0.0:4971
> > +listen = :::4971
> >   max_children = 5
> > -status_address = localhost
> > -status_port = 4972
> > +listen_status = 127.0.0.1:5972
> > +listen_status = ::1:5972
> >   max_status_children = 5
> > 
> > I tried these combinations:
> > 
> > server: 2.1.28
> > client: 2.2.12
> > 
> > server: 2.2.12
> > client: 2.1.28 (it warns that the client should be updated)
> > 
> > server: 2.2.12
> > client: 2.2.12
> > 
> > So it seems like we could drop 2.1 once this is in.
> > 
> > OKs, further tests?
> > 
> > 
> > 
> 
> When I ran `make update-plist', I got the following message:
> Can't put into any plist (no applicable prefix):
>     /var/run/burp
> 
> Additionally, the PLIST changed, more than just cosmetic rearranging of
> entries.

Thanks for looking. That's why they don't let me bring my aura near
anything important. Nevermind then.

> 
> ~Brian

-- 
I'm not entirely sure you are real.



Re: burp 2.2.12

2018-11-28 Thread Brian Callahan

Hi Florian --

On 11/25/18 5:40 AM, Florian Obser wrote:

I started to use burp 2.1 the other day and has the shortcoming that
it can only listen on one port. And :: means IPv6 in OpenBSD, you
don't magically get a v4 socket, too.

2.2.12 gained the feature of listening on multiple sockets, but the syntax 
changed:

-address = ::
-port = 4971
+listen = 0.0.0.0:4971
+listen = :::4971
  max_children = 5
  
-status_address = localhost

-status_port = 4972
+listen_status = 127.0.0.1:5972
+listen_status = ::1:5972
  max_status_children = 5

I tried these combinations:

server: 2.1.28
client: 2.2.12

server: 2.2.12
client: 2.1.28 (it warns that the client should be updated)

server: 2.2.12
client: 2.2.12

So it seems like we could drop 2.1 once this is in.

OKs, further tests?





When I ran `make update-plist', I got the following message:
Can't put into any plist (no applicable prefix):
    /var/run/burp

Additionally, the PLIST changed, more than just cosmetic rearranging of 
entries.


~Brian



burp 2.2.12

2018-11-25 Thread Florian Obser
I started to use burp 2.1 the other day and has the shortcoming that
it can only listen on one port. And :: means IPv6 in OpenBSD, you
don't magically get a v4 socket, too.

2.2.12 gained the feature of listening on multiple sockets, but the syntax 
changed:

-address = ::
-port = 4971
+listen = 0.0.0.0:4971
+listen = :::4971
 max_children = 5
 
-status_address = localhost
-status_port = 4972
+listen_status = 127.0.0.1:5972
+listen_status = ::1:5972
 max_status_children = 5

I tried these combinations:

server: 2.1.28
client: 2.2.12

server: 2.2.12
client: 2.1.28 (it warns that the client should be updated)

server: 2.2.12
client: 2.2.12

So it seems like we could drop 2.1 once this is in.

OKs, further tests?



-- 
I'm not entirely sure you are real.


burp-2.2.tgz
Description: Binary data