Ted Unangst wrote:
> Dariusz Sendkowski wrote:
> > Yes, it does.
> >
> > I extracted 'unveilcommands' function from doas.c and put it into a
> > standalone program to run it.
> > It turned out the result was the same as in doas command. When I disable
> > unveil, then it works fine.
>
> This
> The SiFive FU540 runs FreeBSD.
>
> https://www.sifive.com/boards/hifive-unleashed
>
> https://fosdem.org/2019/schedule/event/testing_freebsd_risc_v5/
Very cool!
Subject/Topic: New York Times: Microwave Weapons Are Prime Suspect in
Ills of U.S. Embassy Workers
This New York Times newspaper article is very welcome and being held
dear by millions of Targeted Individuals (TIs) all over the world,
including Mr. Turritopsis Dohrnii Teo En Ming, who is based in
Dariusz Sendkowski wrote:
> Yes, it does.
>
> I extracted 'unveilcommands' function from doas.c and put it into a
> standalone program to run it.
> It turned out the result was the same as in doas command. When I disable
> unveil, then it works fine.
This diff should fix the problem.
Index:
I found the "-T" (trace) flag to smtpd(8), and it gives me this, which AFAICT
confirms my suspicions:
[...]
rule #2 matched: match from src allowed-hosts for any => translate
lookup: lookup "athom...@athompso.net" as ALIAS in table
static:translations -> 0
lookup:
As it turns out, no, that doesn't work.
Trying to fix up broken sender mail domain-parts only simply gets me a "5.2.4
Mailing list expansion problem" error, with no debug output to suggest why.
In this test case, my translations map had:
@bad.athompso.net @good.athompso.net
in it.
Yes, it does.
I extracted 'unveilcommands' function from doas.c and put it into a
standalone program to run it.
It turned out the result was the same as in doas command. When I disable
unveil, then it works fine.
niedz., 20 sty 2019 o 22:31 Ted Unangst napisał(a):
> Dariusz Sendkowski
Dariusz Sendkowski wrote:
> I investigated the problem a little more and found, that when there is a
> non-existent directory entry in my PATH, the problem occurs. If all of the
> directories from my PATH exist, then it works fine.
To help isolate the problem, if you disable unveil, does it work?
I investigated the problem a little more and found, that when there is a
non-existent directory entry in my PATH, the problem occurs. If all of the
directories from my PATH exist, then it works fine.
niedz., 20 sty 2019 o 12:00 Dariusz Sendkowski
napisał(a):
> This is -stable 6.4.
>
If someone is interested:
https://github.com/kolargol/apu2_firmware
of course for testing bins, OpenBSD reports IBPB:
cpu0:
On Sun, Jan 20, 2019, 21:53 Unfortunately it looks like there are no current production mainstream
> devices which do any better (unless OpenBSD has figured out how to replace
> the Pine64 firmware), leaving niche devices based on e.g OpenPOWER and RISC
> V.
>
> Neither of which fit in hand
> On January 19, 2019 at 6:17 PM Mihai Popescu wrote:
> Since it looks to me that you missed the point, here is it: most
> people on this list, devs mostly are not on vacation ...
> Ask precisely!
Ok, thanks for pointing that out.
> On January 19, 2019 at 11:34 PM Karel Gardas wrote:
> Well, with RPiX you completely missed the target I'm afriad. If I'm
> correct, then whole SoC is booted on the side of video processor which
> loads some blobs into it, run ThreadX OS and then boots ARMv8
> bootloader on ARM core. There
Hi Luca,
Luca Franchini wrote on Sun, Jan 20, 2019 at 03:41:46PM +0100:
> I got an error while running this:
>
> amidatacyber730:~$ python3.6
> Python 3.6.6 (default, Oct 11 2018, 12:39:19)
> [GCC 4.2.1 Compatible OpenBSD Clang 6.0.0 (tags/RELEASE_600/final)] on o
> Type "help", "copyright",
Hi all,
I got an error while running this:
amidatacyber730:~$ python3.6
Python 3.6.6 (default, Oct 11 2018, 12:39:19)
[GCC 4.2.1 Compatible OpenBSD Clang 6.0.0 (tags/RELEASE_600/final)] on o
Type "help", "copyright", "credits" or "license" for more information.
>>> import locale
>>>
This is -stable 6.4.
doas.conf:
permit nopass myuser as root
On Sun, 20 Jan 2019 at 11:50, Hiltjo Posthuma
wrote:
> On Sun, Jan 20, 2019 at 11:15:38AM +0100, Dariusz Sendkowski wrote:
> > Hi,
> >
> > Calling 'doas' in a loop makes the machine hang.
> > I guess this is not an expected
On Sun, Jan 20, 2019 at 11:15:38AM +0100, Dariusz Sendkowski wrote:
> Hi,
>
> Calling 'doas' in a loop makes the machine hang.
> I guess this is not an expected behavior.
> It can be checked by executing the following simple bash script:
>
> for i in {0..2}
> do
> doas ls some_dir
> done
>
Hi,
Calling 'doas' in a loop makes the machine hang.
I guess this is not an expected behavior.
It can be checked by executing the following simple bash script:
for i in {0..2}
do
doas ls some_dir
done
I have run it on three different machines and the result is the same on
each of them.
18 matches
Mail list logo
