Hi Dries
On 26/07/2020 09:30, driesm.michi...@gmail.com wrote:
Following the discussion a while ago regarding the import of a DHCPv6 client.
The current state of dhcpcd is such that capsicum and privelege separation is
fully implemented.
How do we move forward with this? I’d really like to
Hi Ben
On 30/11/2019 02:52, Ben Woods wrote:
I have just added the new port net/dhcpcd-devel which uses the latest commit
(273915d), and enables privilege separation.
If you would care to update port net/dhcpcd to dhcpcd-9.0.0 which I've just
released this discussion can move forwards again :
Hey Ben
On 30/11/2019 02:52, Ben Woods wrote:
I have just added the new port net/dhcpcd-devel which uses the latest
commit (273915d), and enables privilege separation.
So far it seems to be working ok for me!
Good!
I've had a fair bit of feedback from the initial commit and the latest
(whic
On Fri, 29 Nov 2019 at 09:40, Roy Marples wrote:
> On 28/11/2019 22:50, Ben Woods wrote:
> > It is not yet enabled by default until he gets more feedback from others
> > that it is working ok. I intend to update the FreeBSD port to enable
> > this feature (perhaps with a “-devel” port) to allow i
On 28/11/2019 22:50, Ben Woods wrote:
It is not yet enabled by default until he gets more feedback from others
that it is working ok. I intend to update the FreeBSD port to enable
this feature (perhaps with a “-devel” port) to allow it to be tested
more easily on FreeBSD.
Please add it as a n
On Tue, 15 Oct 2019 at 9:00 pm, Hiroki Sato wrote:
> Roy Marples wrote
> in :
> ro> Sorry if it was not clear. The discussion involves what is the
> ro> required acceptance for Priviledge Seperation because this is quite
> ro> new to me.
> ro>
> ro> My current idea is to open DHCP, IPv6RA and
On 14 Oct 2019, at 23:04, Ben Woods wrote:
Whilst I don’t have anything against wide-dhcp, I personally prefer
integrated IPv4/IPv6 tools. ping vs ping6 for example would be better
integrated in my opinion.
I have a totally different opinion on this. I prefer to have a tool
that does one job
Roy Marples wrote
in :
ro> On 13/10/2019 20:32, Hiroki Sato wrote:
ro> > Ben Woods wrote
ro> >in
ro> >:
ro> > wo> On Fri, 11 Oct 2019 at 08:32, Ben Woods
ro> > wrote:
ro> > wo> As promised, I have completed my initial work to import dhcpcd
ro> > into FreeBSD
ro> > wo> base, and it is
On Mon, 14 Oct 2019 at 3:34 am, Hiroki Sato wrote:
> How do you want to proceed the discussion? I sent my view and made
> myself clear that importing dhcpcd into the base system as-is is not
> a good idea. What is your answer to my concerns? I also agree with
> Brooks about a need for sandb
On Sat, 12 Oct 2019 at 3:42 am, Hiroki Sato wrote:
> I do not have a strong objection on dhcpcd (I am using it on some of
> my FreeBSD boxes actually) but let me explain the reason why I chose
> wide-dhcp as the candidate. That is because it is a small,
> functional DHCPv6-only implementation
On Tue, Oct 15, 2019 at 06:41:36AM +0800, Ben Woods wrote:
> On Sat, 12 Oct 2019 at 1:45 am, Brooks Davis wrote:
>
> > DHCP is one of the most exposed attack surfaces in existence. We expect
> > it to take input from explicitly untrustworthy networks and perform
> > actions as root. It might be
On Sat, 12 Oct 2019 at 1:45 am, Brooks Davis wrote:
> DHCP is one of the most exposed attack surfaces in existence. We expect
> it to take input from explicitly untrustworthy networks and perform
> actions as root. It might be OK to import this as a stopgap only
> supporting IPv6, but without c
On 13/10/2019 20:32, Hiroki Sato wrote:
Ben Woods wrote
in :
wo> On Fri, 11 Oct 2019 at 08:32, Ben Woods wrote:
wo> As promised, I have completed my initial work to import dhcpcd into FreeBSD
wo> base, and it is ready for review, testing and comment at the link below.
wo> https://reviews.fr
Ben Woods wrote
in :
wo> On Fri, 11 Oct 2019 at 08:32, Ben Woods wrote:
wo> As promised, I have completed my initial work to import dhcpcd into FreeBSD
wo> base, and it is ready for review, testing and comment at the link below.
wo> https://reviews.freebsd.org/D22012
wo>
wo> As per the comment
On Fri, 11 Oct 2019 at 08:32, Ben Woods wrote:
> On Mon, 7 Oct 2019 at 8:53 am, Ben Woods wrote:
>
>> On Thu, 16 May 2019 at 2:25 am, Hiroki Sato wrote:
>>
>>> wrote
>>> in <001e01d50b49$176104d0$46230e70$@gmail.com>:
>>>
>>> dr> Has anyone ever thought or considered integrating an IPv6 DHCP
On 12/10/2019 03:04, Hiroki Sato wrote:
I emphasize again here that people who want to use dhcpcd are still
able to install net/dhcpcd and override a combination of utilities
such as rtsold. Ditto for ISC's IPv6-capable dhclient. My opinion
about the import is that if we adopt dhcpcd in
Roy Marples wrote
in :
ro> On 11/10/2019 20:40, Hiroki Sato wrote:
ro> > I do not have a strong objection on dhcpcd (I am using it on some of
ro> > my FreeBSD boxes actually) but let me explain the reason why I chose
ro> > wide-dhcp as the candidate. That is because it is a small,
ro> >
On 11/10/2019 20:40, Hiroki Sato wrote:
I do not have a strong objection on dhcpcd (I am using it on some of
my FreeBSD boxes actually) but let me explain the reason why I chose
wide-dhcp as the candidate. That is because it is a small,
functional DHCPv6-only implementation. I am planni
Ben Woods wrote
in :
wo> On Thu, 16 May 2019 at 2:25 am, Hiroki Sato wrote:
wo>
wo> > wrote
wo> > in <001e01d50b49$176104d0$46230e70$@gmail.com>:
wo> >
wo> > dr> Has anyone ever thought or considered integrating an IPv6 DHCP client
wo> > in
wo> > dr> base?
wo> >
wo> > I have a plan to impo
Roy Marples wrote
in :
ro> > A dhcp Client is a necessary part of the OS (though a bit less so with
ro> > IPV6) but the serer side can be a port. (as it is).
ro>
ro> How is FreeBSD handling DNSSL + RDNSS over IPv6RA? That's pretty
ro> standard now and I don't see a userland compoenent for it.
On Fri, Oct 11, 2019 at 08:32:59AM +0800, Ben Woods wrote:
> On Mon, 7 Oct 2019 at 8:53 am, Ben Woods wrote:
>
> > On Thu, 16 May 2019 at 2:25 am, Hiroki Sato wrote:
> >
> >> wrote
> >> in <001e01d50b49$176104d0$46230e70$@gmail.com>:
> >>
> >> dr> Has anyone ever thought or considered integra
On Mon, 7 Oct 2019 at 8:53 am, Ben Woods wrote:
> On Thu, 16 May 2019 at 2:25 am, Hiroki Sato wrote:
>
>> wrote
>> in <001e01d50b49$176104d0$46230e70$@gmail.com>:
>>
>> dr> Has anyone ever thought or considered integrating an IPv6 DHCP client
>> in
>> dr> base?
>>
>
> I would like to discuss
On 07/10/2019 20:20, Julian Elischer wrote:
> On 10/7/19 12:05 PM, Roy Marples wrote:
>> On 07/10/2019 19:45, Julian Elischer wrote:
>>> I'm not HRS, but as it uses netlink, how does NetBSD use it? (i.e.
>>> how do we simulate that?)
>>
>> dhcpcd has a driver per OS:
>> BSD == route(4)
>
> though
On 10/7/19 12:05 PM, Roy Marples wrote:
On 07/10/2019 19:45, Julian Elischer wrote:
I'm not HRS, but as it uses netlink, how does NetBSD use it? (i.e.
how do we simulate that?)
dhcpcd has a driver per OS:
BSD == route(4)
though sometimes I wonder if that could not be improved.. it's now
wh
On 07/10/2019 19:45, Julian Elischer wrote:
I'm not HRS, but as it uses netlink, how does NetBSD use it? (i.e. how
do we simulate that?)
dhcpcd has a driver per OS:
BSD == route(4)
Linux == netlink(3)
Solaris == route(4) along with an unholy mashup of streamio(7)
I try and keep OS specific de
On 10/6/19 5:53 PM, Ben Woods wrote:
On Thu, 16 May 2019 at 2:25 am, Hiroki Sato wrote:
wrote
in <001e01d50b49$176104d0$46230e70$@gmail.com>:
dr> Has anyone ever thought or considered integrating an IPv6 DHCP client
in
dr> base?
I have a plan to import wide-dhcp6 into the base system b
2019-05-15 driesm.michiels wrote:
Has anyone ever thought or considered integrating an IPv6 DHCP client
in base? [...]
I have a plan to import wide-dhcp6 into the base system because it is
simple enough. [...]
Other alternatives? Thoughts?
This topic came up three years ago. David A. Bright rep
On Thu, 16 May 2019 at 2:25 am, Hiroki Sato wrote:
> wrote
> in <001e01d50b49$176104d0$46230e70$@gmail.com>:
>
> dr> Has anyone ever thought or considered integrating an IPv6 DHCP client
> in
> dr> base?
>
> I have a plan to import wide-dhcp6 into the base system because it is
> simple enoug
> -Original Message-
> From: driesm.michi...@gmail.com
> Sent: woensdag 15 mei 2019 21:53
> To: 'Hiroki Sato'
> Cc: freebsd-net@freebsd.org
> Subject: RE: DHCPv6 client in base
>
> > -Original Message-
> > From: Hiroki Sato
> -Original Message-
> From: Hiroki Sato
> Sent: woensdag 15 mei 2019 21:43
> To: driesm.michi...@gmail.com
> Cc: freebsd-net@freebsd.org
> Subject: Re: DHCPv6 client in base
>
> wrote
> in <006001d50b53$72a22e00$57e68a00$@gmail.com>:
>
> dr
wrote
in <006001d50b53$72a22e00$57e68a00$@gmail.com>:
dr> > I have a plan to import wide-dhcp6 into the base system because it is
simple
dr> > enough.
dr>
dr> Thats nice! Any timeline for this; 13.0 RELEASE?
Yes, at the latest. I originally planned it before 12.0 but not
happened for som
> -Original Message-
> From: owner-freebsd-...@freebsd.org On
> Behalf Of Hiroki Sato
> Sent: woensdag 15 mei 2019 20:20
> To: driesm.michi...@gmail.com
> Cc: freebsd-net@freebsd.org
> Subject: Re: DHCPv6 client in base
>
> wrote
> in <001e01d5
wrote
in <001e01d50b49$176104d0$46230e70$@gmail.com>:
dr> Has anyone ever thought or considered integrating an IPv6 DHCP client in
dr> base?
I have a plan to import wide-dhcp6 into the base system because it is
simple enough.
dr> net/dhcp6 isn't really maintained anymore from the KAME days
33 matches
Mail list logo
