Re: On blindly running code

2019-10-18 Thread chohag
Frank Beuth writes: > On Fri, Oct 18, 2019 at 11:54:18AM +0100, cho...@jtan.com wrote: > >Virtualisation is not a panacea. I have managed to achieve data loss through > >destructi > ve actions taken within a "safe" virtualised sandbox. > > How did you manage that feat? Basically assuming "safe"

tar keeps writing after pipe has been closed

2019-10-18 Thread Alfred Morgan
Why does tar not stop? It immediately shows the first line and then sits there for over 3 seconds. $ time tar tzf ports.tar.gz | head -1 ports 0m03.29s real 0m04.03s user 0m01.00s system -alfred

Re: NPPPD Server behind a firewall

2019-10-18 Thread Damian McGuckin
On Wed, 16 Oct 2019, Stuart Henderson wrote: I would srongly recommend switching to IKEv2 if you can, it is far easier to come up with a config that still gives decent crypto with mixed client platforms. (Internal client on Apple OS and non-ancient Windows - strongswan on Android/Linux). I

Re: Strong Host Model in OpenBSD network stack

2019-10-18 Thread Claudio Jeker
On Thu, Oct 17, 2019 at 09:50:28PM +0200, Bastian Kanbach wrote: > Hello, > > recently I was performing some checks that relate to the "Strong Host > Model" and "Weak Host Model", and I noticed that OpenBSD was behaving > different than I expected. I always assumed that the network stack of >

Re: Strong Host Model in OpenBSD network stack

2019-10-18 Thread Claudio Jeker
On Fri, Oct 18, 2019 at 07:21:42AM +0200, Remi Locherer wrote: > On Thu, Oct 17, 2019 at 10:33:41PM -0600, Theo de Raadt wrote: > > > Setting net.inet.ip.check_interface=1 on FreeBSD stopped any ICMP Echo > > > replies immediately. > > > > > > On NetBSD I set net.inet.ip.checkinterface=1 and it

remaining references to xman (RIP)

2019-10-18 Thread Alfred Morgan
Here are some leftover references to xman I found after the upgrade to 6.6. Mostly examples, mentions, and configs. I think the most significant one is the missing man page that xmore references. /usr/X11R6/man/man1/appres.1: % appres Xman.TopLevelShell.Form xman.topBox.form

Re: xauth segfault

2019-10-18 Thread chohag
Well it seems I was wrong and this is a common-or-garden bug. Specifically, from xauth/gethost.c, starting at line 199: #ifdef HAVE_STRLCPY strlcpy(path, fulldpyname, sizeof(path)); #else strncpy(path, fulldpyname, sizeof(path)); path[sizeof(path) - 1] = '\0';

On blindly running code

2019-10-18 Thread chohag
With regards to recent discussion, here is a little anecdote that came out of the 6.5 to 6.6 upgrade. On one machine I run bitlbee, an IRC:IM gateway. After upgrading all the ports it left suggestions in the form of copy pasta commands to run to complete the upgrade process, as it does. One of

Re: On blindly running code

2019-10-18 Thread chohag
Shane Lazarus writes: > Heya > > My own experience agrees with you with regards to any system in production. > > However, it is also my experience that nothing demonstrates the > difference between what should happen and what actually occurs better > than running the code and seeing the aftermath.

Re: Encrypting my keydisk

2019-10-18 Thread Jan Stary
> > On Wednesday, October 16, 2019 11:06 PM, List wrote: > >> I was wondering if there is a reason for the lack of keydisk encryption. $ man bioctl # bioctl -h -v -c C ...

mpd: failed to open default sndio device

2019-10-18 Thread Кирилл
Hello. After install mpd: $ mpc play Antimatter - Over Your Shoulder [paused] #1/7 0:00/4:41 (0%) volume:100% repeat: off random: off single: off consume: off ERROR: Failed to open "sndio output" (sndio); Failed to open default sndio device dmesg: https://pastebin.com/y5A81Cqh

Requesting vi tips

2019-10-18 Thread chohag
OK this has started to get on my nerves now. I use vi to enter emails despite using evil emacs for development and other general editing. Rather than linking them together (they're on seperate machines) to enter emails in emacs I'd rather figure out something interesting about vi. At the moment

Re: remaining references to xman (RIP)

2019-10-18 Thread Ingo Schwarze
Hi Alfred, Alfred Morgan wrote on Thu, Oct 17, 2019 at 11:49:35PM -0700: > Here are some leftover references to xman > I found after the upgrade to 6.6. [...] > /usr/X11R6/man/man1/appres.1: > /usr/X11R6/man/man1/editres.1: > /usr/X11R6/man/man1/fvwm.1: > /usr/X11R6/man/man1/xmore.1: We'll do

Re: On blindly running code

2019-10-18 Thread Frank Beuth
On Fri, Oct 18, 2019 at 11:54:18AM +0100, cho...@jtan.com wrote: Virtualisation is not a panacea. I have managed to achieve data loss through destructive actions taken within a "safe" virtualised sandbox. How did you manage that feat? If the only thing that can demonstrate what a piece of

Re: On blindly running code

2019-10-18 Thread Shane Lazarus
Heya My own experience agrees with you with regards to any system in production. However, it is also my experience that nothing demonstrates the difference between what should happen and what actually occurs better than running the code and seeing the aftermath. Thankfully, virtualisation makes

Re: Softraid data recovery

2019-10-18 Thread Steven Surdock
> -Original Message- > From: Aaron Mason > Sent: Monday, October 14, 2019 7:13 PM > To: Steven Surdock > Cc: misc@openbsd.org > Subject: Re: Softraid data recovery > > On Tue, Oct 15, 2019 at 7:34 AM Steven Surdock net.com> wrote: > > ... > > > > How can I recover as much data as

Re: Requesting vi tips

2019-10-18 Thread chohag
Claudio Jeker writes: > set wl=72 will limit the line lenght to around 72. Additionally you > can use !fmt with movement chars to reformat sections. I use !{fmt > or {!}fmt frequently to reformat the paragraph I'm in. I didn't know [how] ! took movement commands. Thanks. I'll have a play with

Re: Requesting vi tips

2019-10-18 Thread adr
I didn't know [how] ! took movement commands. Thanks. I'll have a play with that one. It's not quite M-q (it's M not C) but I'm using vi after all. Matthew The entire man page is 1332 widely-spaced-out lines of clear, simple formated text. Including comments. Read the damn thing. You see, is

Re: On blindly running code

2019-10-18 Thread Frank Beuth
On Fri, Oct 18, 2019 at 01:20:33PM +0100, cho...@jtan.com wrote: Frank Beuth writes: On Fri, Oct 18, 2019 at 11:54:18AM +0100, cho...@jtan.com wrote: >Virtualisation is not a panacea. I have managed to achieve data loss through destructi ve actions taken within a "safe" virtualised sandbox.

Re: Requesting vi tips

2019-10-18 Thread Claudio Jeker
On Fri, Oct 18, 2019 at 03:12:37PM +0100, cho...@jtan.com wrote: > OK this has started to get on my nerves now. > > I use vi to enter emails despite using evil emacs for development and > other general editing. Rather than linking them together (they're on > seperate machines) to enter emails in

Re: On blindly running code

2019-10-18 Thread Raul Miller
On Fri, Oct 18, 2019 at 8:23 AM wrote: > That's not to even start on the fact that it's little more than process > switching and virtual memory on steroids, so the extra seperation on top of > what the OS already provides is little more than smoke and mirrors. My mental model of computer

Re: Requesting vi tips

2019-10-18 Thread Christian Weisgerber
On 2019-10-18, cho...@jtan.com wrote: > I didn't know [how] ! took movement commands. Thanks. I'll have a play > with that one. > > It's not quite M-q (it's M not C) but I'm using vi after all. Since 'q' is unused in nvi, I have this in my .nexrc: map q !}fmt Close enough to emacs's M-q. --

Re: Requesting vi tips

2019-10-18 Thread Raf Czlonka
On Fri, Oct 18, 2019 at 03:39:41PM BST, cho...@jtan.com wrote: > Raf Czlonka writes: > > On Fri, Oct 18, 2019 at 03:12:37PM BST, cho...@jtan.com wrote: > > Is this what you had in mind? > > > > set editor="EXINIT='set wraplen=72' /usr/bin/vi" I forgot to mention - this is the line in my

Re: Requesting vi tips

2019-10-18 Thread chohag
adr writes: > You see, is so easy to be an asshole. You're telling me? I know I'm not particularly active on OpenBSD's mailing lists but I've certainly been around. For the record, I have a finite amount of neurons with a correspondingly finite amount of synapses. There is only so much even I

Re: Requesting vi tips

2019-10-18 Thread paul wisehart
On Fri, Oct 18, 2019 at 03:12:37PM +0100, cho...@jtan.com wrote: > but I wonder if there's something that can correctly parse the > whole email and format the entire thing en masse :%!fmt -s

Mugs

2019-10-18 Thread Peter J. Philipp
Hi, In the past I've bought mugs from OpenBSDStore.com. The site now points to the main OpenBSD.org website and the DNS SOA indicates it may have been doing so for 7 days. Is there a story to this? Where should we get fan items in the future? Regards, -peter

Re: Requesting vi tips

2019-10-18 Thread Frank Beuth
On Fri, Oct 18, 2019 at 03:12:37PM +0100, cho...@jtan.com wrote: Alternatively is there something that would make vi do it on the fly, or something akin to emacs' C-q or vim's gq. Although I appreciate the fact that vi doesn't try to be clever. 1) select all text in visual mode (e.g with V,

Re: Requesting vi tips

2019-10-18 Thread adr
On Fri, 18 Oct 2019, cho...@jtan.com wrote: For the record, I have a finite amount of neurons with a correspondingly finite amount of synapses. There is only so much even I can hold in my head. Asking actual humans for access to the particular minutiae they happen to have itemised to the nth

Re: Requesting vi tips

2019-10-18 Thread Raf Czlonka
On Fri, Oct 18, 2019 at 03:12:37PM BST, cho...@jtan.com wrote: > OK this has started to get on my nerves now. > > I use vi to enter emails despite using evil emacs for development and > other general editing. Rather than linking them together (they're on > seperate machines) to enter emails in

about vim objects (Re: Requesting vi tips)

2019-10-18 Thread Marc Chantreux
hello, > I didn't know [how] ! took movement commands. Thanks. I'll have a play > with that one. almost related: in addition to the motions, vim has a notion of objects :h objects so you can easily filter a complete paragraph with !ap fmt -w72 in visual mode, you can select

vi(1) and ranges

2019-10-18 Thread adr
Going through the vi man page (and the one of editors/nvi) looking for some hint about '|' in maps some days before, I noticed that the ranges aren't described. If the developers are interested I can add the description from the nvi reference manual, next to the description of count, motion,

Re: Requesting vi tips

2019-10-18 Thread chohag
Raf Czlonka writes: > On Fri, Oct 18, 2019 at 03:12:37PM BST, cho...@jtan.com wrote: > Is this what you had in mind? > > set editor="EXINIT='set wraplen=72' /usr/bin/vi" I'm not sure that I'm happy with it doing it mid-insert. I'd prefer an explicit action or insert mode itself being

Re: On blindly running code

2019-10-18 Thread chohag
Raul Miller writes: > My mental model of computer security often approximates putting a bank > vault door on a picket fence (and maybe setting up a sniper to stop > people from climbing over the door). But in layers. One of them will work right? It's defense^Wobscurity in depth. > Doesn't mean

Re: Requesting vi tips

2019-10-18 Thread Nam Nguyen
On 2019-10-18, Christian Weisgerber wrote: > On 2019-10-18, cho...@jtan.com wrote: > >> I didn't know [how] ! took movement commands. Thanks. I'll have a play >> with that one. >> >> It's not quite M-q (it's M not C) but I'm using vi after all. > > Since 'q' is unused in nvi, I have this in my

Re: mpd: failed to open default sndio device

2019-10-18 Thread Alexandre Ratchov
On Fri, Oct 18, 2019 at 02:34:48PM +0300, Кирилл wrote: > Hello. > After install mpd: > $ mpc play > Antimatter - Over Your Shoulder > [paused] #1/7 0:00/4:41 (0%) > volume:100% repeat: off random: off single: off consume: off > ERROR: Failed to open "sndio output" (sndio); Failed to

Re: vi(1) and ranges

2019-10-18 Thread adr
I for one am currently not interested in looking at your work (assuming there's going to be any) No, there is not going to be any. I don't like what you are encouraging. Bye.

Re: Requesting vi tips

2019-10-18 Thread Christian Weisgerber
On 2019-10-18, Nam Nguyen wrote: >> Since 'q' is unused in nvi, I have this in my .nexrc: >> map q !}fmt > > I just wanted to add that you can Ctrl-v Enter to produce the ^M at the end. > This way it inputs and executes the command for you. > > It could be like this if you want it to press

Re: vi(1) and ranges

2019-10-18 Thread Martijn van Duren
On 10/18/19 7:23 PM, adr wrote: > Going through the vi man page (and the one of editors/nvi) looking > for some hint about '|' in maps some days before, I noticed that > the ranges aren't described. > > If the developers are interested I can add the description from > the nvi reference manual,

Nobody said it yet...

2019-10-18 Thread STeve Andre'
Happy birthday to OpenBSD!

Re: Nobody said it yet...

2019-10-18 Thread jungle Boogie
On Fri, Oct 18, 2019, 6:22 PM STeve Andre' wrote: > Happy birthday to OpenBSD! > Here, here. Have a great weekend to all the developers, contributors, and users of the project.

Re: Nobody said it yet...

2019-10-18 Thread Theo de Raadt
STeve Andre' wrote: > Happy birthday to OpenBSD! It forgot. In my mind, I've been at this a lot longer since I was also initial NetBSD.

Thank you OpenBSD!

2019-10-18 Thread zap
Because of your high security standards, my distro has adopted LibreSSL and Xenocara. In the future it plans to also adopt sndio instead of that pulse garbage. I hope OpenBSD lasts a very, long, long time, not just for this, but because you guys take security very seriously.  

Re: Nobody said it yet...

2019-10-18 Thread Manuel Solis
Better late than never, Happy birthday and all the appreciation to the developers and community of this amazing OpenBSD’s culture and philosophy around it! > El 18 oct 2019, a la(s) 21:03, Theo de Raadt escribió: > > STeve Andre' wrote: > >> Happy birthday to OpenBSD! > > It forgot. > >