Re: IPSec Flow and SA to unexpected subnet

On 2017-11-27, Paul Suh wrote: > Note the two starred flows that are not listed in my ipsec.conf > configuration. The 172.16.0.0/16 subnet does exist on the Sonicwall end, and > I'm pretty sure that the Sonicwall is requesting that a flow be set up for > that subnet.

Re: Testing IKEv2 with Android devices

On 2017-11-26, C. L. Martinez wrote: > > Ok, it is seems the prolem is that iked(8) does not know how to perform > Diffie-Hellman group negotiation: > > https://marc.info/?l=openbsd-tech=151136800328145=2 > > Am I correct? What is the current status for Tim's fix?

Re: MacOS High Sierra. Anyone can login as "root" with empty password

On 2017-11-29, Ilya Abimael wrote: > The question: Would it be a good thing to MANDATORY disable any passwordless > login? That would be annoying for ssh.

Re: IPSec Flow and SA to unexpected subnet

On 2017-11-27, Tobias Urdin wrote: > Had the same problem with a shitty Netgear on the other end. > > OpenBSD happily accepted the flow with a 0/0 from forcing all traffic to > the destination over that tunnel. Yes, I once found the hard way that you can do this from

Re: MacOS High Sierra. Anyone can login as "root" with empty password

Am 29. November 2017 08:36:27 MEZ schrieb Ilya Abimael : >Hello, > >https://news.ycombinator.com/item?id=15800676 > >The mentioned news is _NOT_ OpenBSD related. It just got something in >my mind to ask: You forgot a important detail. The root user is there in all Mac

Re: Testing IKEv2 with Android devices

On Wed, Nov 29, 2017 at 9:33 AM, Stuart Henderson wrote: > On 2017-11-26, C. L. Martinez wrote: >> >> Ok, it is seems the prolem is that iked(8) does not know how to perform >> Diffie-Hellman group negotiation: >> >>

sshd hangs when ldap server is offline

Hi, We have been trying to play around with the login_ldap package and after we have configured login.conf, ypldap.conf and added portmap_flags=YES, ypldap_flags=“”, and ypbind_flags=“” to rc.conf.local we have see an issue. If the ldap server is offline, sshd is not able to restart or even

Re: Odd problem with interfaces

On Wed, Nov 29, 2017 at 09:56:38AM -0500, Rupert Gallagher wrote: > I ran out of ideas on the following problem. > > An obsd server has tree ethernet interfaces, each with its own IP address: > > cat /etc/hostname.* > inet 192.168.1.2 255.255.255.0 192.168.1.255 mtu 9014 description "em0: >

Odd problem with interfaces

I ran out of ideas on the following problem. An obsd server has tree ethernet interfaces, each with its own IP address: > cat /etc/hostname.* inet 192.168.1.2 255.255.255.0 192.168.1.255 mtu 9014 description "em0: MODEM/ROUTER" inet 192.168.1.3 255.255.255.0 192.168.1.255 mtu 9014 description

Re: xterm(1) changing UTF-8 characters when copy-pasting?

Hi Philippe, Philippe Meunier wrote on Wed, Nov 29, 2017 at 09:11:38AM -0500: > I've noticed something unexpected when copy-pasting UTF-8 characters in > xterm: xterm seems to change some of the characters into something > different but visually similar. Here's an example (using ksh): > > $

Re: xterm(1) changing UTF-8 characters when copy-pasting?

Ingo Schwarze wrote: >Philippe Meunier wrote: >> $ ls >> Thérèse > >That's a bad idea. Do not use non-ASCII bytes in file names. That's a nice thought but in practice I have some files on that machine with names written in French, Thai, Chinese, Korean, and Japanese, and for some of these

Re: obligatory leaving letter

On Tue, 28 Nov 2017, leo_...@volny.cz wrote: As dmr often pointed out (though perhaps not quite in the terms that I will use here), UNIX is about community. Or about simplicity? UNIX as the opposite to MULTICS? And this is the impression I get when I read Ritchies and Thompson paper "The

Re: xterm(1) changing UTF-8 characters when copy-pasting?

Hi Philippe, Philippe Meunier wrote on Wed, Nov 29, 2017 at 11:35:59AM -0500: > Ingo Schwarze wrote: >> Philippe Meunier wrote: >>> $ ls >>> Thérèse >> That's a bad idea. Do not use non-ASCII bytes in file names. > That's a nice thought but in practice I have some files on that machine >

Re: xterm(1) changing UTF-8 characters when copy-pasting?

Ingo Schwarze writes: > That's a bad idea. Do not use non-ASCII bytes in file names. > You are in for all kinds of trouble. I don't agree. In a situation where a single user will be accessing files, you can use whatever naming scheme you like. UTF-8 works exactly how you would expect: the

xterm(1) changing UTF-8 characters when copy-pasting?

Hello, I've noticed something unexpected when copy-pasting UTF-8 characters in xterm: xterm seems to change some of the characters into something different but visually similar. Here's an example (using ksh): $ uname -a OpenBSD foo.my.domain 6.1 GENERIC#19 i386 $ ls Thérèse $ ls | od -c

Re: Odd problem with interfaces

Aargh! What a day https://media.giphy.com/media/AYcqmj0cUar9S/giphy.gif Sent from ProtonMail Mobile On Wed, Nov 29, 2017 at 16:13, Jiri B wrote: > On Wed, Nov 29, 2017 at 09:56:38AM -0500, Rupert Gallagher wrote: > I ran out > of ideas on the following problem. > > An

openbsd 6.2 current on lenovo miix 310

Hi, for anyone whos interested in these tablet+keyboad things here are the facts about openbsd 6.2 current on the lenovo miix 310. forgot to try apm -A ... will do next time tldr; - installation was done to a usb thumb drive (it's not my device..) - Installation works as usual (secureboot

Re: Odd problem with interfaces

https://goo.gl/images/eEeb6 Sent from ProtonMail Mobile On Wed, Nov 29, 2017 at 16:13, Jiri B wrote: > On Wed, Nov 29, 2017 at 09:56:38AM -0500, Rupert Gallagher wrote: > I ran out > of ideas on the following problem. > > An obsd server has tree ethernet > interfaces, each

Re: obligatory leaving letter

On Wed, Nov 29, 2017 at 12:17 AM, Jay Williams wrote: > As a new user to OpenBSD, who is trying to learn as much as I can, seeing a > message like this is very disheartening. OpenBSD's security focus and passion > for clean, minimal and secure code is something that the world

Re: xterm(1) changing UTF-8 characters when copy-pasting?

Anthony J. Bentley wrote: > precompose (class Precompose) Thanks! That makes xterm work (almost) as expected: $ ls Thérèse $ ls | od -c 000T h e 314 201 r e 314 200 s e \n 014 $ cp Thérèse Thérèse cp: Thérèse and Thérèse are identical

OpenBSD Puffy Stickers

I like putting stickers on my laptop, but alas after searching high and low over the internet I wasn't able to find any good OpenBSD stickers So, I got a few printed up myself at StickerMule so now all of my laptops and even my car can show support for OpenBSD. That being said, I have 7 extra

Re: STYLE: whitespace at end of input line

> 3. If you think the trailing blanks really matter for users > and commonly occur in practice, change the tool itself to > write a dedicated character at line ends to show where the > end of each line is. Of course, that would be a user interface > change for the tool. Right,

Re: obligatory leaving letter

As a new user to OpenBSD, who is trying to learn as much as I can, seeing a message like this is very disheartening. OpenBSD's security focus and passion for clean, minimal and secure code is something that the world definitely needs. Despite the worldwide trend, especially here in the USA, I

Re: obligatory leaving letter

Hi Jay, Jay Williams wrote on Tue, Nov 28, 2017 at 05:17:05PM -0600: > As a new user to OpenBSD, who is trying to learn as much as I can, > seeing a message like this is very disheartening. Please do not worry about this particular case. The user who wrote this message contributed almost

Re: STYLE: whitespace at end of input line

Jan Stary writes: > The offending portion is: > > .Bd -literal > $ ecurve 7 0 3 > > * * > * * >** > * * >** >** > .Ed > > I can just delete the trailing whitespace and the reader will see the same, > but the whitespace actually has a meaning

snmpd high memory page fault / cpu usage and high latency

Hi List, i've a default snmpd.conf. When i starting snmpd then the page fault jumps to 38000: procsmemory pagediskstraps cpu r b wavm fre flt re pi po fr sr sd0 sd1 int sys cs us sy id 1 1 0 575124 60937927 0 0 0 0

STYLE: whitespace at end of input line

Hi Ingo, the manpage below does not go through mandoc -Tlint -Wstyle, because mandoc -Tlint -Wstyle *.1 mandoc: ecurve.1:48:1: STYLE: whitespace at end of input line mandoc: ecurve.1:49:7: STYLE: whitespace at end of input line mandoc: ecurve.1:50:7: STYLE: whitespace at end of input

Re: xterm(1) changing UTF-8 characters when copy-pasting?

On Wed, Nov 29, 2017 at 07:05:05PM +0100, Ingo Schwarze wrote: > Anthony J. Bentley wrote on Wed, Nov 29, 2017 at 10:29:28AM -0700: > > The only unexpected thing here is xterm doing these transformations > > without asking. > > I think i would support a diff to fix that Seconded. The current

Re: xterm(1) changing UTF-8 characters when copy-pasting?

Hi Anthony, Anthony J. Bentley wrote on Wed, Nov 29, 2017 at 10:29:28AM -0700: > Ingo Schwarze writes: >> That's a bad idea. Do not use non-ASCII bytes in file names. >> You are in for all kinds of trouble. > I don't agree. In a situation where a single user will be accessing > files, That's

Re: STYLE: whitespace at end of input line

Hi Jan, Jan Stary wrote on Wed, Nov 29, 2017 at 09:05:48PM +0100: > the manpage below does not go through mandoc -Tlint -Wstyle, because > > mandoc -Tlint -Wstyle *.1 > mandoc: ecurve.1:48:1: STYLE: whitespace at end of input line > mandoc: ecurve.1:49:7: STYLE: whitespace at end of input