Re: httpd ssl failures

2019-12-16 Thread Mayuresh
On Tue, Dec 17, 2019 at 03:22:17PM +1100, Geoff Wing wrote: > :> > Is this a problem with my setup? > :> Think it may be an httpd issue. Used the cert/key with postfix and tested > :> with openssl s_client and didn't see any issues. Notice this thread late. I have same issue with httpd

Re: httpd ssl failures

2019-12-16 Thread Geoff Wing
On Monday 2019-12-16 19:56 -0600, ed...@pettijohn-web.com output: :> > Certificate/key created like so: :> > openssl req -x509 -nodes -days 365 -sha256 -newkey rsa:2048 -keyout :> > mycert.pem -out mycert.pem [...] :> > Is this a problem with my setup? :> Think it may be an httpd issue. Used the

daily CVS update output

2019-12-16 Thread NetBSD source update
Updating src tree: P src/crypto/external/bsd/heimdal/Makefile.inc P src/crypto/external/bsd/heimdal/bin/krb5-config/Makefile P src/distrib/evbarm/instkernel/instkernel/Makefile P src/distrib/utils/embedded/conf/arm64.conf P src/distrib/utils/embedded/conf/armv7.conf P

RPi 3B+ pmap_tlb.c panic

2019-12-16 Thread Michael Cheponis
*[ 81623.3847677] panic: kernel diagnostic assertion "!cpu_intr_p()" failed: file "/c/usr/src/sys/uvm/pmap/pmap_tlb.c", line 979[ 81623.3847677] cpu0: Begin traceback...[ 81623.3847677] 0x9df29aac: netbsd:vpanic+0x16c[ 81623.3847677] Bad frame pointer: 0x80ab79bc[ 81623.3847677] cpu0: End

NetBSD Security Advisory 2019-006: Denial of service and possible privilege escallation in filemon

2019-12-16 Thread NetBSD Security-Officer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 NetBSD Security Advisory 2019-006 = Topic: Denial of service and possible privilege escallation in filemon Version:NetBSD-current: affected up to 9.99.17

Re: httpd ssl failures

2019-12-16 Thread Edgar Pettijohn
On 2019-12-15 20:09, Edgar Pettijohn wrote: On 2019-12-15 18:18, Edgar Pettijohn wrote: laptop$ uname -a NetBSD laptop.my.domain 9.99.24 NetBSD 9.99.24 (GENERIC_KASLR) #0: Sat Dec 14 21:37:06 CST 2019 r...@laptop.my.domain:/usr/obj/sys/arch/amd64/compile/GENERIC_KASLR amd64 Testing ssl

Automated report: NetBSD-current/i386 build failure

2019-12-16 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2019.12.16.15.59.04. An extract from the build.sh output follows:

NetBSD 9.0 RC1 compile error

2019-12-16 Thread 6bone
Hello, with enabled DEBUG: --- if_ena.o --- /usr/src/sys/dev/pci/if_ena.c: In function 'ena_request_io_irq': /usr/src/sys/dev/pci/if_ena.c:2089:7: error: unused variable 'irq_slot' [-Werror=unused-variable] int irq_slot = i + irq_off; ^~~~ Regards Uwe

Re: No uefi install in VM

2019-12-16 Thread Emmanuel Dreyfus
On Mon, Dec 16, 2019 at 01:52:32PM +0100, Martin Husemann wrote: > Yes, but as a fallback it is good (and sometimes you have "serial console" > and working copy & paste - though with modern server management this seems > to be a lost property). As a fallback, you can boot hd0b:/netbsd The dev

Re: No uefi install in VM

2019-12-16 Thread Martin Husemann
On Mon, Dec 16, 2019 at 12:50:39PM +, Emmanuel Dreyfus wrote: > I thought about it, but requiring the user to enter an UUID to boot > seems harsh. Yes, but as a fallback it is good (and sometimes you have "serial console" and working copy & paste - though with modern server management this

Re: No uefi install in VM

2019-12-16 Thread Emmanuel Dreyfus
On Mon, Dec 16, 2019 at 12:45:52PM +0100, Martin Husemann wrote: > P.S.: sysinst offer naming the partitions (in the partitions detail menu), > but it does not come up with names by itself. Could the boot code fall back > to the guid if no name is available? I thought about it, but requiring the

Re: No uefi install in VM

2019-12-16 Thread Martin Husemann
On Mon, Dec 16, 2019 at 08:52:29AM +, Emmanuel Dreyfus wrote: > The attached patch fixes the bug by avoid using NAME= when there > is no label. Once applied, rebuild src/sts/arch/i386/stand and > install updated bootstrap. This makes my old installation boot again! Please commit + request

Re: No uefi install in VM

2019-12-16 Thread Emmanuel Dreyfus
On Thu, Dec 12, 2019 at 08:41:15AM +0100, Martin Husemann wrote: > Yes, it is. I took a bootable UEFI installation (in VirtualBox) and replaced > the efi/boot/*.efi files on the MSDOS/EFI partition with the ones from > the latest netbsd-9 build and it stopped booting as you describe. I have a fix