21–30 of 62 posts
Busy upgrading machines now, lots of nice new things. Looking forward to checking out the new execpromises in pledge. I use pledge in all my C stuff and have added it to a few other apps. Thanks OpenBSD devs!
Of all the priviledge dropping mechanisms I have encountered, pledge seemed the most comprehensible.
and get a better return in 7days,i can help you manage your account with the
minimum of $300 assure you get $3300.Contact us here $200 get $3200 $300 get $4300 $500 get $6400 $1000 get $10,000 $1,500 get $15,400 $2000 get $20,800 All in weekly profits and 100% guaranteed.(payout is assured)you can also
monitor your account whenever you want. contact us on besonmark458@gmail.com
sshd(8): Add "expiry-time" option for authorized_keys files to allow for expiring keys. -- hooray! Can someone help explain what the "routing domain" is?
man rdomain to start, though unfortunately you kind of need to already understand rdomains to fully understand the docs. Basically it's a network partitioning/virtualization tool. Two computers can have two routing tables. rdomains lets one computer have two routing tables. Each process is in one rdomain or another which determines where its traffic goes and how it sees the network.
Earlier quoted context omitted.
man rdomain to start, though unfortunately you kind of need to already understand rdomains to fully understand the docs. Basically it's a network partitioning/virtualization tool. Two computers can have two routing tables. rdomains lets one computer have two routing tables. Each process is in one rdomain or another which determines where its traffic goes and how it sees the network.
Interfaces can be places into rdomains aswell
From the release notes: > o Support the sun4v hypervisor interrupt cookie API, adding support for SPARC T7-1/2/4 machines. Who is running OpenBSD on a big expensive SPARC T7 and why? I'm genuinely curious as to what possible use cases there are which make this a desirable combination.
It was probably for testing, but that platform supports partitioning up the hardware through LDOMs, which OpenBSD supports as both a host and guest. https://www.tedunangst.com/flak/post/OpenBSD-on-a-Sun-T5120 (Not expired, Ted runs his own CA) http://man.openbsd.org/man8/sparc64/ldomctl.8
I notice the new Broadcom Wifi bwfm(4) drivers. Anyone with better knowledge of the project know what hardware is supported by that? The manpage doesn't mention specific chips: https://man.openbsd.org/bwfm.4
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_... indicates: static const struct pci_matchid bwfm_pci_devices[] = { { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM43602 }, { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM4350 }, }; those are hex codes defined in: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/pci... as: vendor BROADCOM 0x14e4 Broadcom product BROADCOM BCM4350 0x43a3 BCM4350 prod…
Busy upgrading machines now, lots of nice new things. Looking forward to checking out the new execpromises in pledge. I use pledge in all my C stuff and have added it to a few other apps. Thanks OpenBSD devs!
Interesting that they just changed the interface from `int pledge(const char * promises, const char * paths[]);` to `int pledge(const char * promises, const char * execpromises);`. I guess that is the power they have by being a BSD and integrated system, they do not worry about userland compatibility.
Earlier quoted context omitted.
It was probably for testing, but that platform supports partitioning up the hardware through LDOMs, which OpenBSD supports as both a host and guest. https://www.tedunangst.com/flak/post/OpenBSD-on-a-Sun-T5120 (Not expired, Ted runs his own CA) http://man.openbsd.org/man8/sparc64/ldomctl.8
unrelated, but I found his post about running his own CA quite interesting: https://www.tedunangst.com/flak/post/moving-to-https
>Do we really want an internet where the use of encryption requires authorization?
No, it doesn't require, it provides identification and that's a huge benefit. We are all far better by having it as a standard. Just configure Let's Encrypt and stop annoying your readers.
From the release notes: > o Support the sun4v hypervisor interrupt cookie API, adding support for SPARC T7-1/2/4 machines. Who is running OpenBSD on a big expensive SPARC T7 and why? I'm genuinely curious as to what possible use cases there are which make this a desirable combination.