bsdauth being removed from Dovecot?
Hi. Wondering if anyone noticed Timo’s email where he said: > To start, the following features are likely to be removed in next few > releases of Dovecot. > > - Authentication drivers: vpopmail, checkpassword, bsdauth, shadow, sia I’m a bit behind so if the last couple of releases of OpenBSD have moved dovecot away from bsdauth, then N/M. But if we’re still using bsdauth, has anyone looked at a Lua authentication replacement (https://doc.dovecot.org/configuration_manual/authentication/lua_based_authentication/ was given replacing the deprecated authentication mechanisms)? Sean
(No Subject)
Empty Message
More on wscons/X11 problem
I am trying to install X11 on a new machine (Zotac box running quad core Celeron with Intel HD graphics). X11 fails to launch with a message about not being able to find a console driver, as the Xorg log file shows below: [ 199.973] (==) Log file: "/home/raymond/.local/share/xorg/Xorg.0.log", Time:\ Tue Mar 31 10:23:19 2020 [ 199.974] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf\ .d" [ 199.974] (==) No Layout section. Using the first Screen section. [ 199.975] (==) No screen section available. Using defaults. [ 199.975] (**) |-->Screen "Default Screen Section" (0) [ 199.975] (**) | |-->Monitor "" [ 199.976] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 199.976] (==) Automatically adding devices [ 199.976] (==) Automatically enabling devices [ 199.976] (==) Not automatically adding GPU devices [ 199.976] (==) Max clients allowed: 256, resource mask: 0x1f [ 199.977] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [ 199.977] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 199.977] (II) The server relies on wscons to provide the list of input devi\ ces. If no devices become available, reconfigure wscons or disable AutoAddDe\ vices. [ 199.977] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 199.977] (II) The server relies on wscons to provide the list of input devi\ ces. If no devices become available, reconfigure wscons or disable AutoAddDe\ vices. [ 199.977] (II) Loader magic: 0x3c2056ae000 [ 199.977] (II) Module ABI versions: [ 199.977]X.Org ANSI C Emulation: 0.4 [ 199.977]X.Org Video Driver: 24.1 [ 199.977]X.Org XInput driver : 24.1 [ 199.977]X.Org Server Extension : 10.0 [ 199.978] (EE) Fatal server error: [ 199.978] (EE) xf86OpenConsole: No console driver found Supported drivers: wscons Check your kernel's console driver configuration and /dev entries(EE) [ 199.978] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 199.978] (EE) Please also check the log file at "/home/raymond/.local/share\ /xorg/Xorg.0.log" for additional information. [ 199.978] (EE) [ 199.979] (EE) Server terminated with error (1). Closing log file. I have compared the console and ttyC* entries in /dev/ with a functioning X11 system on my laptop. There were some differences in permissions, but changing those to match the laptop didn't help. Disabling AutoAddDevices in an X11 configuration file snippit didn't help either. Any pointers on where to look to fix this problem? -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond X11zotac.dmesg Description: Binary data
Re: Failed to install bootblocks. You will not be able to boot OpenBSD
On Fri, Apr 03, 2020 at 05:03:23PM +0200, Otto Moerbeek wrote: > On Fri, Apr 03, 2020 at 07:11:12AM -0700, Justin Noor wrote: > > > Hello OpenBSD Community, > > > > Hope you all are staying safe during these crazy times. > > > > I am looking for any feedback on an installation error that occurred using > > the custom-layout partition option across two SSDs. > > > > ERROR: > > > > Installboot: no OpenBSD partition > > Failed to install bootblocks. > > You will not be able to boot OpenBSD from sd0 > > > > VERSION: > > > > OpenBSD 6.6 release/install66.fs media > > I don't think so, the logs below shows you were using a snapshot, or > maybe a mixed install (boot from a snap install.fs, but install older > sets; don't do that). > > That would be my bet. Since you neglected to show any more detailad > info like the way you partitioned or an install log it is impossible > to diagnose what is going on. Thought about it a bit more. Since you did an EFI install and installboot did not find your EFI partion (it fell back to MBR) I must conclude that your custom disklabel did not include an entry for the EFI partition. Normally that would have been the 'i' partition in the auto-created disklabel. -Otto > > > > > MACHINE ARCHITECTURE: > > > > amd64/AMD Ryzen 5 chipset > > > > BACKGROUND: > > > > The plan was to install OpenBSD 6.6 across two disks. Previously, these > > disks had FreeBSD-12.1-ZFS installed on them. Since the disks were new and > > had no data on them, other than the FreeBSD installation sets, I decided > > not to clean the boot code area with 'dd if=/dev/zero of=/dev/rsd0c bs=1 > > count=1'. > > > > INSTALLATION STEPS: > > > > 1) Initialized disks for a GPT schema: > > > > # fdisk -iy -g -b 960 sd0 > > # fdisk -iy -g -b 960 sd1 > > > > 2) Entered the installer, choosing the custom-layout option for a whole > > disk GPT > > 3) Cleared the auto-generated partitions, and created all new partitions > > across sd0 and sd1 > > 4) At the error installer dropped into a shell. At the shell, I entered > > reboot, and the machine booted. > > 5) Logged into the machine and ran the installboot command: > > > > $ doas installboot -nv sd0 > > > > Output: > > > >Using / as root > >would install bootstrap on /dev/rsd0c > >using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot > >would copy /usr/mdec/boot to //boot > >looking for superblock at 65536 > >bad superblock magic 0x0 > >lookign for superblock at 8192 > >found valid ffs1 superblock > >//boot is 6 blocks x 16384 bytes > >fs block shift 2; part offset 1024; inode block 24, offset 1704 > >expecting 32-bit fs blocks (incr 0) > >master boot record (MBR) at secto 0 > >partition 0: type 0xEE offset 1 size 4294967295 > >installboot: no OpenBSD partition > > > > KEY OBSERVATIONS: > > > > 1) The error only occurs with the custom-layout option. When OpenBSD is > > installed on a single disk using the auto-layout option, the error does not > > occur > > > > 2) The error says there is "no OpenBSD partition," but there is an > > OpenBSD partition. > > > > $ doas fdisk sd0 > > > > Output: > > > >Disk: sd0 Usable LBA: 64 to 976772081 [976772081 Sectors] > > #: type [start:size ] > > > > > > 1: EFI Sys [ 64: 960 ] > > 2: OpenBSD [ 1024: 976772081 ] > > > > 3) The machine seems to boot and run fine. > > > > $ doas reboot > > > > Output: > > > > probing: pc0 mem[640K 63M 92M 16M 3308M 1M 42M 29171M] > > disk: hd0 hd1 > > >> OpenBSD/amd64 BOOTX64 3.46 > > boot> > > booting hd0a:/bsd: 12858696+2749448+326464+0+704512 > > [806406+128+1021271] > > > > 4) The system successfully updates to current - it generates the error - > > but it updates and reboots on its own. > > > > 5) The 'installboot' command generates a "bad superblock magic 0x0" error > > > > QUESTIONS: > > > > Why does the error say that there is no OpenBSD partition? > > Why does the error only occur with the custom-layout option? > > Should I have cleaned the boot-code region with dd if=/dev/zero > > of=/dev/rsd0c bs=1 count=1 before the installation? > > Is the "bad superblock magic 0x0 error" related to pre-existing garabage > > in the boot-code region? >
Re: Any console SIP client from ports or packages?
This one is exactly I'm looking for. Thanks ‐‐‐ Original Message ‐‐‐ On Thursday, April 2, 2020 9:31 PM, Mihai Popescu wrote: > pjsua > > It has audio only, no video part ported yet. I didn't use it with asterisk > but was fine with iptel.org.
Re: Contributing to spamd
Indeed ! Good luck, and thank you ! Le 3 avril 2020 18:49:56 GMT+02:00, Aisha Tammy a écrit : >Oh that is really good to hear :) >Thanks a lot phessler! > >Here is to hoping it can be included in the next release. > >Thanks a lot again, >Aisha > >On 4/3/20 12:28 PM, Denis Fondras wrote: >> On Fri, Apr 03, 2020 at 08:54:22AM -0400, Aisha Tammy wrote: >>> Hi devs and all, >>> I have been using spamd for quite a while and have been loving it. >>> I've seen that spamd currently only supports ipv4 and have been >>> wondering if it was possible to extend it to ipv6. I know that >workforce >>> is always limited so I wanted to know if there is anyway to >contribute >>> help towards this :) >>> I admit I'm not the most knowledgeable about ipv6 so I was wondering >if >>> there is any small place to start to contribute to spamd and build >up >>> from there. >>> Hoping for some positive response. >>> >>> Thanks a lot for your work and hope you are safe, >>> Aisha >>> >> >> phessler@ did almost all the work. There are still one issue so it >did not get >> in. >>
Re: Contributing to spamd
Oh that is really good to hear :) Thanks a lot phessler! Here is to hoping it can be included in the next release. Thanks a lot again, Aisha On 4/3/20 12:28 PM, Denis Fondras wrote: > On Fri, Apr 03, 2020 at 08:54:22AM -0400, Aisha Tammy wrote: >> Hi devs and all, >> I have been using spamd for quite a while and have been loving it. >> I've seen that spamd currently only supports ipv4 and have been >> wondering if it was possible to extend it to ipv6. I know that workforce >> is always limited so I wanted to know if there is anyway to contribute >> help towards this :) >> I admit I'm not the most knowledgeable about ipv6 so I was wondering if >> there is any small place to start to contribute to spamd and build up >> from there. >> Hoping for some positive response. >> >> Thanks a lot for your work and hope you are safe, >> Aisha >> > > phessler@ did almost all the work. There are still one issue so it did not get > in. >
Re: Faking the same LAN over the Internet
I think as long as one side of the tunnel is not doing NAT then you would be okay. For a while I had an IPSEC VPN going between my cloud server and my home desktop so that I could access my home desktop remotely and it worked well. Although, I have never tried any layer two tunneling. Report back and let us know how it goes. EtherIP might be simpler to set up. On Fri, Apr 3, 2020 at 11:51 AM Chris Rawnsley wrote: > Many thanks for all the suggestions, folks. > > I think I will have a play around with egre(4) and etherip(4) paired > with iked(8) first and then move on to OpenVPN if all else fails. I > will try to simulate the network layout with vmm(4) and hopefully > report back in a few days. > > > On Wed, 1 Apr 2020, at 18:47, Tom Smyth wrote: > > Gre is great and fast and a hell of a lot faster than OpenVPN... > > However and it is a Big However... > > Gre does not typically work Across NATs > > On my side of the link I have an APU2 with OpenBSD working as a > gateway and, potentially, managing this tunnelling too. As I have > not got into details yet, would the NAT issue be avoided if one side > of the tunnel has a public IP? > > -- > Chris Rawnsley > >
Re: Contributing to spamd
On Fri, Apr 03, 2020 at 08:54:22AM -0400, Aisha Tammy wrote: > Hi devs and all, > I have been using spamd for quite a while and have been loving it. > I've seen that spamd currently only supports ipv4 and have been > wondering if it was possible to extend it to ipv6. I know that workforce > is always limited so I wanted to know if there is anyway to contribute > help towards this :) > I admit I'm not the most knowledgeable about ipv6 so I was wondering if > there is any small place to start to contribute to spamd and build up > from there. > Hoping for some positive response. > > Thanks a lot for your work and hope you are safe, > Aisha > phessler@ did almost all the work. There are still one issue so it did not get in.
Re: Faking the same LAN over the Internet
Many thanks for all the suggestions, folks. I think I will have a play around with egre(4) and etherip(4) paired with iked(8) first and then move on to OpenVPN if all else fails. I will try to simulate the network layout with vmm(4) and hopefully report back in a few days. On Wed, 1 Apr 2020, at 18:47, Tom Smyth wrote: > Gre is great and fast and a hell of a lot faster than OpenVPN... > However and it is a Big However... > Gre does not typically work Across NATs On my side of the link I have an APU2 with OpenBSD working as a gateway and, potentially, managing this tunnelling too. As I have not got into details yet, would the NAT issue be avoided if one side of the tunnel has a public IP? -- Chris Rawnsley
bird make network unusable on 6.6-current
Hello,
As bird makes 6.6 panic, I tested it on 6.6-current. The kernel does
not panic, but after bird runs, networking deos not work anymore.
Bird seems to work correctly, it inserts routes in the kernel as
intended :
(before bird)
Routing tables
Internet:
DestinationGatewayFlags Refs Use Mtu Prio Iface
default10.42.42.1 UG100 -56 em0
224/4 127.0.0.1 URS0 17 32768 8 lo0
10.42.2/24 10.42.42.21UG100 -56 em0
10.42.42/2410.42.42.69U1h1 51 -56 em0
10.42.42.3 10.42.42.69UGHD 1 51 - L 56 em0
10.42.42.6908:00:27:d6:6e:dd UHLhl 1 26 - 1 em0
10.42.42.255 10.42.42.69UHb0 10 - 1 em0
127/8 127.0.0.1 UGRS 00 32768 8 lo0
127.0.0.1 127.0.0.1 UHhl 12 32768 1 lo0
(with bird)
Routing tables
Internet:
DestinationGatewayFlags Refs Use Mtu Prio Iface
default10.42.42.1 UGS5 12 - 8 em0
default10.42.42.1 UG100 -56 em0
224/4 127.0.0.1 URS0 15 32768 8 lo0
10.0.42.21 10.42.42.21UGH1 00 -56 em0
10.42.0/24 10.42.42.1 UG100 -56 em0
10.42.1.56/30 10.42.42.21UG100 -56 em0
10.42.1.64/30 10.42.42.21UG100 -56 em0
10.42.1.76/30 10.42.42.21UG100 -56 em0
10.42.2/24 10.42.42.21UGS04 - 8 em0
10.42.2/24 10.42.42.21UG100 -56 em0
10.42.2.25410.42.42.21UGH1 00 -56 em0
10.42.7.6 10.42.42.21UGH1 00 -56 em0
10.42.7.7 10.42.42.21UGH1 00 -56 em0
[...]
Bird config is simple (stripped comments):
router id 10.42.42.69;
protocol device {
}
protocol direct {
disabled; # Disable by default
ipv4; # Connect to default IPv4 table
ipv6; # ... and to default IPv6 table
}
protocol kernel {
ipv4 { # Connect protocol to IPv4 table by channel
import none; # Import to table, default is import all
export all; # Export to protocol. default is export none
};
}
protocol ospf v2 ospfv2 {
rfc1583compat yes;
tick 2;
ipv4 {};
area 0 {
interface "em0" { cost 10; };
};
}
But although bird adjacencies are ok, the box cannot communicate with
others, via TCP (ssh) or ping, even on the same link :
BIRD 2.0.6 ready.
ospfv2:
Router ID Pri State DTime Interface Router IP
10.42.42.21 1 ExStart/DR 39.261 em010.42.42.21
10.42.42.11 ExStart/BDR 38.635 em010.42.42.1
BIRD 2.0.6 ready.
ospfv3:
Router ID Pri State DTime Interface Router IP
10.42.42.21 1 Full/DR 35.854 em0
fe80::225:22ff:fe1e:bb7
10.42.42.11 Full/BDR36.525 em0
fe80::4262:31ff:fe01:4b66
PING fe80::225:22ff:fe1e:bb7 (fe80::225:22ff:fe1e:bb7): 56 data bytes
ping6: sendmsg: Network is unreachable
ping: wrote fe80::225:22ff:fe1e:bb7 64 chars, ret=-1
ping6: sendmsg: Network is unreachableping: wrote fe80::225:22ff:fe1e:bb7 64
chars, ret=-1
ping6: sendmsg: Network is unreachableping: wrote fe80::225:22ff:fe1e:bb7 64
chars, ret=-1
ping6: sendmsg: Network is unreachableping: wrote fe80::225:22ff:fe1e:bb7 64
chars, ret=-1
--- fe80::225:22ff:fe1e:bb7 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
PING 10.42.42.1 (10.42.42.1): 56 data bytes
ping: sendmsg: Invalid argument
ping: wrote 10.42.42.1 64 chars, ret=-1
ping: sendmsg: Invalid argument
ping: wrote 10.42.42.1 64 chars, ret=-1
ping: sendmsg: Invalid argument
ping: wrote 10.42.42.1 64 chars, ret=-1
ping: sendmsg: Invalid argument
ping: wrote 10.42.42.1 64 chars, ret=-1
--- 10.42.42.1 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
Stopping bird does not let network recover, nor does flushing routes
(route -n flush) or restarting interface with netstart em0
I've done theses tests on various VMs, as I didn't want to upgrade my
real router to snapshot (the bug is reproductible on virtual box &
qemu-kvm, with intel pro/1000 or virtio interfaces)
here is the dmesg (with errors that may be relevant):
OpenBSD 6.6-current (GENERIC) #94: Thu Apr 2 14:10:04 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GEN
Re: Contributing to spamd
Thanks a lot Ingo. I'm currently looking through spamd.c and trying to learn. I'm way too far behind to send any patches yet, lol. I'll slowly work to it. Much appreciated, Aisha On 4/3/20 9:40 AM, Ingo Schwarze wrote: > Hi Aisha, > > Aisha Tammy wrote on Fri, Apr 03, 2020 at 08:54:22AM -0400: > >> I have been using spamd for quite a while and have been loving it. >> I've seen that spamd currently only supports ipv4 and have been >> wondering if it was possible to extend it to ipv6. I know that workforce >> is always limited so I wanted to know if there is anyway to contribute >> help towards this :) > > The way to contribute to OpenBSD is by sending patches - ideally > small, incremental patches that work and are well tested, but when > you get stuck, you can also send something like: "I hope to do > FOOBAR, and here is what i have so far; the FOO part already seems > to work in my preliminary testing, but i have doubts whether my > approach to the BAR part is ideal. Feedback is welcome." > >> I admit I'm not the most knowledgeable about ipv6 so I was wondering if >> there is any small place to start to contribute to spamd and build up >> from there. >> Hoping for some positive response. > > Being able to learn on your own is among the key qualifications > required to contribute to OpenBSD. Learning by doing is recommended: > First find an issue you would like to fix. Good judgement of your > own abilities is essential here: don't pick a task so much over > your head that you have no chance of ever getting it done. Picking > something *slightly* more difficult than what you have experience > with may be OK if you are willing to learn and can tolerate the > frustration that unavoidably comes with the first try likely not > being good enough for commit yet. Then again, getting used to the > the processes of sending patches, receiving feeback, and improving > and re-sending the patches such that they get ready for commit may > also require some effort, so it is not a bad idea to start with > tasks you are absolutely sure you can easily manage, until you get > used to the processes, then progress to more difficult stuff in order > to learn and grow. > > When asking questions, be as specific as possible, ideally showing > specific patches or specific sequences of commands and asking > specific questions about them. > > Avoid questions similar to "what should i do" or "where should i > start" or "is there a todo list". That depends on what you are > interested in and what your abilities are, and you need to know > that yourself, no one else who doesn't know you personally can help > you with that. > > Sorry that i can't give you specifics about spamd(8), but your > question wasn't very specific anyway. In general, seamless IPv6 > support is welcome in OpenBSD, but i'm not sure about the requirements > of spamd(8) in particular since i never used it nor worked on it. > > Yours, > Ingo >
Re: Failed to install bootblocks. You will not be able to boot OpenBSD
On Fri, Apr 03, 2020 at 07:11:12AM -0700, Justin Noor wrote: > Hello OpenBSD Community, > > Hope you all are staying safe during these crazy times. > > I am looking for any feedback on an installation error that occurred using > the custom-layout partition option across two SSDs. > > ERROR: > > Installboot: no OpenBSD partition > Failed to install bootblocks. > You will not be able to boot OpenBSD from sd0 > > VERSION: > > OpenBSD 6.6 release/install66.fs media I don't think so, the logs below shows you were using a snapshot, or maybe a mixed install (boot from a snap install.fs, but install older sets; don't do that). That would be my bet. Since you neglected to show any more detailad info like the way you partitioned or an install log it is impossible to diagnose what is going on. -Otto > > MACHINE ARCHITECTURE: > > amd64/AMD Ryzen 5 chipset > > BACKGROUND: > > The plan was to install OpenBSD 6.6 across two disks. Previously, these > disks had FreeBSD-12.1-ZFS installed on them. Since the disks were new and > had no data on them, other than the FreeBSD installation sets, I decided > not to clean the boot code area with 'dd if=/dev/zero of=/dev/rsd0c bs=1 > count=1'. > > INSTALLATION STEPS: > > 1) Initialized disks for a GPT schema: > > # fdisk -iy -g -b 960 sd0 > # fdisk -iy -g -b 960 sd1 > > 2) Entered the installer, choosing the custom-layout option for a whole > disk GPT > 3) Cleared the auto-generated partitions, and created all new partitions > across sd0 and sd1 > 4) At the error installer dropped into a shell. At the shell, I entered > reboot, and the machine booted. > 5) Logged into the machine and ran the installboot command: > > $ doas installboot -nv sd0 > > Output: > >Using / as root >would install bootstrap on /dev/rsd0c >using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot >would copy /usr/mdec/boot to //boot >looking for superblock at 65536 >bad superblock magic 0x0 >lookign for superblock at 8192 >found valid ffs1 superblock >//boot is 6 blocks x 16384 bytes >fs block shift 2; part offset 1024; inode block 24, offset 1704 >expecting 32-bit fs blocks (incr 0) >master boot record (MBR) at secto 0 >partition 0: type 0xEE offset 1 size 4294967295 >installboot: no OpenBSD partition > > KEY OBSERVATIONS: > > 1) The error only occurs with the custom-layout option. When OpenBSD is > installed on a single disk using the auto-layout option, the error does not > occur > > 2) The error says there is "no OpenBSD partition," but there is an > OpenBSD partition. > > $ doas fdisk sd0 > > Output: > >Disk: sd0 Usable LBA: 64 to 976772081 [976772081 Sectors] > #: type [start:size ] > > > 1: EFI Sys [ 64: 960 ] > 2: OpenBSD [ 1024: 976772081 ] > > 3) The machine seems to boot and run fine. > > $ doas reboot > > Output: > > probing: pc0 mem[640K 63M 92M 16M 3308M 1M 42M 29171M] > disk: hd0 hd1 > >> OpenBSD/amd64 BOOTX64 3.46 > boot> > booting hd0a:/bsd: 12858696+2749448+326464+0+704512 > [806406+128+1021271] > > 4) The system successfully updates to current - it generates the error - > but it updates and reboots on its own. > > 5) The 'installboot' command generates a "bad superblock magic 0x0" error > > QUESTIONS: > > Why does the error say that there is no OpenBSD partition? > Why does the error only occur with the custom-layout option? > Should I have cleaned the boot-code region with dd if=/dev/zero > of=/dev/rsd0c bs=1 count=1 before the installation? > Is the "bad superblock magic 0x0 error" related to pre-existing garabage > in the boot-code region?
Failed to install bootblocks. You will not be able to boot OpenBSD
Hello OpenBSD Community, Hope you all are staying safe during these crazy times. I am looking for any feedback on an installation error that occurred using the custom-layout partition option across two SSDs. ERROR: Installboot: no OpenBSD partition Failed to install bootblocks. You will not be able to boot OpenBSD from sd0 VERSION: OpenBSD 6.6 release/install66.fs media MACHINE ARCHITECTURE: amd64/AMD Ryzen 5 chipset BACKGROUND: The plan was to install OpenBSD 6.6 across two disks. Previously, these disks had FreeBSD-12.1-ZFS installed on them. Since the disks were new and had no data on them, other than the FreeBSD installation sets, I decided not to clean the boot code area with 'dd if=/dev/zero of=/dev/rsd0c bs=1 count=1'. INSTALLATION STEPS: 1) Initialized disks for a GPT schema: # fdisk -iy -g -b 960 sd0 # fdisk -iy -g -b 960 sd1 2) Entered the installer, choosing the custom-layout option for a whole disk GPT 3) Cleared the auto-generated partitions, and created all new partitions across sd0 and sd1 4) At the error installer dropped into a shell. At the shell, I entered reboot, and the machine booted. 5) Logged into the machine and ran the installboot command: $ doas installboot -nv sd0 Output: Using / as root would install bootstrap on /dev/rsd0c using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot would copy /usr/mdec/boot to //boot looking for superblock at 65536 bad superblock magic 0x0 lookign for superblock at 8192 found valid ffs1 superblock //boot is 6 blocks x 16384 bytes fs block shift 2; part offset 1024; inode block 24, offset 1704 expecting 32-bit fs blocks (incr 0) master boot record (MBR) at secto 0 partition 0: type 0xEE offset 1 size 4294967295 installboot: no OpenBSD partition KEY OBSERVATIONS: 1) The error only occurs with the custom-layout option. When OpenBSD is installed on a single disk using the auto-layout option, the error does not occur 2) The error says there is "no OpenBSD partition," but there is an OpenBSD partition. $ doas fdisk sd0 Output: Disk: sd0 Usable LBA: 64 to 976772081 [976772081 Sectors] #: type [start:size ] 1: EFI Sys [ 64: 960 ] 2: OpenBSD [ 1024: 976772081 ] 3) The machine seems to boot and run fine. $ doas reboot Output: probing: pc0 mem[640K 63M 92M 16M 3308M 1M 42M 29171M] disk: hd0 hd1 >> OpenBSD/amd64 BOOTX64 3.46 boot> booting hd0a:/bsd: 12858696+2749448+326464+0+704512 [806406+128+1021271] 4) The system successfully updates to current - it generates the error - but it updates and reboots on its own. 5) The 'installboot' command generates a "bad superblock magic 0x0" error QUESTIONS: Why does the error say that there is no OpenBSD partition? Why does the error only occur with the custom-layout option? Should I have cleaned the boot-code region with dd if=/dev/zero of=/dev/rsd0c bs=1 count=1 before the installation? Is the "bad superblock magic 0x0 error" related to pre-existing garabage in the boot-code region?
Re: Contributing to spamd
Hi Aisha, Aisha Tammy wrote on Fri, Apr 03, 2020 at 08:54:22AM -0400: > I have been using spamd for quite a while and have been loving it. > I've seen that spamd currently only supports ipv4 and have been > wondering if it was possible to extend it to ipv6. I know that workforce > is always limited so I wanted to know if there is anyway to contribute > help towards this :) The way to contribute to OpenBSD is by sending patches - ideally small, incremental patches that work and are well tested, but when you get stuck, you can also send something like: "I hope to do FOOBAR, and here is what i have so far; the FOO part already seems to work in my preliminary testing, but i have doubts whether my approach to the BAR part is ideal. Feedback is welcome." > I admit I'm not the most knowledgeable about ipv6 so I was wondering if > there is any small place to start to contribute to spamd and build up > from there. > Hoping for some positive response. Being able to learn on your own is among the key qualifications required to contribute to OpenBSD. Learning by doing is recommended: First find an issue you would like to fix. Good judgement of your own abilities is essential here: don't pick a task so much over your head that you have no chance of ever getting it done. Picking something *slightly* more difficult than what you have experience with may be OK if you are willing to learn and can tolerate the frustration that unavoidably comes with the first try likely not being good enough for commit yet. Then again, getting used to the the processes of sending patches, receiving feeback, and improving and re-sending the patches such that they get ready for commit may also require some effort, so it is not a bad idea to start with tasks you are absolutely sure you can easily manage, until you get used to the processes, then progress to more difficult stuff in order to learn and grow. When asking questions, be as specific as possible, ideally showing specific patches or specific sequences of commands and asking specific questions about them. Avoid questions similar to "what should i do" or "where should i start" or "is there a todo list". That depends on what you are interested in and what your abilities are, and you need to know that yourself, no one else who doesn't know you personally can help you with that. Sorry that i can't give you specifics about spamd(8), but your question wasn't very specific anyway. In general, seamless IPv6 support is welcome in OpenBSD, but i'm not sure about the requirements of spamd(8) in particular since i never used it nor worked on it. Yours, Ingo
Contributing to spamd
Hi devs and all, I have been using spamd for quite a while and have been loving it. I've seen that spamd currently only supports ipv4 and have been wondering if it was possible to extend it to ipv6. I know that workforce is always limited so I wanted to know if there is anyway to contribute help towards this :) I admit I'm not the most knowledgeable about ipv6 so I was wondering if there is any small place to start to contribute to spamd and build up from there. Hoping for some positive response. Thanks a lot for your work and hope you are safe, Aisha
mapserver httpd configuration
Hello all,
Does anybody had tried to mapserver using httpd.
I had latest mapserver 7.3 installed but cannot configure as it gives 500
internal server error
https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/geo/mapserver/pkg/README-main?rev=1.4&content-type=text/x-cvsweb-markup
The above readme show information on ngix and supervisor.
I tried to copy the ngix config into my httpd.conf and got that 500
internel server error.
See my httpd.conf below:
server "mydomain.com" {
listen on * port 80
root "/htdocs/ mydomain.com"
location "*.php*" {
fastcgi socket "/run/php-fpm.sock"
}
location "/cgi-bin/mapserv" {
fastcgi socket "/run/mapserv.sock"
fastcgi param SCRIPT_FILENAME "/cgi-bin/mapserv"
}
}
I had php script working correctly and /var/www/cgi-bin/mapserv -v is
working correctly
MapServer version 7.2.2 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ
SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=ICONV
SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT
SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER
SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=GEOS SUPPORTS=PBF INPUT=JPEG
INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
In the Readme on cvs give details on chroot, but I don't know it usage for
using OpenBSD httpd
thanks for your help.
--
Regards,
Rashad
ospfd in 6.6 when dying doesn't recover database before adj timer expires
Hello, We've seen a issue where if you perform a ospfctl reload and have a faulty configuration for example a interface that doesn't exist it dies (which is fair in itself) but the seq num for the database never catches up with the DR until the adjacency timer expires over and over again, can take up to 30 minutes before it's back. I produce a failure with a faulty interface. Apr 3 10:03:46 router1 ospfd[36062]: fatal in rde: rde_nbr_new: unknown interface Apr 3 10:03:46 router1 ospfd[19043]: ospf engine exiting Apr 3 10:03:46 router1 ospfd[67917]: kernel routing table decoupled Apr 3 10:03:46 router1 ospfd[67917]: terminating Upon startup we then get stuck in this loop och trying to get back. Apr 3 10:04:15 router1 ospfd[91965]: startup Apr 3 10:06:22 router1 ospfd[19699]: nbr_adj_timer: failed to form adjacency with x.x.x.1 on interface vmx0 Apr 3 10:06:42 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27a9fd66 his 27a99b25 Apr 3 10:08:22 router1 ospfd[19699]: nbr_adj_timer: failed to form adjacency with x.x.x.1 on interface vmx0 Apr 3 10:09:17 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa6475 his 27a9fd69 Apr 3 10:10:22 router1 ospfd[19699]: nbr_adj_timer: failed to form adjacency with x.x.x.1 on interface vmx0 Apr 3 10:11:02 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa9109 his 27aa6476 Apr 3 10:11:22 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa9109 his 27aa6476 Apr 3 10:11:27 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa9109 his 27aa6476 Apr 3 10:11:32 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa9109 his 27aa6476 Apr 3 10:11:37 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa9109 his 27aa6476 Apr 3 10:11:42 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa9109 his 27aa6476 Apr 3 10:11:47 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27aa9109 his 27aa6476 Apr 3 10:12:22 router1 ospfd[19699]: nbr_adj_timer: failed to form adjacency with x.x.x.1 on interface vmx0 Apr 3 10:12:51 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27ab558d his 27aa910b Apr 3 10:12:51 router1 ospfd[19699]: recv_db_description: neighbor ID x.x.x.1: invalid seq num, mine 27ab558d his 27aa910b It's like it cannot match the database with the DR until the DEFAULT_ADJ_TMOUT (120sec) timeout occurs and it starts all over again. Anybody seen this before? Should probably note that the DR in the other end is not a device running OpenOSPFD. Best regards OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4278059008 (4079MB) avail mem = 4135682048 (3944MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0010 (620 entries) bios0: vendor Phoenix Technologies LTD version "6.00" date 04/05/2016 bios0: VMware, Inc. VMware Virtual Platform acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3) S16F(S3) S17F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3) PE50(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) Gold 6138 CPU @ 2.00GHz, 1995.58 MHz, 06-55-04 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,AVX512CD,AVX512BW,AVX512VL,PKU,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,XSAVEOPT,XSAVEC,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 65MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Xeon(R) Gold 6138 CPU @ 2.00GHz, 1995.12 MHz, 06-55-04 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,AVX512CD,AVX512BW,AVX512VL,PKU,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,XSAVEOPT,XSAVEC,XSAVES,M
Re: news from my hacked box
On Thu, Apr 02, 2020 at 10:26:36PM +0200, Kristjan Komlosi wrote: > The thing I find funny is that you insist on being spied on or somehow > hacked, you act tin-foil paranoid to the point of changing your laptop > because of some unexplained behavior, yet you use Speedtest.net and > CloudFlare DNS. Are you trolling or delusional? Looks like a troll and a longer he get fed, the longer he keeps going. -- Henri Järvinen
