Re: vmd: alpine-virt guest, clock synchronization issue

On 10/14/2017 13:01, x9p wrote: Hi, While running Alpine-virt 3.6.2 VM guest under OpenBSD 6.1 host, i noticed the clock frequency is 2x slower on the guest machine. This can be a problem for applications that relies on accurate time. Even after sync clock with ntpd inside alpine-virt guest,

Re: A stupid question, re: xargs(1)

> On Oct 14, 2017, at 4:02 PM, Abel Abraham Camarillo Ojeda > wrote: > > find . | grep something | more filters | perl -ne 'chomp; print > "$_\0"' | xargs -0 ... Nice! *Now* can we stop talking about it?

Re: use /dev/arandom on the Linux

Hi Philipp, hi Markus, Philip Guenther wrote on Sat, Oct 14, 2017 at 12:05:55AM -0700: > On Fri, Oct 13, 2017 at 11:54 PM, Mohammad BadieZadegan > arandom entropy is better than urandom and I need arandom for better >> entropy and better speed in comparison about

vmd: alpine-virt guest, clock synchronization issue

Hi, While running Alpine-virt 3.6.2 VM guest under OpenBSD 6.1 host, i noticed the clock frequency is 2x slower on the guest machine. This can be a problem for applications that relies on accurate time. Even after sync clock with ntpd inside alpine-virt guest, it gets out-of-sync a few seconds

Re: A stupid question, re: xargs(1)

On Sat, Oct 14, 2017 at 10:26 AM, Marc Espie wrote: > the find -print0 / xargs -0 couple was designed to solve that problem > a long time ago in one specific case. I suppose the other angle to take would be the addition of a null delimiter option for other command line

Re: A stupid question, re: xargs(1)

On Sat, Oct 14, 2017 at 12:02 PM, Raul Miller wrote: > On Sat, Oct 14, 2017 at 10:26 AM, Marc Espie wrote: >> the find -print0 / xargs -0 couple was designed to solve that problem >> a long time ago in one specific case. > > I suppose the other angle to

Re: dump to remote system

On Sat, Oct 14, 2017 at 11:18 AM, Federico Giannici wrote: > I'd like to do a"dump" of a filesystem to a remote machine. > > The dump command man page says to use "-f user@host:file", but sniffing > the network traffic I have found that it tries to connect to the 514 TCP >

Re: "athn0: could not load firmware" for AR9271

Maximilian Pichler writes: > The dmesg is the same as previously (this is on the APU), except for: > athn0 at pci5 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 2 int 16 > athn0: AR9280 rev 2 (2T2R), ROM rev 22, address xx:xx:xx:xx:xx:e2 I'm debugging some issues

Re: OpenBSD 6.2 AMD64, crashed during reboot.

I had a bit of trouble upgrading my vultr account. The fix for me was updating the name of the desired kernel in /etc/boot.conf On Sat, Oct 14, 2017 at 6:27 AM, Özgür Kazancci wrote: > Hey everyone. > > I've a VPS on Vultr that was running OpenBSD 6.1 smoothly, since a

iwm fatal firmware error on - current

On 6.2 current shortly after boot iwm fails with the error: iwm0: fatal firmware error iwm0: could not remove MAC context (error 35) The device is able to initially connect get an address and connect for a few minutes. Output from ifconfig and dmesg are below. Let me know what other

Re: kernel panic i386

On Sat, Oct 14, 2017 at 6:57 AM, Krzysztof Strzeszewski wrote: > This is very interested "the kernel did non panic". panic() is an explicit call in the kernel, made when some sanity or consistency check fails. Dereferencing a bogus pointer results in a failed page fault trap

dump to remote system

I'd like to do a"dump" of a filesystem to a remote machine. The dump command man page says to use "-f user@host:file", but sniffing the network traffic I have found that it tries to connect to the 514 TCP port, the rsh protocol port. But it seems to me that rsh has been removed from OpenBSD

Re: use /dev/arandom on the Linux

On Sat, Oct 14, 2017 at 10:00 AM, Ingo Schwarze wrote: ... > RTFS is all well and good, but trying to understand your postings, > i also tried to RTFM. > > schwarze@isnote $ man urandom > man: No entry for urandom in the manual. > > This is ungood. > > So i looked at

athn0: device timeout and network hanging with AR9285

Frequently -- several times per hour when I'm actively doing stuff on my laptop, the network hangs for perhaps 30-60 seconds. This coincides with athn0 timeout messages on the console. I don't have much data to back up my claim that it feels like it's more frequent since the upgrade to 6.2, but it

use /dev/arandom on the Linux

Hi everybody, I need /dev/arandom on some Linux, How can I use /dev/arandom on the Linux Kernel OS? Which way is the fast way?

Re: use /dev/arandom on the Linux

arandom entropy is better than urandom and I need arandom for better entropy and better speed in comparison about /dev/random. On Sat, Oct 14, 2017 at 10:18 AM, Philip Guenther wrote: > On Fri, Oct 13, 2017 at 11:28 PM, Mohammad BadieZadegan < > mbzade...@gmail.com> wrote: >

Re: use /dev/arandom on the Linux

On Fri, Oct 13, 2017 at 11:54 PM, Mohammad BadieZadegan wrote: > arandom entropy is better than urandom and I need arandom for better > entropy and better speed in comparison about /dev/random. > Umm, I don't understand. /dev/arandom was an OpenBSD "innovation" that we

Re: A stupid question, re: xargs(1)

On Sat, Oct 14, 2017 at 1:08 AM, Philip Guenther wrote: > You want a version of xargs that, instead of requiring special handling for > 5 characters legal in filenames (quote, double-quote, backslash, space, tab, > newline), will be completely unable to handle exactly one of

RE: A stupid question, re: xargs(1)

"Raul Miller" wrote: > > And if I search, I can find a tremendous variety of other elaborate > approaches, including replacements for xargs. So it's not like this is > not a real issue, nor is it like this isn't something that grows new > handlings on an ongoing basis.

Re: Automatically restarting services/daemons after crash

On Sat, Oct 14, 2017 at 1:15 AM, Luke Small wrote: > I am not certain about Braille, but what I am sure of is there is no > incremental process to guessing a 64 bit datum that changes every single > execution. I'll note that in OpenBSD, stack cookies are the size of a

Re: A stupid question, re: xargs(1)

On Sat, Oct 14, 2017 at 08:44:08AM +, Raul Miller wrote: > On Sat, Oct 14, 2017 at 3:08 AM, Andreas Kusalananda Kähäri > wrote: > > find . -type f -mtime -1 \ > > -exec grep -q -E 'pattern1' {} ';' \ > > -exec shasum {} + > > That's cute, but it winds up

Re: Automatically restarting services/daemons after crash

On Fri, Oct 13, 2017 at 11:54 PM, Philip Guenther wrote: > On Fri, Oct 13, 2017 at 11:43 PM, Luke Small wrote: > >> I am not versed in operating systems as well as you, but I would think >> that stack and buffer canaries would differ from each

Re: A stupid question, re: xargs(1)

On Fri, Oct 13, 2017 at 11:52:11PM +, Raul Miller wrote: > On Fri, Oct 13, 2017 at 7:37 PM, edgar wrote: > > Perhaps a real life example of what you have been doing with xargs before > > and after your change would be helpful. > > That's tough, since when I was

Re: A stupid question, re: xargs(1)

On Sat, Oct 14, 2017 at 3:08 AM, Andreas Kusalananda Kähäri wrote: > find . -type f -mtime -1 \ > -exec grep -q -E 'pattern1' {} ';' \ > -exec shasum {} + That's cute, but it winds up spinning up a process for every file (actually, in your example, two processes

Re: kernel panic i386

I changed only name kernel :) W dniu 14.10.2017 o 01:13, Mike Larkin pisze: On Fri, Oct 13, 2017 at 09:21:37PM +0200, Krzysztof Strzeszewski wrote: Hi, When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic. Try 6.1 stock kernel and see if that works. Then at least we know if we

RE: A stupid question, re: xargs(1)

"Andreas Kusalananda Kähäri" write: > > Another thing to avoid is having too exotic filenames. Or always passing file names through vis(3) before writing them. Though that's probably not as simple as it sounds. --schaafuit.

Re: Automatically restarting services/daemons after crash

I am not versed in operating systems as well as you, but I would think that stack and buffer canaries would differ from each execution.

Re: use /dev/arandom on the Linux

On Fri, Oct 13, 2017 at 11:28 PM, Mohammad BadieZadegan wrote: > Hi everybody, I need /dev/arandom on some Linux, How can I use /dev/arandom > on the Linux Kernel OS? > Which way is the fast way? > Don't use /dev/arandom: use /dev/urandom instead. You have a program whose

Re: Automatically restarting services/daemons after crash

If that's true, then why has Theo been speaking of the brop problems, when they begin with an incremental canary discovery that becomes all but impossible to guess when it becomes a random 4 byte datum each time rather than a datum that remains the same each restart? Braille should already be

Re: Automatically restarting services/daemons after crash

On Sat, Oct 14, 2017 at 12:49 AM, Luke Small wrote: > If that's true, then why has Theo been speaking of the brop problems, > when they begin with an incremental canary discovery that becomes all but > impossible to guess when it becomes a random 4 byte datum each time

Re: Automatically restarting services/daemons after crash

I am not certain about Braille, but what I am sure of is there is no incremental process to guessing a 64 bit datum that changes every single execution. I typically don't state a fact unless I am willing to die if I am incorrect. At least

Re: Automatically restarting services/daemons after crash

On Fri, Oct 13, 2017 at 11:43 PM, Luke Small wrote: > I am not versed in operating systems as well as you, but I would think > that stack and buffer canaries would differ from each execution. > I suggest you examine the source, OR BETTER, examine actual processes under a

Re: Looking for libraries

On 2017-10-14, Nigel Taylor wrote: > On 10/13/17 22:09, Per-Olov Sjöholm wrote: >> Hi >> >> I just upgraded to 6.2… >> >> Anyone that knows what packages I can find the following libs in: >> libpthread.so.22.0 >> libc.so.88.0 >> libm.so.9.0 >> >> I used this

Re: The dlopen manual lacks RTLD_TRACE info

On Wed, Oct 4, 2017 at 5:59 PM, Nan Xiao wrote: > > I find the ldd program actually uses "RTLD_TRACE" when calling > "dlopen": > dlhandle = dlopen(buf, RTLD_TRACE); > > While the manual (https://man.openbsd.org/dlopen.3) seems doesn't > provide introduction of

Re: kernel panic i386

On Fri, Oct 13, 2017 at 12:21 PM, Krzysztof Strzeszewski wrote: > When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic. > It's unfortunate that no one has submitted to dm...@openbsd.org the dmesg from that hardware since February 2016. Please consider doing so every

X on OpenBSD security question

Any comments on the security of using X in OpenBSD would be much appreciated, when running X with machdep.allowaperture=0 , or higher. This is with background of the general buzz that X is terribly unsecure and anyone security-minded not even should touch it with a stick, e.g. a userland X

Re: A stupid question, re: xargs(1)

As Theo said already, the main issue there is that it's totally non-standard, so you end up writing scripts that won't work anywhere but on OpenBSD. The problem you're trying to solve is quoting in shell. It's basically broken by design. There will always be fun patterns in names that do various

Re: kernel panic i386

This is very interested "the kernel did non panic". Where is memcmp in sys? When I run bsd.rd end mount filesystem I can't find memcmp. http://wklej.org/hash/e5591ccc88f/ . . . cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8

Security question / idea

Hi misc@, In playing around with Libreboot and Coreboot, my belief that physical access to the hardware really ups an attacker’s ability to win against most security has been massively reinforced. For example, someone with enough practice could take my Thinkpad T500 apart, force flash the BIOS

Re: Security question / idea

> On 14. Oct 2017, at 16:26, Bryan C. Everly wrote: > > Hi misc@, > > In playing around with Libreboot and Coreboot, my belief that physical > access to the hardware really ups an attacker’s ability to win against most > security has been massively reinforced. For