Thanks, fixed.
On 2023/11/20 22:06, Alexander Bluhm wrote:
> This breaks iperf3 in my setup.
>
> root@ot50:.../~# iperf3 -sD
> Abort trap (core dumped)
>
> iperf3[72726]: pledge "proc", syscall 2
>
> Program terminated with signal SIGABRT, Aborted.
> #0 _thread_sys_fork () at /tmp/-:2
> 2
This breaks iperf3 in my setup.
root@ot50:.../~# iperf3 -sD
Abort trap (core dumped)
iperf3[72726]: pledge "proc", syscall 2
Program terminated with signal SIGABRT, Aborted.
#0 _thread_sys_fork () at /tmp/-:2
2 /tmp/-: No such file or directory.
(gdb) bt
#0 _thread_sys_fork () at
...also as was as syscalls, socket options could do with checking over too.
If everything is in order then there's not much point adding a configure
flag really, just check for pledge
--
Sent from a phone, apologies for poor formatting.
On 21 October 2023 19:01:33 Stuart Henderson wrote:
It hasn't been properly reviewed to check if there are any syscalls which
aren't covered by the pledge. I found the diskfile one which you missed,
but haven't checked over nm output to look for more.
--
Sent from a phone, apologies for poor formatting.
On 21 October 2023 18:57:55 Mikhail
On Sat, Oct 21, 2023 at 08:57:33PM +0300, Mikhail wrote:
> On Sat, Oct 21, 2023 at 06:38:57PM +0100, Stuart Henderson wrote:
> > Err, sending that upstream is a bit premature.
>
> Reasons? It works fine in my testing, also it's enabled only with
> --enable-openbsd-sandbox, so if something arise
On Sat, Oct 21, 2023 at 06:38:57PM +0100, Stuart Henderson wrote:
> Err, sending that upstream is a bit premature.
Reasons? It works fine in my testing, also it's enabled only with
--enable-openbsd-sandbox, so if something arise it's very easy for the
users to check without this code. And during
Err, sending that upstream is a bit premature.
--
Sent from a phone, apologies for poor formatting.
On 21 October 2023 15:53:34 Mikhail wrote:
On Wed, Oct 18, 2023 at 10:28:47PM +0100, Stuart Henderson wrote:
On 2023/10/18 22:19, Mikhail wrote:
> [cc'ing maintainer]
>
> Inlined patch
On Wed, Oct 18, 2023 at 10:28:47PM +0100, Stuart Henderson wrote:
> On 2023/10/18 22:19, Mikhail wrote:
> > [cc'ing maintainer]
> >
> > Inlined patch updates iperf3 to 3.15 (3 bug fixes, details here -
> > https://github.com/esnet/iperf/releases/tag/3.15).
> >
> > I run iperf on public server
lteo, are you still interested in maintaining iperf3?
On 2023/10/18 22:28, Stuart Henderson wrote:
> On 2023/10/18 22:19, Mikhail wrote:
> > [cc'ing maintainer]
> >
> > Inlined patch updates iperf3 to 3.15 (3 bug fixes, details here -
> > https://github.com/esnet/iperf/releases/tag/3.15).
> >
>
On 2023/10/18 22:19, Mikhail wrote:
> [cc'ing maintainer]
>
> Inlined patch updates iperf3 to 3.15 (3 bug fixes, details here -
> https://github.com/esnet/iperf/releases/tag/3.15).
>
> I run iperf on public server with unfirewalled ports, so I'd like it to
> be pledged/unveiled, -I and --logfile
[cc'ing maintainer]
Inlined patch updates iperf3 to 3.15 (3 bug fixes, details here -
https://github.com/esnet/iperf/releases/tag/3.15).
I run iperf on public server with unfirewalled ports, so I'd like it to
be pledged/unveiled, -I and --logfile options are working fine.
Probably we could drop
11 matches
Mail list logo
