9 ms·
OpenBSD 7.5
- a-french-anon 3y agoDoes anyone know if there's any plan to reintroduce xattrs in FFS2? Probably the only modern UNIX without it in its main FS(s). Or for a more standard/modern FS like XFS (I don't expect OpenBSD to go for ZFS bloat).
- ByQuyzzy 3y agoThey made their FFS 64-bit. That’s what you get. And FFS is THE standard. In short no. Also they removed softupdates, code was old and slow and was holding back the quest to unlock.
- znpy 3y ago> And FFS is THE standard What's that supposed to mean? ed is the standard text editor, yet we don't actually expect anyone to use it (let alone know it...)
- ByQuyzzy 3y agoIt means no meme filesystems will be tolerated. There are tons of operating systems out there if you don’t like ffs.
- jabl 3y ago> They made their FFS 64-bit. What does this mean? 64-bit inode numbers? 64-bit timestamps? Something else? > Also they removed softupdates, Shame in a way, I remember reading McKusick's paper and being impressed. But I guess it's the antithesis of batching, which turned out to be more important for performance than avoiding the extra I/O due to journalling. Also the implementation was AFAIU fearsomely subtle and tricky.
- ByQuyzzy 3y agoRead the manual page, I’m not going to type it all in here.
- volkadav 3y agohttps://unixgeeks.net/posts/2022/10/check-for-openbsd-ffs-filesystems-version/ https://unixgeeks.net/posts/2022/10/check-for-openbsd-ffs-fi... may be helpful. tl;dr - timestamps and blocknumbers are 64b in FFS2, intro'd in 4.2 and made the default (more or less) in 6.7
- yjftsjthsd-h 3y ago> Or for a more standard/modern FS like XFS (I don't expect OpenBSD to go for ZFS bloat). At some point, I think I heard that they might use HAMMER2, which would be nice.
- alberth 3y agohttps://github.com/kusumi/openbsd_hammer2 https://github.com/kusumi/openbsd_hammer2 A developer was making active progress, but hasn't made any commits since Dec
- jmclnx 3y ago>plan to reintroduce xattrs in FFS2? With unveil(2) and maybe pledge(2), I do not think there is a need for Extended Attributes. To me, all it does is add complexities not really needed in OpenBSD.
- omnibrain 3y agoNo song this time.
- dbolgheroni 3y agoSometimes the song release comes after the software release.
- bheadmaster 3y agoThe removal of generic syscall(), and introduction of pinsyscalls() which registers the precise entry location of every system call used by a program, makes me think of some kernel-level ABI issues that Linux has. In particular, kernel ABI is the main stable interface that Linux exposes - and all applications can just use syscalls directly without having to interface with the libc at all. However, that means that kernel must not change its ABI lest it risks breaking compatibility, and each functionality that isn't implemented inside of the kernel (e.g. GUI stuff) cannot be implemented completely portably. However, using pinsyscalls(), a kernel can make sure that syscalls can only be called from the libc - therefore, making the libc de-facto ABI! Which allows for much more freedom in changing kernel ABI, as long as the libc follows through. Perhaps this way the system can go away from the syscall-level ABI and move over to the libc ABI / shared library ABI?
- newpavlov 3y agoHonestly, I think that making libc THE system interface is a mistake. Ok, I understand issues with the Linux approach of exposing raw syscalls (though it works well enough in practice and ossification could be amended by some kind of syscall versioning scheme), but why in the world can't you introduce libsystem/libsyscall/libopenbsd which would contain only "syscall" functions? Why do you need all the C junk in a library for talking with OS?
- resuresu 3y ago[dead]
- tedunangst 3y agoNothing stops you from making your own libsystem. Or still just making syscalls. Nobody seems to understand how this feature works, even though it's quite simple. The process asks the kernel to only allow system calls from one segment. If you don't like that, don't ask for it.
- newpavlov 3y agoLack of stable syscall ABI is what stops me. It can be only done by OS developers.
- dfc 3y agoDoes anyone know the story behind the artwork? Puffy does not look so good.
- gattilorenz 3y agoVaguely reminiscent of https://en.wikipedia.org/wiki/Creature_from_the_Black_Lagoon#/media/File:Creature_from_the_Black_Lagoon_poster.jpg https://en.wikipedia.org/wiki/Creature_from_the_Black_Lagoon...
- greyface- 3y agohttps://en.wikipedia.org/wiki/Ozymandias https://en.wikipedia.org/wiki/Ozymandias
- NortySpock 3y agoIf you prefer to hear it from a excellent narrator: https://youtu.be/xbLdz1kcQNw https://youtu.be/xbLdz1kcQNw
- nullindividual 3y agoTex is an awesome narrator. Thanks for linking! “Comrade Stalin says there’s bread on the Finnish line”
- dfc 3y agoDo you know this to be the inspiration for the artwork or best guess?
- ch0ic3 3y agoFor anybody wondering about the new pinsyscalls(2) suggest having a look at https://isopenbsdsecu.re/mitigations/pinsyscall/ https://isopenbsdsecu.re/mitigations/pinsyscall/ . To be clear: I use OpenBSD on all my external-facing systems. I trust it infinitely more than any GNU/Linux distribution (esp with the recent xz.. "issue"), but I think it's important to do your own research and see what the contrarians say from time to time.
- calvinmorrison 3y agoDo you think there's more value in combining 2 heterogenous systems (like openbsd up front, linux behind) than using one 'more secure' system throughout? I feel like the number of critical issues that have faced two systems at once is far fewer than a single system. Also I think it shows value in having independent implementations of standards. If you have 5x different xz tools or C compilers or Javascript engines, the threat is chopped in half, plus you can easily compare reference outputs between them (RE: on trusting trust)
- wannacboatmovie 3y agoIt's common practice for the ultra paranoid to use two firewalls, from different vendors, back to back, for this reason.
- terlisimo 3y agoThere is a name for this https://en.wikipedia.org/wiki/Swiss_cheese_model https://en.wikipedia.org/wiki/Swiss_cheese_model
- ch0ic3 3y agoFor sure! An argument in OpenBSD circles is that contrary to popular belief one can have security through depth. This means that even though you'll never be 100% secure you can definitely make an attacker's job harder and their life more miserable. Of course, if the NSA wants to attack you then they'll probably succeed, but for your average script kiddy / botnet scanner / worm exploiting some vulnerability having multiple layers might be enough of a deterrent. I'm not a security person but I also think a lot of malware damage comes from companies / users using misconfigured or outdated software. As such, if you were a sysadmin, knew what you were doing and had the time, then running GNU/Linux is probably fine, but I'm not super knowledgeable. I just want to host a website or run a tor-relay on a VPS and not have to worry about updating my system as soon as some 0-day is announced in glibc or systemd; even if it's in the service itself, my hope is that by using a non-mainstream OS the exploit might not initially target it, hence giving sufficient time to see the news somewhere and patch / update.
- jacksonhacker 3y ago[dead]
- The_Colonel 3y ago> Copyright 1997-2024, Theo de Raadt. Caught my eye. I'm vaguely aware that Theo de Raadt is not the paragon of modesty, but would still expect a more "communal" copyright. Or is OpenBSD largely a one-man show?
- ninjin 3y agoOne would probably have to define "one-man show". But, no, Theo does not write most of OpenBSD's code. Although he certainly is the leader of the project. If the copyright statement bothers you, I can recommend the announcement e-mail (see "THANKS" in particular): https://marc.info/?l=openbsd-announce&m=171228270018970&w=2 https://marc.info/?l=openbsd-announce&m=171228270018970&w=2 You will also find separate copyright statements in a lot of the source files and many carry the name of their authors.
- gtirloni 3y agoUh? Of course it's not a one-man show. https://github.com/search?q=repo%3Aopenbsd%2Fsrc%20copyright&type=code https://github.com/search?q=repo%3Aopenbsd%2Fsrc%20copyright...
- jmclnx 3y agoAre you referring to the text in the WEB Page ? https://www.openbsd.org/75.html https://www.openbsd.org/75.html I think that is because Theo de Raadt maintains the Site. As someone said the source files have their own copyright comments.
- phone8675309 3y agoI believe that copyright notice is for organizing the layout of the actual distribution images (ISO, etc) and for the music and artwork (though work-for-hire), not that Theo de Raadt is claiming copyright over all of the code in the distribution.
- ByQuyzzy 3y agoThe advantage of Theo being dictator is that big companies can’t take over like they did with Linux.
- shrubble 3y agoIs the artwork a reference to the poem, Ozymandias?
- rydgel 3y agoit is
- another2another 3y agoAlways interesting to see the amount of work going into LibreSSL, but I'm not sure how much use it gets outside of OpenBSD which seems a bit of a shame.
- anonymous_union 3y agoapple ships it
- lemper 3y agowhat i enjoy the most when openbsd has a new release is their new song. my favourite is the legend of puffy hood. https://www.openbsd.org/lyrics.html https://www.openbsd.org/lyrics.html
- kstrauser 3y ago“Pond-erosa Puff” lives in my head. I think we’ve been using this a while, huh?
- dyingkneepad 3y agoDoes anybody know what are the major companies employing OpenBSD developers these days? To what level are they invested?
- alberth 3y agoI think this will be difficult to know, because IIRC, to commit to OpenBSD you must use an @openbsd.org account. So it's not like you can just look at the commit log and search for private company @names http://cdn.openbsd.org/pub/OpenBSD/Changelogs/ http://cdn.openbsd.org/pub/OpenBSD/Changelogs/
- whitepoplar 3y agoCan anyone comment on the OpenBSD security model in 2024? Is it more secure than a minimal linux distro (or one configured to be so) such as Ubuntu Minimal or Debian Stable? I'm finding it quite difficult to compare OS "security" these days, whatever that means. Everyone seems to have their own crackpot opinions. If anyone with a security background could chime in, I'd be forever grateful.
- ranger_danger 3y agoAs far as I know, all of these statements are still true: https://web.archive.org/web/20220227172102/https://madaidans-insecurities.github.io/openbsd.html https://web.archive.org/web/20220227172102/https://madaidans... https://isopenbsdsecu.re/ https://isopenbsdsecu.re/
- yjftsjthsd-h 3y ago> OpenBSD has no Mandatory Access Control (MAC) system like AppArmor or SELinux which prevents you from fully locking down user space. Isn't that pledge? And in general, I observe that lots of people are happy to say that OpenBSD's protections are no good, but somehow they can't be bothered to actually show a working exploit.
- MuffinFlavored 3y ago> > OpenBSD has no Mandatory Access Control (MAC) system like AppArmor or SELinux which prevents you from fully locking down user space. Would this have mattered/stopped/mitigated the `xz` problem if systemd spawns opensshd and transiently loads infected .so shared objects?
- yjftsjthsd-h 3y agoI'm not really super confident, but I think the problem is that sshd has to be able to spawn user sessions and those users are generally not supposed to be (meaningfully) confined by selinux or whatever. So I suspect that it wouldn't have helped, because a compromised sshd is necessarily in the prefect place to MitM or forge a session regardless of extra constraints. But take with a grain of salt.
- zvmaz 3y agoIs OpenBSD used in industry, in critical systems, etc.? If so, what are some examples of its use? Truly interested to know.
- mrweasel 3y agom:tier (https://www.mtier.org/refs/ https://www.mtier.org/refs/) claims to have customers in the oil and gas industry.
- tranxen 3y agoThere was this interesting talk [1] about how this ISP uses OpenBSD as BGP control plane. I used to heard that OpenBSD was often used as Internet facing middlebox (like firewalls/proxy/network load balancer) because of how good pf and relayd are. But it would surprise me if it would still be the case nowadays, OpenBSD seems to perform poorly [2] in terms of network throughput compared to the competition (VyOS/VPP). And I don't think this 7.5 upgrade helped a lot regarding this topic. [1]: https://gregsowell.com/?p=7069 https://gregsowell.com/?p=7069 [2]: https://ipng.ch/s/articles/2021/07/19/pcengines-apu6.html https://ipng.ch/s/articles/2021/07/19/pcengines-apu6.html
- binkHN 3y ago> https://ipng.ch/s/articles/2021/07/19/pcengines-apu6.html https://ipng.ch/s/articles/2021/07/19/pcengines-apu6.html Nice little write-up. I found it interesting that OpenBSD outperformed Linux, but DPDK-based systems blew the roof off.
- tranxen 3y agoHopefully one day DPDK will be ported to OpenBSD. Altough I think OpenBSD also lack proper network card documentation.
- sjaak 3y agoJust upgraded my small homeserver sysupgrade; sysmerge; pkg_add -u; Done! What a delight!
- tux2bsd 3y ago[dead]
- brynet 3y agoAnnouncement mail: https://marc.info/?l=openbsd-announce&m=171228270018970&w=2 https://marc.info/?l=openbsd-announce&m=171228270018970&w=2
- tux2bsd 3y ago[dead]
- Panino 3y agoI'm currently switching my Go code to Rust in part because of the syscall related Go trouble: > Users of syscall(2), such as Perl and the Go programming language were converted to use the libc functions. I think the following may still need to be converted: * unix.Pledge from golang.org/x/sys/unix * unix.Unveil from golang.org/x/sys/unix * terminal.ReadPassword from golang.org/x/crypto/ssh/terminal
- qweqwe14 3y agoDidn't Go already realize that it can't use direct syscalls on anything other than Linux? They made some mistakes in the past but by this point I think they learned their lesson. On Linux, using direct syscalls is a good idea, since it's the stable userspace-kernel interface. There's really no need for libc on Linux, each language should just implement it's standard library on top of syscalls.
- int_19h 3y agoThey knew it all along, since it's well-documented. But they don't seem to care about it until they get burned. Which first happened on macOS, so that was switched; then OpenBSD. This was previously discussed at length here: https://news.ycombinator.com/item?id=25999623 https://news.ycombinator.com/item?id=25999623
- pjmlp 3y agoLike many other decisions, and as it happens with other technologies, reaching for it is a decision that outweights my preferences, given how it has managed to become unavoidable in many CNCF and DevOps products.
- akira2501 3y agoIronically the libc itself fails to document how large of a stack you should have before you call into it. Which is why go, having goroutines, tried to avoid it in the first place. They didn't "get burned" they were "trying to provide a nice feature that wasn't as broadly compatible as they had hoped."