The vim display issue on OpenBSD
Hi all, Greetings from me! I meet a weird issue: there is a file which contains only "1": # cat a 1 While use vim to open it, it displays "0". I find the number behind cursor will decrease 1. Does anyone bump into this issue? Thanks very much in advance! P.S., my OpenBSD is 6.2 release, and vim is 8.0.1476. Best Regards Nan Xiao
Re: bridging vmm network
On Thu, Mar 08, 2018 at 05:48:05PM +, niya wrote: > hi > > i working out my ideas for modelling my home network, > > the network will have four vether interfaces to cover the needs of my > firewall, > > which will have a lan, demilitarised zone, carp redundancy and connection > to the wan, > > should i bridge all four vether interfaces to one bridge or a separate > bridge for each ? > Can you explain a bit more? Specifically, what role is vmm playing here? -ml
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 09.03.2018 um 00:09 schrieb Stefan Wollny: > Am 08.03.2018 um 23:25 schrieb Stefan Wollny: >> Am 08.03.2018 um 22:11 schrieb Stefan Wollny: >> >>> Am 08.03.2018 um 17:44 schrieb Stefan Wollny: Gesendet von meinem BlackBerry 10-Smartphone. Originalnachricht Von: Kevin Chadwick Gesendet: Donnerstag, 8. März 2018 17:28 An: misc@openbsd.org Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument On Thu, 8 Mar 2018 14:47:43 +0100 > Has anyone a clue what might have happend and how to solve the issue? > I searched the net but didn't find any substantial infos on this. As > the error happends with all three USB-keys I have this is unlikely to > be cause of the trouble. The bootloader normally lists the disks that the bios sees beforehand e.g. disk: hd0+ hd1+ sr0* >> OpenBSD/amd64 BOOT 3.34 Perhaps they have been moved around? I tried boot hd1a:/bsd but got the same message. I can enter # fsck -fy hd0a but this just gets me a prompt without any action. BTW: This is a SSD. >>> OK - back at home I downloaded install63.iso and burned a CD which does >>> start. Choosing "(U)pgrade" I am presented with "Available disks are: >>> sd0 sd1" - but both are "not a valid root disk". Back to the shell I >>> tried fdisk but I get "fdisk: sd0: No such file or directory" >>> >>> Could this be an issue with the bootloader or is it the encryption of >>> softraid0 that hinders the upgrade? >>> > tb@ provided another valuable hint: > I can start the boot-process with 'boot sr0a:/bsd' but this ends with a > panic: > > ... > softraid0 at root > scsibus4 at softraid0:256 targets > panic: root device (...) not found > Stopped at db_enter+0x5: popq %rbp > TID PID UID PRFLAGS PFLAGS CPU COMMAND > * 0 0 0 0X1 0X200 OK swapper > ... > OK . final remarks for tonight: I can start 'boot sr0a:/bsd.rd' but trying to upgrade is the same dead-end road - "sd0 is not a valid root device". 'fdisk sd0' shows the expected '*' before the partition number. 'disklabel sd0' shows the expected fstype "RAID" 'for sd0a. Doing 'bioctl -c C -l /dev/sd0a' says "KDF hint has invalid size". 'installboot -nv sd0a' misses '/usr/mdec/biosboot' - there is only '/usr/mdec/mbr'. While the 'upgrade' started from 'boot sr0a:/bsd.rd' does not see 'sd0' the 'install' process started from the CD actually does. Sigh - I need some sleep...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 23:25 schrieb Stefan Wollny: > Am 08.03.2018 um 22:11 schrieb Stefan Wollny: > >> Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >>> Gesendet von meinem BlackBerry 10-Smartphone. >>> Originalnachricht >>> Von: Kevin Chadwick >>> Gesendet: Donnerstag, 8. März 2018 17:28 >>> An: misc@openbsd.org >>> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >>> >>> On Thu, 8 Mar 2018 14:47:43 +0100 >>> >>> Has anyone a clue what might have happend and how to solve the issue? I searched the net but didn't find any substantial infos on this. As the error happends with all three USB-keys I have this is unlikely to be cause of the trouble. >>> The bootloader normally lists the disks that the bios sees beforehand >>> e.g. >>> >>> disk: hd0+ hd1+ sr0* > OpenBSD/amd64 BOOT 3.34 >>> Perhaps they have been moved around? >>> >>> >>> I tried >>> >>> boot hd1a:/bsd >>> >>> but got the same message. >>> >>> I can enter # fsck -fy hd0a but this just gets me a prompt without any >>> action. BTW: This is a SSD. >>> >> OK - back at home I downloaded install63.iso and burned a CD which does >> start. Choosing "(U)pgrade" I am presented with "Available disks are: >> sd0 sd1" - but both are "not a valid root disk". Back to the shell I >> tried fdisk but I get "fdisk: sd0: No such file or directory" >> >> Could this be an issue with the bootloader or is it the encryption of >> softraid0 that hinders the upgrade? >> tb@ provided another valuable hint: I can start the boot-process with 'boot sr0a:/bsd' but this ends with a panic: ... softraid0 at root scsibus4 at softraid0:256 targets panic: root device (...) not found Stopped at db_enter+0x5: popq %rbp TID PID UID PRFLAGS PFLAGS CPU COMMAND * 0 0 0 0X1 0X200 OK swapper ...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 23:25 schrieb Stefan Wollny: > Am 08.03.2018 um 22:11 schrieb Stefan Wollny: > >> Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >>> Gesendet von meinem BlackBerry 10-Smartphone. >>> Originalnachricht >>> Von: Kevin Chadwick >>> Gesendet: Donnerstag, 8. März 2018 17:28 >>> An: misc@openbsd.org >>> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >>> >>> On Thu, 8 Mar 2018 14:47:43 +0100 >>> >>> Has anyone a clue what might have happend and how to solve the issue? I searched the net but didn't find any substantial infos on this. As the error happends with all three USB-keys I have this is unlikely to be cause of the trouble. >>> The bootloader normally lists the disks that the bios sees beforehand >>> e.g. >>> >>> disk: hd0+ hd1+ sr0* > OpenBSD/amd64 BOOT 3.34 >>> Perhaps they have been moved around? >>> >>> >>> I tried >>> >>> boot hd1a:/bsd >>> >>> but got the same message. >>> >>> I can enter # fsck -fy hd0a but this just gets me a prompt without any >>> action. BTW: This is a SSD. >>> >> OK - back at home I downloaded install63.iso and burned a CD which does >> start. Choosing "(U)pgrade" I am presented with "Available disks are: >> sd0 sd1" - but both are "not a valid root disk". Back to the shell I >> tried fdisk but I get "fdisk: sd0: No such file or directory" >> >> Could this be an issue with the bootloader or is it the encryption of >> softraid0 that hinders the upgrade? >> > ??? > Running dmesg from the CD-shell the system "sees" sd0 (the internel SSD) > and sd1 (the USB with the key). Having attached another USB drive I see > this is recognizes as sd2. But running 'fdisk sd2' or 'disklabel sd2' I > get "No such file or directory" (and consequently as well when trying to > mount this external drive). > > Puzzled... > tb@ hit me with the clue stick: MAKEDEV was the missing part to mount the external USB drive. Now: Here's the dmesg OpenBSD 6.3-beta (RAMDISK_CD) #38: Thu Mar 8 10:01:01 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 17079074816 (16287MB) avail mem = 16557678592 (15790MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries) bios0: vendor American Megatrends Inc. version "1.03.06" date 06/25/2014 bios0: Notebook W65_67SZ acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT SSDT DMAR acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz, 3093.25 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP03) acpiprt3 at acpi0: bus 4 (RP04) acpiprt4 at acpi0: bus 1 (P0P2) acpiprt5 at acpi0: bus -1 (P0PA) acpiprt6 at acpi0: bus -1 (P0PB) acpiprt7 at acpi0: bus 1 (PEG0) acpiec0 at acpi0 acpicpu at acpi0 not configured acpitz at acpi0 not configured "INT3F0D" at acpi0 not configured "MSFT0001" at acpi0 not configured "ETD0403" at acpi0 not configured "PNPC000" at acpi0 not configured "PNP0C0C" at acpi0 not configured "PNP0C0E" at acpi0 not configured "PNP0C0D" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT340E" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi pci1 at ppb0 bus 1 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) "Intel Core 4G HD Audio" rev 0x06 at pci0 dev 3 function 0 not configured xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x05: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x05: apic 2 int 16 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel 8 Series HD Audio" rev 0x05 at pci0 dev 27 function 0 not configured ppb1 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5 pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 2 "Intel 8 Series PCIE" rev 0xd5: msi pci3 at ppb2 bus
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 22:11 schrieb Stefan Wollny: > Am 08.03.2018 um 17:44 schrieb Stefan Wollny: >> Gesendet von meinem BlackBerry 10-Smartphone. >> Originalnachricht >> Von: Kevin Chadwick >> Gesendet: Donnerstag, 8. März 2018 17:28 >> An: misc@openbsd.org >> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >> >> On Thu, 8 Mar 2018 14:47:43 +0100 >> >> >>> Has anyone a clue what might have happend and how to solve the issue? >>> I searched the net but didn't find any substantial infos on this. As >>> the error happends with all three USB-keys I have this is unlikely to >>> be cause of the trouble. >> The bootloader normally lists the disks that the bios sees beforehand >> e.g. >> >> disk: hd0+ hd1+ sr0* OpenBSD/amd64 BOOT 3.34 >> Perhaps they have been moved around? >> >> >> I tried >> >> boot hd1a:/bsd >> >> but got the same message. >> >> I can enter # fsck -fy hd0a but this just gets me a prompt without any >> action. BTW: This is a SSD. >> > OK - back at home I downloaded install63.iso and burned a CD which does > start. Choosing "(U)pgrade" I am presented with "Available disks are: > sd0 sd1" - but both are "not a valid root disk". Back to the shell I > tried fdisk but I get "fdisk: sd0: No such file or directory" > > Could this be an issue with the bootloader or is it the encryption of > softraid0 that hinders the upgrade? > ??? Running dmesg from the CD-shell the system "sees" sd0 (the internel SSD) and sd1 (the USB with the key). Having attached another USB drive I see this is recognizes as sd2. But running 'fdisk sd2' or 'disklabel sd2' I get "No such file or directory" (and consequently as well when trying to mount this external drive). Puzzled...
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Am 08.03.2018 um 17:44 schrieb Stefan Wollny: > > Gesendet von meinem BlackBerry 10-Smartphone. > Originalnachricht > Von: Kevin Chadwick > Gesendet: Donnerstag, 8. März 2018 17:28 > An: misc@openbsd.org > Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > > On Thu, 8 Mar 2018 14:47:43 +0100 > > >> Has anyone a clue what might have happend and how to solve the issue? >> I searched the net but didn't find any substantial infos on this. As >> the error happends with all three USB-keys I have this is unlikely to >> be cause of the trouble. > The bootloader normally lists the disks that the bios sees beforehand > e.g. > > disk: hd0+ hd1+ sr0* >>> OpenBSD/amd64 BOOT 3.34 > Perhaps they have been moved around? > > > I tried > > boot hd1a:/bsd > > but got the same message. > > I can enter # fsck -fy hd0a but this just gets me a prompt without any > action. BTW: This is a SSD. > OK - back at home I downloaded install63.iso and burned a CD which does start. Choosing "(U)pgrade" I am presented with "Available disks are: sd0 sd1" - but both are "not a valid root disk". Back to the shell I tried fdisk but I get "fdisk: sd0: No such file or directory" Could this be an issue with the bootloader or is it the encryption of softraid0 that hinders the upgrade?
bridging vmm network
hi i working out my ideas for modelling my home network, the network will have four vether interfaces to cover the needs of my firewall, which will have a lan, demilitarised zone, carp redundancy and connection to the wan, should i bridge all four vether interfaces to one bridge or a separate bridge for each ?
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Gesendet von meinem BlackBerry 10-Smartphone. Originalnachricht Von: Kevin Chadwick Gesendet: Donnerstag, 8. März 2018 17:28 An: misc@openbsd.org Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument On Thu, 8 Mar 2018 14:47:43 +0100 > Has anyone a clue what might have happend and how to solve the issue? > I searched the net but didn't find any substantial infos on this. As > the error happends with all three USB-keys I have this is unlikely to > be cause of the trouble. The bootloader normally lists the disks that the bios sees beforehand e.g. disk: hd0+ hd1+ sr0* >> OpenBSD/amd64 BOOT 3.34 Perhaps they have been moved around? I tried boot hd1a:/bsd but got the same message. I can enter # fsck -fy hd0a but this just gets me a prompt without any action. BTW: This is a SSD.
Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
On Thu, 8 Mar 2018 14:47:43 +0100 > Has anyone a clue what might have happend and how to solve the issue? > I searched the net but didn't find any substantial infos on this. As > the error happends with all three USB-keys I have this is unlikely to > be cause of the trouble. The bootloader normally lists the disks that the bios sees beforehand e.g. disk: hd0+ hd1+ sr0* >> OpenBSD/amd64 BOOT 3.34 Perhaps they have been moved around?
Re: Cloud Services and kernel mitigations and OpenBSD cli support
Cloud poses a risk to privacy that you cannot and must not ignore in business. Ignore everyone that says otherwise. --- If you are a fabless company, for example, it is easy for a cloud sysadmin to exploit the latest vulnerabilities to read your data bank and sell your secrets. Email (yahoo, hotmail, gmail, you name it) is another example of cloud service: sysadmins do not need to exploit anything, because the contents are stored in plain text. --- If you need a cloud, you better make your own. Sent from ProtonMail Mobile On Thu, Mar 8, 2018 at 11:51, Kevin Chadwick wrote: > We all know Bare metal is more secure (ignoring physical security) especially > with OpenBSD but if you need cost effective global resources on tap then I > believe you need cloud. We all know microsoft have a huge user base and > userland issues that are problematic however despite some recent Linux kernel > mitigation adoption attemps, Linux focus on kernel mitigations have been > lacklustre whilst microsoft have been comparatively active albeit enabling > and enforcing mitigations (even ASLR) for all applications by default has > been lacklustre. As cloud services are free from microsofts userland it is a > *hopeful* assumption that their security mitigation works applies to their > cloud too whereas I expect it is unlikely with Amazon and Google (AFAIK > Android fairs better than Linux for mitigations due to Google however??) > Perhaps OpenBSD mitigations still apply effectively to ec2 instances and > cloud services isolation is good enough to never undermine this, though I > find that hard to believe. Perhaps new processor developments will solve this > issue. None of this matters if you cannot get things done. I know there is > OpenBSD AWS client availability but I am unsure about Azure, Google etc. Any > advice and experience is welcome, Thankyou.
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
Hi there! I need help or some hints on how to proceed: My system a laptop running amd64-current fully encrypted, key-based. I start from BIOS, not UEFI. Two days ago I updated to the then latest snapshot and apparently s.th. went wrong: At reboot the system stops after >> OpenBSD/amd64 BOOT 3.34 open(hd0a:/etc/boot.conf): Invalide argument boot> cannot open hd0a:/etc/random.seed: Invalid argument booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try /bsd Turning timeout off. boot> Has anyone a clue what might have happend and how to solve the issue? I searched the net but didn't find any substantial infos on this. As the error happends with all three USB-keys I have this is unlikely to be cause of the trouble. At present I only have a USB-stick with install62.fs with me (roughly 3~4 weeks old) which only starts if I change from BIOS to UEFI. As all data from /home is redundantly backed up I could reinstall everything but would prefer to avoid it. There are dmesgs from this laptop with some older posts. Obviously no current dmesg possible... Any hint/idea/suggestion welcome! TIA. Best, STEFAN
Re: [6.2] Problem with X, .cwmrc file missing from fresh install
Thanks for the info, I got a picture there needs to be a default one from last thread. Ill read docs more carefully next time. On Thu, Mar 8, 2018 at 8:49 AM, Maurice McCarthy wrote: > On 08/03/18 05:16, Luka Kosanovic wrote: >> Hi, Im a new user and I have a problem with cwm, everything works, I >> login and default xterm window appears but default keyboard shortcuts >> do not work. I tried many standard shortcuts and nothing happens, then >> I went on mailing lists and found somebody had the same problem a >> month ago so I did a little bit of digging and found out .cwmrc conf >> file doesnt exist. >> Can you please tell me why is that, shouldnt there >> be a default file in my home folder with a fresh install? Everything >> else works as expected there were no problems. >> >> Thank you >> > > The zero config is intentional. First have a read of man 5 cwmrc. My own > ~/.cwmrc looks like this: > > command xterm /usr/X11R6/bin/xterm -bg black -fg wheat -fn 10x20 -ls > > and ~/.xsession like this: > > exec /usr/X11R6/cwm > > > and ~/.xinitrc like so: > > /usr/X11R6/bin/xconsole -geometry -0+0 -fn 8x10 & \ > /usr/X11R6/bin/xterm -e tmux -2u & \ > /usr/X11R6/bin/xterm & \ > /usr/X11R6/bin/cwm > > Good Luck >
Re: Cloud Services and kernel mitigations and OpenBSD cli support
Hi, I've yet to stumble upon the first provider which actually uses OpenBSD as the hypervisor, instead of VMware, Xen, KVM, etc. That, in fact, would be an awesome development. I have been thinkering with this thought back and forth, but the IT company I work for isn't big enough to facilitate this - yet. As to public clouds, no doubt it's far less secure than running OpenBSD bare metal. However, public clouds do have one advantage over bare metal, VMs can be made with the mere click of a button, whereas bare metal often takes time to be put online. Having said that, it isn't always that more cost effective. There are very cheap dedicated servers available. Like in Germany, there is Hetzner, Servdiscount, etc. If you need bulk storage, a dedi is often more affordable than a VM/VPS. However, they do oversell bandwith - a lot. I always prefer a dedicated server to run OpenBSD on, which is my preferred OS. However, if you would hold a gun to my head and made me pick a public cloud provider, I'd pick Azure. There have been some developments that sound okay-ish, like confidential computing: https:// arstechnica.com/gadgets/2017/09/azure-confidential-computing-will-keep- data-secret-even-from-microsoft/ As to the exploit mitigation, I really don't know how this upholds after four years or whether this even applies to public clouds - this might be somewhat related at best: https://www.youtube.com/watch?v=OXS8 ljif9b8 I am keen to know whether someone has real hands-on experience with OpenBSD, exploit mitigations and public clouds - I don't. -J. On Thu, 2018-03-08 at 10:51 +, Kevin Chadwick wrote: > We all know Bare metal is more secure (ignoring physical security) > especially with OpenBSD but if you need cost effective global resources > on tap then I believe you need cloud. > > We all know microsoft have a huge user base and userland issues that > are problematic however despite some recent Linux kernel mitigation > adoption attemps, Linux focus on kernel mitigations have been > lacklustre whilst microsoft have been comparatively active albeit > enabling and enforcing mitigations (even ASLR) for all applications by > default has been lacklustre. > > As cloud services are free from microsofts userland it is a *hopeful* > assumption that their security mitigation works applies to their cloud > too whereas I expect it is unlikely with Amazon and Google (AFAIK > Android fairs better than Linux for mitigations due to Google > however??) > > Perhaps OpenBSD mitigations still apply effectively to ec2 instances > and cloud services isolation is good enough to never undermine this, > though I find that hard to believe. Perhaps new processor developments > will solve this issue. > > None of this matters if you cannot get things done. I know there is > OpenBSD AWS client availability but I am unsure about Azure, Google etc. > > Any advice and experience is welcome, Thankyou. >
Cloud Services and kernel mitigations and OpenBSD cli support
We all know Bare metal is more secure (ignoring physical security) especially with OpenBSD but if you need cost effective global resources on tap then I believe you need cloud. We all know microsoft have a huge user base and userland issues that are problematic however despite some recent Linux kernel mitigation adoption attemps, Linux focus on kernel mitigations have been lacklustre whilst microsoft have been comparatively active albeit enabling and enforcing mitigations (even ASLR) for all applications by default has been lacklustre. As cloud services are free from microsofts userland it is a *hopeful* assumption that their security mitigation works applies to their cloud too whereas I expect it is unlikely with Amazon and Google (AFAIK Android fairs better than Linux for mitigations due to Google however??) Perhaps OpenBSD mitigations still apply effectively to ec2 instances and cloud services isolation is good enough to never undermine this, though I find that hard to believe. Perhaps new processor developments will solve this issue. None of this matters if you cannot get things done. I know there is OpenBSD AWS client availability but I am unsure about Azure, Google etc. Any advice and experience is welcome, Thankyou.
