subscribe
subscribe -- Thanks, SplinTer splin...@nastycode.com IRCNow Network https://www.nastycode.com/For all your UNIX/IRC Needs https://www.partnaz-n-crime.com/For all your UNIX/IRC Needs https://waterboy.nastycode.com/FREE Waterboy Gospel Lyrics
Re: shm_unlink and pledge
I should note it's Mono itself calling cpath and vminfo. Changing the runtime to be more pledge friendlier (i.e: SHM dealloc concerns, store boottime for later) would require surgery in it. I was just curious about if SHM manipulation was documented to need a pledge. From: owner-m...@openbsd.org [owner-m...@openbsd.org] on behalf of Theo Buehler [t...@math.ethz.ch] Sent: April 9, 2016 5:35 PM To: misc@openbsd.org Subject: Re: shm_unlink and pledge On Sat, Apr 09, 2016 at 12:52:16PM +0000, Calvin wrote: > Recently, I've created a pledge wrapper for C#. [1] I discovered that pledge > seems to trigger on shared memory manipulations, which aren't mentioned in the > man page for pledge. For example, Mono uses shared memory, which triggers > pledge unless I add the "cpath" promise. (It also uses "vminfo," to check for > boot time, but this seems fairly ays, should SHM operations be mentioned in the man > page, or is this a bug? The pledge manual generally only lists the supported system calls, not the library functions (with only a few exceptions). Not sure the shm_* functions would qualify as they are practically unused in the base system. The shm_*(3) library functions should be supported by the appropriate pledge promises (mostly filesystem manipulations). As is the case with most other libc functions, you need to inspect them and see what system calls they use internally. Your example: shm_unlink(3) calls unlink(2), which, in turn, requires "cpath", so everything is as expected. On the other hand, the shmat(2), shmdt(2), shmget(2) and shmctl(2) system calls are not currently supported by pledge. As far as I know, there are currently no plans of adding support for those. If they are used, you need to make sure the pledge call comes after them. Concerning the "vminfo" pledge: is it possible to fetch that value and store it before you call pledge? > A backtrace of Mono tripping up > on exit without the promise: > > (gdb) bt > #0 0x196ea192113a in unlink () at > :2 > #1 0x196ea18bf018 in shm_unlink (path=Variable "path" is not > available.) at /usr/src/lib/libc/gen/shm_open.c:87 > #2 0x196bc332e085 in > mono_shared_area_remove () from /usr/local/bin/mono > #3 0x196ea191bcc7 in > *_libc___cxa_finalize (dso=0x0) at /usr/src/lib/libc/stdlib/atexit.c:159 > #4 > 0x196ea191a07e in *_libc_exit (status=0) at > /usr/src/lib/libc/stdlib/exit.c:57 > #5 0x196bc312dce8 in _start () from > /usr/local/bin/mono > #6 0x in ?? () > > Oh, and just in case, if > you omit "vminfo" instead: > > (gdb) bt > #0 0x1e868df09eaa in sysctl () at > :2 > #1 0x1e844fa302c0 in mono_free () from /usr/local/bin/mono > #2 > 0x1e844f9deed0 in mono_gchandle_get_target () from /usr/local/bin/mono > #3 > 0x1e844f9da27e in mono_runtime_cleanup () from /usr/local/bin/mono > #4 > 0x1e844f82e63b in mono_get_runtime_build_info () from /usr/local/bin/mono > #5 0x1e844f8964d7 in mono_main () from /usr/local/bin/mono > #6 > 0x1e844f82dce1 in _start () from /usr/local/bin/mono > #7 > 0x in ?? () > > [1] https://github.com/NattyNarwhal/pledge.cs
shm_unlink and pledge
Recently, I've created a pledge wrapper for C#. [1] I discovered that pledge seems to trigger on shared memory manipulations, which aren't mentioned in the man page for pledge. For example, Mono uses shared memory, which triggers pledge unless I add the "cpath" promise. (It also uses "vminfo," to check for boot time, but this seems fairly expected.) Anyways, should SHM operations be mentioned in the man page, or is this a bug? A backtrace of Mono tripping up on exit without the promise: (gdb) bt #0 0x196ea192113a in unlink () at :2 #1 0x196ea18bf018 in shm_unlink (path=Variable "path" is not available.) at /usr/src/lib/libc/gen/shm_open.c:87 #2 0x196bc332e085 in mono_shared_area_remove () from /usr/local/bin/mono #3 0x196ea191bcc7 in *_libc___cxa_finalize (dso=0x0) at /usr/src/lib/libc/stdlib/atexit.c:159 #4 0x196ea191a07e in *_libc_exit (status=0) at /usr/src/lib/libc/stdlib/exit.c:57 #5 0x196bc312dce8 in _start () from /usr/local/bin/mono #6 0x in ?? () Oh, and just in case, if you omit "vminfo" instead: (gdb) bt #0 0x1e868df09eaa in sysctl () at :2 #1 0x1e844fa302c0 in mono_free () from /usr/local/bin/mono #2 0x1e844f9deed0 in mono_gchandle_get_target () from /usr/local/bin/mono #3 0x1e844f9da27e in mono_runtime_cleanup () from /usr/local/bin/mono #4 0x1e844f82e63b in mono_get_runtime_build_info () from /usr/local/bin/mono #5 0x1e844f8964d7 in mono_main () from /usr/local/bin/mono #6 0x1e844f82dce1 in _start () from /usr/local/bin/mono #7 0x in ?? () [1] https://github.com/NattyNarwhal/pledge.cs
Re: What happens to OpenBSD when Secure Boot becomes manditory?
As long as you can enroll your own keys, probably nothing. It's the removal of CSM you have to worry about, as I don't think OpenBSD has an UEFI bootloader. From: owner-m...@openbsd.org [owner-m...@openbsd.org] on behalf of Steve Litt [sl...@troubleshooters.com] Sent: April 2, 2015 5:38 PM To: OpenBSD Misc Subject: What happens to OpenBSD when Secure Boot becomes manditory? Hi all, What happens to OpenBSD when Secure Boot becomes manditory? http://www.pcworld.com/article/2901262/microsoft-tightens-windows-10s-secure-boot-screws-where-does-that-leave-linux.html http://www.pcworld.com/article/2900536/windows-10s-secure-boot-requirement-could-make-installing-linux-a-big-headache.html http://arstechnica.com/information-technology/2015/03/windows-10-to-make-the-secure-boot-alt-os-lock-out-a-reality/ http://news.thewindowsclub.com/microsoft-secure-boot-linux-75539/ http://www.extremetech.com/extreme/201722-linuxs-worst-case-scenario-microsoft-makes-secure-boot-mandatory-locks-out-other-operating-systems http://www.techradar.com/us/news/software/operating-systems/microsoft-s-windows-10-secure-boot-ruling-spells-trouble-for-linux-lovers-dual-booters-1289096 SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance
Re: OpenBSD Tablet-ish
Why OpenBSD on a tablet? On a laptop it makes sense, but OpenBSD is not exactly known for it's touch capability. Even with GNOME 3/KDE, it's still bit of an odd choice for such HW. >What's the smallest, most tablet-ish device I can put OpenBSD on? Want to >travel and stay connected.
gdm error on 5.6-RELEASE inside VMware
I installed gnome and added the items to /etc/rc.conf.local as needed. When I get to GDM, it says : "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again. " And then it stays on a blank X screen. I seem to remember it working on 5.5. # dmesg [truncated duplicate pre-reboot] OpenBSD 5.6 (GENERIC) #310: Fri Aug 8 00:14:24 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1056899072 (1007MB) avail mem = 1020080128 (972MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (364 entries) bios0: vendor Phoenix Technologies LTD version "6.00" date 07/31/2013 bios0: VMware, Inc. VMware Virtual Platform acpi0 at bios0: rev 2 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) S3F0(S3) S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) S10F(S3) S11F(S3) S12F(S3) S13F(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) Core(TM) i5 CPU M 560 @ 2.67GHz, 2660.63 MHz 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,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,NXE,LONG,LAHF,PERF,ITSC 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 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins acpimcfg0 at acpi0 addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 acpibat0 at acpi0: BAT1 not present acpibat1 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: LID_ vmt0 at mainbus0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01 ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01 pci1 at ppb0 bus 1 pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08 pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 64-sector PIO, LBA, 8192MB, 16777216 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus disabled "VMware VMCI" rev 0x10 at pci0 dev 7 function 7 not configured vga1 at pci0 dev 15 function 0 "VMware SVGA II" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) mpi0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: apic 1 int 17 mpi0: 0, firmware 1.3.41.32 scsibus2 at mpi0: 16 targets, initiator 7 ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02 pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 "Intel 82545EM" rev 0x01: apic 1 int 18, address 00:0c:29:d0:e3:3f eap0 at pci2 dev 1 function 0 "Ensoniq AudioPCI97" rev 0x02: apic 1 int 19 ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3) audio0 at eap0 midi0 at eap0: ppb2 at pci0 dev 21 function 0 "VMware PCIE" rev 0x01 pci3 at ppb2 bus 3 ppb3 at pci0 dev 21 function 1 "VMware PCIE" rev 0x01 pci4 at ppb3 bus 4 ppb4 at pci0 dev 21 function 2 "VMware PCIE" rev 0x01 pci5 at ppb4 bus 5 ppb5 at pci0 dev 21 function 3 "VMware PCIE" rev 0x01 pci6 at ppb5 bus 6 ppb6 at pci0 dev 21 function 4 "VMware PCIE" rev 0x01 pci7 at ppb6 bus 7 ppb7 at pci0 dev 21 function 5 "VMware PCIE" rev 0x01 pci8 at ppb7 bus 8 ppb8 at pci0 dev 21 function 6 "VMware PCIE" rev 0x01 pci9 at ppb8 bus 9 ppb9 at pci0 dev 21 function 7 "VMware PCIE" rev 0x01 pci10 at ppb9 bus 10 ppb10 at pci0 dev 22 function 0 "VMware PCIE" rev 0x01 pci11 at ppb10 bus 11 ppb11 at pci0 dev 22 function 1 "VMware PCIE" rev 0x01 pci12 at ppb11 bus 12 ppb12 at pci0 dev 22 function 2 "VMware PCIE" rev 0x01 pci13 at ppb12 bus 13 ppb13 at pci0 dev 22 function 3 "VMware PCIE" rev 0x01 pci14 at ppb13 bus 14 ppb14 at pci0 dev 22 function 4 "VMware PCIE" rev 0x01 pci15 at ppb14 bus 15 ppb15 at pci0 dev 22 function 5 "VMware PCIE" rev 0x01 pci16 at ppb15 bus 16 ppb16 at pci0 dev 22 function 6 "VMware PCIE" rev 0x01 pci17 at ppb16 bus 17 ppb17 at pci0 dev 22 function 7 "VMware PCIE" rev 0x01 pci18 at ppb17 bus 18 ppb18 at pci0 dev 23 function 0 "VMware PCIE" rev 0x01 pci19 at ppb18 bus 19 ppb19 at pci0 dev 23 function 1 "VMware PCIE" rev 0x01 pci20 at ppb19 bus 20 ppb20 at pci0 dev 23 function 2 "VMware PCIE" rev 0x01 pci21 at ppb20 bus 21 ppb21 at pci0 dev 23 function 3 "VMware PCIE" rev 0x01 pci22 at ppb21 bus 22 ppb22 at pci0 dev 23 function 4 "VMware PCIE" re
Re: Wouldn't `daemon_enable=YES` make more sense than `daemon_flags=""` in rc.conf.local?
There's also simplicity of implementation. Even a few more
lines means more bugs. Having the parameters as one and
checking for less cases means simpler software, and simple
is reliable.
From: owner-m...@openbsd.org [owner-m...@openbsd.org] on behalf of Raf Czlonka
[rczlo...@gmail.com]
Sent: January 29, 2015 8:03 PM
To: misc@openbsd.org
Subject: Re: Wouldn't `daemon_enable=YES` make more sense than
`daemon_flags=""` in rc.conf.local?
On Thu, Jan 29, 2015 at 11:16:41PM GMT, openda...@hushmail.com wrote:
> Indeed, don't get me wrong, I use flags all the time as well. I'm just
> arguing for a cleaner separation between startup and configuration for
> a slightly more semantic (and better looking) `rc.conf.local`, ie.:
>
> ftpd_enable=YES
> ftpd_flags="-llSA"
> mountd_enable=YES
> nfsd_enable=YES
> nfsd_flags="-tun 4"
> ntpd_enable=YES
> portmap_enable=YES
> rsyncd_enable=YES
> slowcgi_enable=YES
> unbound_enable=YES
Semantic? Maybe. Better looking? Most certainly not!
Configuration == Startup
Basically, if you are configuring a daemon, that is by using
${daemon_flags}, then you *intend* to *run* it. If you *don't* intend to
run it, *don't* configure it (or hash it out)!
Simple? Simple!
> Thanks for your feedback!
You're welcome :^)
Regards,
Raf
Re: Please help advertise DigitalOcean on OpenBSD Misc (again)
Or you can just use any cheap KVM-based VPS provider that allows you to upload ISOs. -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Constantine A. Murenin Sent: January 21, 2015 2:47 AM To: Steve Shockley Cc: misc@openbsd.org Subject: Re: Please help advertise DigitalOcean on OpenBSD Misc (again) On 20 January 2015 at 18:12, Steve Shockley wrote: > On 1/19/2015 9:06 AM, openda...@hushmail.com wrote: >> >> So please stop by and give us your upvotes. > > > So, is this advertising or SEO? DigitalOcean is a shady provider with a lack of documentation, who doesn't even give you IPv6 address space across their fleet, or in those few locations they do, they do it in violation of all known RFCs and the best practices -- I've heard a rumour that they only give out 16 IPv6 addresses. Why a rumour? Because, as already mentioned, they completely lack the documentation! I don't know why you would want to run OpenBSD on it. If you're just in it for the "OpenBSD" part, just go with real hardware like online.net -- they start at 5,99 EUR/mo, there's not much reason to have to rent a virtual server if dedi is that cheap. Lots of other dedi options at http://lowendcore.com/. With dedi prices that low, virtual hosting for OpenBSD is kinda dead, IMHO. C.
Re: [probably solved] Re: Openbsd broke my hard drive twice! Getting frustrated
I had a machine that didn't like OpenBSD either, it froze during POST or Plop, basically when BIOS services were still usable. It was a BIOS-based system though, and I didn't patch it either. Luckily, I installed on an external disk. -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Henrique Lengler Sent: December 23, 2014 12:56 PM To: misc@openbsd.org Subject: [probably solved] Re: Openbsd broke my hard drive twice! Getting frustrated I figured that my BIOS have a old firmware from 2013. So I decided to update it. At least this my motherboard did good, I easily updated the firmware by plugging a USB with the new firmware. Then It rebooted and yes, it worked as it should. Booted normally with the HDD sata connected. I cannot get satisfied yet, I will install a OS and see if it will still working. I'm in doubt about try openBSD again, I'm afraid everything could happen again. Also is there a explanation to this shitty behavior? My motherboard acted like having a short circuit, making everything stop working because a bad formatted HDD, this is a really unexpected behavior, which made me think the problem was openBSD. By now, thanks for helping. I expect don't need to post anything more here. Regards, -- Henrique Lengler
