Re: httpd and Curve25519 (X25519)

> `tls ecdhe "X25519"` gives the OK to the configuration, but the site then > fails to load in Chromium 58.0.3029.96 or Firefox 53.0.2, which should both > have X25519 support. A little more context. `$ doas httpd -n` and `$ doas rcctl reload httpd` give the OK with either `tls ecdhe

full disk encryption "unknown error" on current

Hi, I followed the FAQ for encrypting external disks, but unfortunately it's failing. I'm trying to encrypt a 32Tb raid 6 drive on a lsi 9265-8i with 8 x 6Tb drives and it's failing with an "unknown error". I was able to encrypt the 256Gb system disk without error during installation. I

Re: httpd and Curve25519 (X25519)

> Do the other short names in /usr/include/openssl/obj_mac.h work? `tls ecdhe "X25519"` gives the OK to the configuration, but the site then fails to load in Chromium 58.0.3029.96 or Firefox 53.0.2, which should both have X25519 support. `tls ecdhe "secp384r1"` gives the OK to the

Re: httpd and Curve25519 (X25519)

On May 14 14:30, Bryan wrote: > OpenBSD 6.1 httpd is (according to Qualys SSL Labs) using "Supported EC > Named Curves x25519, secp256r1, secp384r1 (server preferred order)" > when `tls ecdhe "auto"` is used in the server configuration. > > Is it possible to configure httpd to use only x25519? >

httpd and Curve25519 (X25519)

OpenBSD 6.1 httpd is (according to Qualys SSL Labs) using "Supported EC Named Curves x25519, secp256r1, secp384r1 (server preferred order)" when `tls ecdhe "auto"` is used in the server configuration. Is it possible to configure httpd to use only x25519? Trying various ways of specifying this

syspatch ideas

Hi, the syspatch utility for now knows only three options: -c(heck for available plugins and list them) -l(ist installed patches - "id"'s only) -r(evert most recent patch) .. and recently apparently also -R(evert all patches) Here are two additional features that would be very useful: 1)

How are people dealing with the Intel AMT BIOS vulnerability/backdoor?

Hi, Just checked my router today and found out that the AMT vuln is on there and active/provisioning, probably like most of your systems too.. I have had to disconnect it from the Internet of course. Looks like trying to disable AMT/MEBx within the BIOS doesn't do jack on my M58P, as it's

Re: openup vs. syspatch vs. pkg_add -u ?

Je 2017-05-14 16:56, Adam Thompson skribis: Now that we’re in the wonderful world of syspatch(8) – which works well for me so far (thanks for the hard work, everyone!), I’m trying to figure out if there’s still any point to using m:tier’s openup tool. From what I can tell, running “syspatch ;

Re: terminals + tmux + vim: ESC + arrows unexpected behaviour

On Sun, May 14, 2017 at 07:12:45PM +0200, frantisek holop wrote: > Andreas Kusalananda Kähäri, 14 May 2017 14:28: > > tmux has an "escape-time" setting: > > > > escape-time time > > Set the time in milliseconds for which tmux waits > > after an escape is input to determine

Re: iwm0: could not initiate scan

On May 14 15:55:34, s...@stsp.name wrote: > On Sun, May 14, 2017 at 03:24:34PM +0200, Jan Stary wrote: > > > But please show me your hostname.iwm0 file. > > dhcp > > So you're not setting a network name (and perhaps a WPA password) before > bringing the interface up. Does the message go away if

Re: terminals + tmux + vim: ESC + arrows unexpected behaviour

Andreas Kusalananda Kähäri, 14 May 2017 14:28: > tmux has an "escape-time" setting: > > escape-time time > Set the time in milliseconds for which tmux waits > after an escape is input to determine if it is part > of a function or meta key sequences. The default >

Re: iwm0: could not initiate scan

On Sun, May 14, 2017 at 06:06:47PM +0300, G wrote: > sorry for the last email. i wanted to write ifconfig iwm0 chan 5. > Still i dont know what you mean by change to 5GHz channel. 2GHz channels are numbered 1 to 14. 5GHz channels are numbered 36, 40, 48, 50, 52, etc. See

Re: iwm0: could not initiate scan

sorry for the last email. i wanted to write ifconfig iwm0 chan 5. Still i dont know what you mean by change to 5GHz channel. On 05/14/17 17:52, G wrote: > i dont understand what you mean? > If you mean ifconfig scan 5 > > i get > > ifconfig scan 5 > ifconfig: SIOCDIFADDR: Device not configured

openup vs. syspatch vs. pkg_add -u ?

Now that we’re in the wonderful world of syspatch(8) – which works well for me so far (thanks for the hard work, everyone!), I’m trying to figure out if there’s still any point to using m:tier’s openup tool. >From what I can tell, running “syspatch ; pkg_add -u” is pretty much >equivalent to

Re: iwm0: could not initiate scan

i dont understand what you mean? If you mean ifconfig scan 5 i get ifconfig scan 5 ifconfig: SIOCDIFADDR: Device not configured On 05/14/17 16:31, Stefan Sperling wrote: > On Sun, May 14, 2017 at 04:00:02PM +0300, G wrote: >> I noticed that wifi after a while becomes really slow and i have to

Re: iwm0: could not initiate scan

On Sun, May 14, 2017 at 03:47:59PM +0200, Jan Stary wrote: > Would you please recommend a card that has one of the radio chips > that support 5G, fits into the ALIX, and is known to work well? In my experience AR9280 chips work well. Cards with this chip exist in MiniPCI format as well as PCIe.

Re: iwm0: could not initiate scan

On Sun, May 14, 2017 at 03:24:34PM +0200, Jan Stary wrote: > > But please show me your hostname.iwm0 file. > dhcp So you're not setting a network name (and perhaps a WPA password) before bringing the interface up. Does the message go away if you do that? > > It's possible that you're running a

Re: iwm0: could not initiate scan

On May 14 15:31:12, s...@stsp.name wrote: > On Sun, May 14, 2017 at 04:00:02PM +0300, G wrote: > > I noticed that wifi after a while becomes really slow and i have to restart > > sh /etc/netstart > > in order for the speed to improve. > > Try a 5 GHz channel. Works great here. Hm, my athn has

Re: iwm0: could not initiate scan

On Sun, May 14, 2017 at 04:00:02PM +0300, G wrote: > I noticed that wifi after a while becomes really slow and i have to restart > sh /etc/netstart > in order for the speed to improve. Try a 5 GHz channel. Works great here.

default: couldn't open audio device

This is current/amdd64 on a Dell Latitude E5570 (dmesg below). I am experiencing the following audio regression: $ aucat -o /tmp/file.wav default: couldn't open audio device This happens with or without sndiod running. With sndiod -d -d running, it's: $ sndiod -d -d

Re: iwm0: could not initiate scan

On May 14 13:10:17, s...@stsp.name wrote: > On Sun, May 14, 2017 at 12:16:55PM +0200, Jan Stary wrote: > > This is current/amdd64 on a Dell Latitude E5570 (dmesg below). > > The "device timeouts" of iwm have mostly disappeared, > > Great! > > > but the boot sequence ends with > > > > iwm0: hw

Re: iwm0: could not initiate scan

I got similar messages on my dmesg. I noticed that wifi after a while becomes really slow and i have to restart sh /etc/netstart in order for the speed to improve. On 05/14/17 14:10, Stefan Sperling wrote: > On Sun, May 14, 2017 at 12:16:55PM +0200, Jan Stary wrote: >> This is current/amdd64 on a

Re: terminals + tmux + vim: ESC + arrows unexpected behaviour

On Sun, May 14, 2017 at 01:54:27PM +0200, frantisek holop wrote: > there seems to be some unexpected behaviour (at least > for me) in terminal vim running under tmux: > > pressing ESC and right after that the arrow keys to > move around (vim purist need not comment on this) get > interpreted as

terminals + tmux + vim: ESC + arrows unexpected behaviour

there seems to be some unexpected behaviour (at least for me) in terminal vim running under tmux: pressing ESC and right after that the arrow keys to move around (vim purist need not comment on this) get interpreted as different vim commands: for example UP will enter insert mode again, LEFT,

Re: iwm0: could not initiate scan

On Sun, May 14, 2017 at 12:16:55PM +0200, Jan Stary wrote: > This is current/amdd64 on a Dell Latitude E5570 (dmesg below). > The "device timeouts" of iwm have mostly disappeared, Great! > but the boot sequence ends with > > iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:40:21:08 >

Re: OpenBSD 6.1: BOOTIA32 3.32 issue

On Fri, 12 May 2017 16:15:52 +0200 Michele Curti wrote: > On Fri, May 12, 2017 at 06:01:35PM +0900, YASUOKA Masahiko wrote: >> > And something like this? >> >> Yes. What we need to do is comparing the device path node before >> MEDIA_DEVICE_PATH type. So I rewrote it

Re: Pinebook (if anyones up for it)

On Sat, May 13, 2017 at 11:43 PM, Andrew Gwozdziewycz wrote: > My understanding is that there is some support for the Pine64 platform, > though it requires access to the pins to get a serial console. I haven't > opened mine up yet, but I assume it's a Pine64, on a different

iwm0: could not initiate scan

This is current/amdd64 on a Dell Latitude E5570 (dmesg below). The "device timeouts" of iwm have mostly disappeared, but the boot sequence ends with iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:40:21:08 iwm0: could not initiate scan This particular message is not in iwm(4)

Re: CGI script to see collectd stats

On Wed, May 10, 2017 at 04:24:44PM +0530, ajitabhpan...@gmail.com wrote: > Hello, > > I am running collectd server on my OpenBSD 6.1 box and various clients are > sending stats to this box. I see /var/collectd that various RRDs are > getting created. However, I am not sure what should I used to

RESEND: Advice on migration to OpenBSD

Hi,� For some strange reason Yandex keeps messing up messages sent from it,sorry about that.� My original message:� I am in the process of migrating to OpenBSD on personal usage and in myoffice as well, but I need some advice.� Both at home and in the office we have several Linux boxes