Hi,
Currently syslogd accepts network input only for either IPv4 or
IPv6. To overcome this limitation, allow to specify more than one
listen addresses.
As multiple TLS contexts need more thought, implement it only for
TCP and UDP sockets now.
ok?
bluhm
Index: usr.sbin/syslogd/syslogd.8
==
On Fri, 30 Dec 2016 11:30:10 -0700
Theo de Raadt wrote:
> I'm wondering if anyone doing an install/upgrade has noticed any
> behaviour changes in the last week...
Did an auto_upgrade with pre-downloaded sets today. Got curious and did one
normal/manual update again from a mirror. No regressions.
As discussed, these files aren't used and aren't useful. make build +
make release are ok with this.
(Well, make release is ok until
COPY/usr/local/share/u-boot/am335x_boneblack/MLO/usr/mdec/am335x/MLO
cp: /usr/local/share/u-boot/am335x_boneblack/MLO: No such file or directory
becaus
On Dec 30, 2016 20:32, "Theo de Raadt" wrote:
I'm wondering if anyone doing an install/upgrade has noticed any
behaviour changes in the last week...
There's a secret diff being tested :-)
Hello,
so far I haven't noticed anything peculiar. Two or three distinct machines,
two for surfing and on
Alexander Bluhm writes:
> On Mon, Dec 26, 2016 at 04:54:54PM -0700, Theo de Raadt wrote:
>> I think programs should only block the absolutely critical things, and this
>> is overreach.
>
> Yes, blocking SIGINT and SIGQUIT is not clever. I thought there
> were races with SIGCHLD and SIGTERM where
On Fri, Dec 30, 2016 at 11:30:10AM -0700, Theo de Raadt wrote:
> I'm wondering if anyone doing an install/upgrade has noticed any
> behaviour changes in the last week...
>
> There's a secret diff being tested :-)
i was building from source but just tried a snapshot
is it a scheduler or librthrea
Yes, that's much better. It solves the problem, without trying to
solve other problems which don't exist.
> On Mon, Dec 26, 2016 at 04:54:54PM -0700, Theo de Raadt wrote:
> > I think programs should only block the absolutely critical things, and this
> > is overreach.
>
> Yes, blocking SIGINT an
On Mon, Dec 26, 2016 at 04:54:54PM -0700, Theo de Raadt wrote:
> I think programs should only block the absolutely critical things, and this
> is overreach.
Yes, blocking SIGINT and SIGQUIT is not clever. I thought there
were races with SIGCHLD and SIGTERM where only one process would
survive. B
I'm wondering if anyone doing an install/upgrade has noticed any
behaviour changes in the last week...
There's a secret diff being tested :-)
On Thu, Dec 29, 2016 at 09:30 +0100, Martin Pieuchot wrote:
> On 29/12/16(Thu) 01:15, Alexander Bluhm wrote:
> > On Fri, Dec 23, 2016 at 12:09:32AM +0100, Martin Pieuchot wrote:
> > > On 22/12/16(Thu) 20:45, Mike Belopuhov wrote:
> > > > I think this is what is required here. Works here, but YMMV.
As many of you will already be aware, the OpenSSL 1.1.0 release intentionally
introduced significant API changes from the previous release[0][1]. In summary,
a large number of data structures that were previously publically visible have
been made opaque, with accessor functions being added in order
On Wed, Dec 28, 2016 at 09:59:06PM +0100, Jan Stary wrote:
> Markup a forgotten keyword.
>
> Jan
>
fixed, thanks.
jmc
> Index: ntpd.conf.5
> ===
> RCS file: /cvs/src/usr.sbin/ntpd/ntpd.conf.5,v
> retrieving revision 1.33
> di
12 matches
Mail list logo