From: "Nelson H. F. Beebe"
Date: Fri, 18 Oct 2019 07:39:26 -0600
> Has anyone looked into the problem of enumerating packages that are
> installed in the /usr/local tree that actually NEED simultaneous write
> and execute access?
You can find that as below:
$ grep -rHI USE_WXNEEDED /usr/ports/
Jeremie Courreges-Anglas(j...@wxcvbn.org) on 2019.10.19 16:01:45 +0200:
> On Sat, Oct 19 2019, "Theo de Raadt" wrote:
> > Jeremie Courreges-Anglas wrote:
> >
> >> On Sat, Oct 19 2019, Claudio Jeker wrote:
> >> > bgpd supports up to 255 byte shutdown communications. So the manpage is
> >> > not t
Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.10.19 11:07:28 +0200:
> bgpd supports up to 255 byte shutdown communications. So the manpage is
> not telling the truth. Also I don't think it is helpful to mention the
> limit at all. bgpctl will exit with 'shutdown reason too long' if the text
> is
Hello tech@,
I have a question (or maybe a suggestion) about vmm(4).
I'm writing a small additional feature to sys/arch/amd64/amd64/vmm.c
and found a seemingly unneeded vmclear() at the end of
vcpu_readregs_vmx(). This function didn't seem to affect VM state at
first glance because, obviously, it
There has been an update to
https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-https-tal-05
Which permits comments in the tal files. I proposed this at nanog yvr
as something which might help the arin tal hangup.
queue_add_tal(int fd, struct entityq *q, const char *file, size_t *eid)
{
Change the way TAL files are loaded into rpki-client. Instead of passing
the filename to the parser process and have that one open the file. Do it
in the main process and pass the buffer to the parser. The benefit of this
is that TAL files are not read by the parser and therefor the unveil can
be l
