>Synopsis: relayd doesn't verify backend TLS by default
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
>Synopsis: relayd applies 'with tls' to all relay backends if any have it
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
Thanks for taking a look. relayd is a complicated but still elegant solution to
some messy parts of the web and I appreciate that its author took the time to
look in on this.
On February 11, 2020 6:15:54 PM EST, Sebastian Benoit wrote:
>Nick(n...@kousu.ca) on 2020.02.11 07:29:44 +0
>Synopsis: relayd silently ignores ill-defined protocol mixtures
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
February 10, 2020 6:31 PM, "Nick" wrote:
>> Synopsis: relayd applies 'with tls' to all relay backends if any have it
>> Category: system
In light of looking into
<https://marc.info/?l=openbsd-bugs=158140337725409=2>, it occurs to me
that relayd's logic is that each
>Synopsis: relayd's 'listen on' support is incomplete
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
>Synopsis: relayd depends on the order of the 'forward' lines even when
>they should be unambiguous
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
>Synopsis: relayd gives 4xx errors on backend http protocol errors, but
>should give 5xx
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
>Synopsis: relayd hitting a syntax error will continue parsing and give
>even more confusing errors
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
>Synopsis: relayd mixes up filter rules when a protocol is reused in
>multiple relays
>Category: system
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
Ah I step in a giant puddle of egg for my first post here. My lines were all
too long and my sample code had typos. Let's try this again:
> How-To-Repeat:
```
$ mkdir relayd-confused-filters; cd relayd-confused-filters
```
```
$ openssl req -x509 -newkey
>Synopsis: amdgpu: random lockup with "Illegal register access in command
>stream"
>Category: kernel
>Environment:
System : OpenBSD 6.8
Details : OpenBSD 6.8 (GENERIC.MP) #96: Tue Sep 29 18:30:41 MDT 2020
a boot reboot at the ddb prompt, and when you do a dmesg after
the reboot, it's there for you. While I have lots of machines that
preserve dmesg across boots, those machines usually don't seem to ever
panic, the ones that panic don't save the dmesg buffer. :(
Nick.
found this one recently, runs 4.9, won't run current or 5.0, breakage
happened between 2011/05/28 snapshot and 2011/06/02 snapshot:
Synopsis: early boot panic post 5/28/2011 snapshot
Category: i386 kernel
Environment:
System : OpenBSD 4.9
Details : OpenBSD
that did it!
Nick.
On 12/04/11 12:16, Miod Vallat wrote:
Please try this:
Index: pci/pci_machdep.c
===
RCS file: /cvs/src/sys/arch/i386/pci/pci_machdep.c,v
retrieving revision 1.66
diff -u -p -r1.66 pci_machdep.c
--- pci
On 12/04/11 14:25, Mark Kettenis wrote:
I'd prefer to fix it with the diff below, to help the diffability with
the amd64 codebase.
I confirm this also seems to fix my p90.
Nick.
Index: pci_machdep.c
===
RCS file: /cvs/src
it.
Nick.
On 12/13/12 08:56, Martin Pieuchot wrote:
On 08/12/12(Sat) 23:43, Nick Holland wrote:
On 11/11/12 16:13, Brynet wrote:
It seems that macppc snapshots are broken on this model.
The RAMDISK kernel never reaches userland, it gets as far as mounting
root (root on rd0a..) and then.. stops
Synopsis: absurd packet loss for some packet sizes on Beaglebone Black
Category: armv7
Environment:
System : OpenBSD 5.4
Details : OpenBSD 5.4-current (GENERIC-OMAP) #11: Tue Oct 8
08:49:25 CEST 2013
On Thu, Jan 09, 2014 at 01:02:43PM +0100, Martin Pieuchot wrote:
Thanks for your bug report.
On 09/01/14(Thu) 18:55, Nick Gray wrote:
Synopsis: kernel panic when wscons display.screen_off variable is set to
a non-zero value
I can reproduce this bug here and the diff below fixes
On Tue, Jan 28, 2014 at 09:04:07PM -0800, Philip Guenther wrote:
On Tue, 28 Jan 2014, Nick Gray wrote:
Synopsis: Kernel panic in acpibat with AMD64 snapshot 24.01.2014 (#279)
on Macbook Core2Duo 2Ghz (2006 Model)
...
Fresh install of 5.5-beta AMD64 snapshot #279 on a Macbook
On Tue, Jan 28, 2014 at 09:04:07PM -0800, Philip Guenther wrote:
On Tue, 28 Jan 2014, Nick Gray wrote:
Synopsis: Kernel panic in acpibat with AMD64 snapshot 24.01.2014 (#279)
on Macbook Core2Duo 2Ghz (2006 Model)
...
Fresh install of 5.5-beta AMD64 snapshot #279 on a Macbook
back next week. :)
Nick.
On 03/18/14 15:38, jungleboogie0 wrote:
Hi Stuart,
the openbsd group doesn't have a BBB?
I replied to Nick's letter but I forgot to reply ALL. Is 5.5 going to be
released next week?
http://www.openbsd.org/faq/faq1.html#Next
Nick.
).
Nick.
OpenBSD 5.5 (GENERIC.MP) #262: Wed Mar 5 10:06:29 MST 2014
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz (GenuineIntel 686-class) 3 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI
On 04/05/14 20:45, Kenneth Westerback wrote:
On 5 April 2014 16:00, Nick Holland n...@holland-consulting.net wrote:
When setting up wireless for someone, tripped across this one:
# ifconfig ral0 nwkey 0x4646464646 - note: 10 hex digits
# ifconfig ral0
ral0: flags=8843UP,BROADCAST
Kim N. Lesmer Developer Unix/Linux sysadmin Web :
We really don't want to encourage the use of this process -- if you
can't figure out what files to download, it really is a clue you
probably shouldn't be doing this.
Nick.
fine with that. Fiddling with active partitions
is a known risk on all OSs. I was hoping to get lucky, I didn't, fine.
I do NOT want fdisk to limit what I can do with partitions. I like the
ability to do things with OpenBSD's fdisk that other OSs protect me
from doing.
Nick.
On 09/25/14 03:16, ML mail wrote:
Hi Nick,
Thanks for your detailed analysis of my situation.
I started first with updating my AMI BIOS firmware and now
have the latest version available from July 2014, before it
was a version of February 2014.
So what I tried is to format my USB key
Section 3.1 - Buying an OpenBSD CD set.
a official CD set should be an official CD set.
Section 3.7 - What is an appropriate first system to learn OpenBSD on?
more the better should be the more the better or more is better.
Best regards,
Nick Permyakov
was deemed too old, undermaintained in March of
this year, I believe it is the FAQ which must be fixed.
Ken
removed from both faq9.html and faq4.html
Nick.
to touch the disks when running in SW
RAID mode. It's a feature, not a bug.
Nick.
Index: landisk.html
===
RCS file: /home/nick/src/openbsd/cvs/www/landisk.html,v
retrieving revision 1.70
diff -u -p -u -r1.70 landisk.html
--- landisk.html8 Apr 2016 01:58:04 - 1.70
+++ landisk.html9 Jun 2016
As an aside: I dare not try fixing all these "seperate" in the tree, it seems
to have become OpenBSD's trademark spelling, haven't it? ;)
Index: sys/arch/sh/sh/locore_subr.S
===
RCS file: /cvs/src/sys/arch/sh/sh/locore_subr.S,v
Or maybe "Specifying multiple -v options increases the verbosity".
Index: src/usr.sbin/httpd/httpd.8
===
RCS file: /cvs/src/usr.sbin/httpd/httpd.8,v
retrieving revision 1.51
diff -u -p -u -r1.51 httpd.8
---
>Synopsis: multicast reception fails for certain groups on interfaces with
>TI ThunderLAN chip
>Category: system
>Environment:
System : OpenBSD 6.1
Details : OpenBSD 6.1-current (GENERIC) #4: Tue Jul 11 21:35:56 PDT
2017
08:49:41.963983 00:25:00:3e:ae:2d 01:00:5e:00:00:fb ip 72: 192.168.42.64.mdns >
224.0.0.251.mdns: 0 A? nobody.local. (30)
Thanks.
-- Nick Briggs
> On Jul 13, 2017, at 7:44 AM, Christian Weisgerber <na...@mips.inka.de> wrote:
>
> Nick Briggs:
>
>> The code i
I'm good with that.
> On Jul 13, 2017, at 7:37 PM, Ted Unangst <t...@tedunangst.com> wrote:
>
> Nick Briggs wrote:
>> because netinet/ip_var.h, which it includes, depends on
>> #ifdef MROUTING
>> extern struct socket *ip_mrouter[]; /* multicast routin
>Synopsis: missing "struct socket;" in netinet/ip_var.h prevents compiling
>without MROUTING option
>Category: system
>Environment:
System : OpenBSD 6.1
Details : OpenBSD 6.1-stable (PIGEON) #5: Thu Jul 13 17:09:51 PDT
2017
> Synopsis: sys/arch/i386/i386/bios.c won't compile if NACPI ==0 and NAPM>0
> Category: system
> Environment:
System : OpenBSD 6.1
Details : OpenBSD 6.1-stable (PIGEON) #5: Thu Jul 13 17:09:51 PDT
2017
> On Jul 14, 2017, at 10:29 PM, Mike Larkin <mlar...@azathoth.net> wrote:
>
> On Fri, Jul 14, 2017 at 03:39:25PM -0700, Nick Briggs wrote:
>>
>>> Synopsis: sys/arch/i386/i386/bios.c won't compile if NACPI ==0 and
>>> NAPM>0
>>> Cat
, 2018 at 7:55 AM, Juan Francisco Cantero Hurtado <
i...@juanfra.info> wrote:
> Try this:
>
> python2.7 -c 'import urllib2; web = urllib2.urlopen("https://www.
> mercurial-scm.org/repo/hello"); print web.read()'
>
> Does python crash?
>
>
> On Fri, M
t will run a few tests against
> the SSL library. You should see some segfaults there.
>
>
>
> On Sat, May 19, 2018 at 10:19:17AM -0700, Nick Owens wrote:
> > no, that's working fine. it does not crash and i see the HTML content
> from
> > the webserver.
> >
t;
> 2018-05-19 22:48 GMT+02:00 Nick Owens <misch...@offblast.org>:
>
>> my ERL is very sad and slow with a 500mhz cpu/512M ram and the usb drive
>> is
>> very sad and slow at around 1-2MB/s throughput.
>>
>> i will see about getting ports going on it, but i
it looks like that's working. with this test mercurial prints (falling back
to static-http) whereas in the mercurial 'hello' repo it does not. i wonder
if it has something todo with the web server/http protocol.
erl$ pwd
/home/mischief
erl$ df -h
Filesystem SizeUsed Avail Capacity
Python-2.7.14/Python-2.7.14/Modules/socketmodule.c:2441
#2 0x002dd052c32d in ?? ()
On Sun, May 20, 2018 at 3:13 PM, Nick Owens <misch...@offblast.org> wrote:
> are there instructions i can read for operating ports over NFS? i have my
> R400 running 6.3 directly connected via
ry X), USB
keyboard worked, looks like a wonderfully usable box. Other than
the disk. :)
Any prayer of using it for OpenBSD?
Thanks,
Nick.
OpenBSD 6.3-current (GENERIC.MP) #54: Mon Jun 25 13:10:32 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 21089320
On 06/27/18 08:16, Nick Holland wrote:
> Cute little Atom powered disk box, but it seems the AHCI(-like?)
> interfaces aren't working properly on OpenBSD. This system booted
> from the on-board USB flash (PXE boot/install) and has a 1T SATA
> disk that was recognized during POST.
&
bus11 target 0 lun 0
da0: < USB DISK 2.0 PMAP> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 650043DFAD4A2A17
da0: 40.000MB/s transfers
da0: 956MB (1957888 512 byte sectors)
da0: quirks=0x3
GEOM_PART: integrity check failed (da0s4, BSD)
GEOM_PART: integrity check failed (diskid/DI
> -Otto
>>
>
> So I spend/wasted some time on this. There is a diff on tech@ and in
> snapshots that enables booting on amd64 and i386 with very big root
> filesystems. Note that on amd64 and i386 the bootloader uses bios
> calls to load the kernel. These bios calls might have restrictions.
>
> The advise on partitioning your disk still stands.
>
> -Otto
>
Fixed a machine that had only a 500mb root partition, but I managed to
put a 32k block format on. No idea how I did it, but it fixed it!
Nick.
here the first
write to disk gets lost. fsck? First write is correcting the disk, it
gets lost, thus you still have a problem. You could also do some
sacrificial first write to the disk, but I don't think you will see a
big problem if you just switch to an LSI SCSI or SAS driver.
Nick.
current
> Linux distro with OpenBSD!
If you have a Linux system, using the dd process should work nicely.
Nick.
bug reporting page on the website. And
I'd start disabling individual ACPI drivers a few at a time until you
figure out exactly which ONE ACPI device is causing your problem. Then
report back with that info and a dmesg of the system.
Nick.
5.0% spin, 13.2% intr, 6.4%
idle
CPU1 states: 0.0% user, 0.0% nice, 0.8% sys, 0.2% spin, 0.0% intr, 99.0%
idle
Memory: Real: 147M/794M act/tot Free: 1175M Cache: 385M Swap: 0K/1026M
PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
79498 nick 20 1364K 277
roblem I'm having (7/24. "acpimadt(4) problem").
Quick starting point might be to try disabling acpimadt, and see if that
helps.
Nick.
>
>> On 2019/07/25 18:10, Per Gunnarsson wrote:
>> > It's the same with the snapshot I got from the norwegian mirror. Console
>
On 7/24/19 8:49 PM, Nick Holland wrote:
> This machine seems to have a problem with acpimadt(4).
>
> It will not run bsd.rd for an install or upgrade. It hangs
> seemingly indefinitely at "root on ..." after otherwise seeming
> to booted successfully.
>
>
drop ONE packet sometimes, never two or more.
My really bad ones were also odd sizes, but I saw lesser problems
on at least -s480.
Mine was a Beaglebone Black, with its cpsw(4).
https://marc.info/?l=openbsd-bugs=138275913126582=2
Nick.
>Synopsis: multiple rge(4) nics causes hang
>Category: kernel
>Environment:
System : OpenBSD 6.8
Details : OpenBSD 6.8 (GENERIC.MP) #5: Mon Feb 22 04:36:10 MST 2021
On Tue, Mar 2, 2021 at 7:00 PM Kevin Lo wrote:
>
> On Tue, Mar 02, 2021 at 02:20:12PM -0800, Nick Owens wrote:
> >
> > >Synopsis:multiple rge(4) nics causes hang
> > >Category:kernel
> > >Environment:
> > System : OpenBSD 6.8
> &
On Wed, Mar 03, 2021 at 01:54:52PM +0800, Kevin Lo wrote:
> On Tue, Mar 02, 2021 at 08:23:38PM -0800, Nick Owens wrote:
> >
> > On Tue, Mar 2, 2021 at 7:00 PM Kevin Lo wrote:
> > >
> > > On Tue, Mar 02, 2021 at 02:20:12PM -0800, Nick Owens wrote:
> > &
On 7/25/22 3:27 PM, Nick Holland wrote:
Somewhere between 7.1 release and -current, X quit working
on this machine. It is a really lousy machine, wireless
doesn't work, slow, etc., and it cost $80 new (and is
currently $60), so "What do you expect?" is a valid response.
But in ca
On 7/25/22 4:34 PM, Chris Narkiewicz wrote:
On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
Sigh. collect info, leave out most basic part: what I mean
by "X quit working"...
I checked your Xorg.0.log and it looks familiar. Please look for post
"X11 hangs on
On 7/26/22 8:43 AM, Jonathan Gray wrote:
On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
> Sigh. collect info, leave out most basic part: what I mean
> by "X quit working"...
I checked your Xorg.0.
I have experienced this same issue on an old Lenovo laptop of mine 4 years ago.
Wish I knew about the machine gop command back then! :(
Best,
Nick
On 9/15/22 18:58, Chris Narkiewicz wrote:
On Mon, Jul 25, 2022 at 03:27:30PM -0400, Nick Holland wrote:
Somewhere between 7.1 release and -current, X quit working
on this machine. It is a really lousy machine, wireless
doesn't work, slow, etc., and it cost $80 new (and is
currently $60), so
Back from vacation, sorry for the delay in responding...
On 7/28/22 10:04, Jonathan Gray wrote:
On Tue, Jul 26, 2022 at 09:56:21AM -0400, Nick Holland wrote:
On 7/26/22 8:43 AM, Jonathan Gray wrote:
> On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
> > On Mon, Jul
On 8/10/22 00:42, Jonathan Gray wrote:
On Tue, Aug 09, 2022 at 10:29:41AM -0400, Nick Holland wrote:
On 8/9/22 09:36, Jonathan Gray wrote:
> On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > > When looking at top what does Xorg have for WAIT?
> >
> >
On 8/9/22 09:36, Jonathan Gray wrote:
On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> When looking at top what does Xorg have for WAIT?
PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
41914 _x11 -22 -1 15M 26M idle schto 0:01 0
68 matches
Mail list logo
