OpenBSD 6.5 just came out

>Brother
>Transgender FTM (Female to Male)
>ThinkPad User

>Me
>Non-Transgender Male
>Never had a ThinkPad in my life

Your ftm brother has a giant clit

>BSD license
>full freedom
t. cuck who gives away everything he makes to corporations without any returns

Attached: Screenshot_2019-03-17 My wife's boyfriend moved in with us.png (1261x906, 148K)

How does those pictures come from?
Is this my gf?

slackware works fine

>implying there's anyone enforcing GPL
>implying there's not more company contribution to BSD than GNU
I bet you think systemd is "bloated" too, don't you.

BSD is more restrictive than GPL you absolute retard

Most companies that aren's shady chinks do respect the GPL.
The Linux foundation is sponsored by big companies, the only comparable company supported *BSD is FreeBSD but they might as well just be proprietary cucks.
SystemD is indeed a bloated mess.

>bsd
>more restrictive than gpl
>calling somebody else a retard
jesus christ user respect yourself. if you wanna bait about BSD say something vague about multithreading or filesystems

>>implying there's anyone enforcing GPL
There is: en.wikipedia.org/wiki/GNU_General_Public_License#Legal_status
>>implying there's not more company contribution to BSD than GNU
GNU gets tons of contributions, especially to GCC. FreeBSD is basically glorified game console firmware at this point.

People who use BSD on anything but a server with access to the internet are all just pretentious contrarians eho want to feel even more special snowflakes using an obscure system, because using a relatively unpopular system like GNU/Linux isn't enough, and want to just feel like the kool kids even then.
Prove me wrong.

Why do people keep saying OpenBSD 6.5 came out? In the website it says that it will come out in May.

Then you wake up and realized everyone not using the GPL are the turbofaggots of our time and felt an insatiable need of getting punch'd in the face by a frog cartoon

Attached: 1545842160636.jpg (250x241, 25K)

Can I install it on an eMMC drive yet? Does it have 802.11ac drivers? I want to use OpenBSD but it didn't detect my hardware the last time I tried.

Look at this retard, this is the common userbase of OpenBSD, the OS that can't even saturate a 100mbit link. It was planned by a retard to be made by retards targeted at retards. Don't even get me started on the fact that it has nothing better over any other distro. So, in essence, if you install OpenBSD you're pretty much admitting to the world that you're a proud retard.

Attached: 1553217925433.jpg (480x459, 16K)

Meanwhile the download link takes you to a page of 6.5 links.

>this is the common userbase of OpenBSD
Pretty sure he's one of your fellow GPL zealots
>the OS that can't even saturate a 100mbit link
We already covered this in another thread, you can stop any time now.

HP’s are trash, why are you keeping that dog?

>check vault 7
>not a single tool or hack for OpenBSD

No shit. Nobody uses OpenBSD.

Millions of people use it, you’re just salty because you haven’t managed to shit it up with backdoors yet.

I'm pretty sure the answer to that second question is still no, but I could be wrong.

Nope, that's the price to pay to be secure against 802.11ac driver issues.

both options are equally austistic

Wow that vacation-style treatment really did a number on that old glownigger didn’t it?

OpenBSD doesn't support anything, so you shouldn't support it.

It's supported everything I've tried it on, from UMPCs to touchscreen laptops with styli to normal desktops

>complains about corporations
>IBM bought redhat
>Microsoft literally buy their way into Linux foundation
Oh the irony.

I'm not so worried about corporation stealing good clean codes, I'm more worried about corps injecting backdoors through bugs in a massively bloated, unauditable source codes.

openbsdfoundation.org/contributors.html
Speaking of selling out

That’s retard talk.

FreeBSD has ZFS.

Just installed it on a Toughbook CF-U1 and everything works great, got the stylus calibrated and everything. Only thing I can’t figure out is how to do middle and right clicks.

Those are donors not board members like MS and Google and IBM and Intel are with Linux.

Oh look, the opposite of truth troll and the retarded tripfaggot that I forgot to filter arrived.

>hurr durr no support xd

Then why does my state-of-the-art, IoT-Ready™ Dishwasher runs OpenBSD. What's your pathetic excuse now?

>schizos in this thread claiming that the BSD license equals companies taking code from OpenBSD without giving back
>Microsoft takes OpenBSD security mitigations
>they fund the project back in return

Thanks for proving the retardation of the GPL-zealots.

Attached: 54354354.png (853x560, 94K)

>n-no! it's different i swear!

Attached: 1548991810478.png (640x640, 4K)

pic realted

Attached: 543545445435345.jpg (2048x1536, 640K)

>Microsoft takes OpenBSD security mitigations
I'm pretty sure they didn't disable hyperthreading on Windows, I mean, that's a pretty stupid way of dealing with bugs, you fix your roof when it leaks, not tear the whole building off.

It is different you fucking imbecile, Linux foundations is just a facade for all the big corps that control Linux developments and Torvalds is Red Hat's bitch.

The OpenBSD page you linked are just donors.

You are comparing apples with oranges, fucking imbecile.

Is this the OS that let's Sony and Apple play with its pussy for free? Lmao

Yep, surely those evil companies climbed to the top by donating away their money for no return whatsoever.

Attached: 1EFA85F2-7B7C-42C7-B7FE-496208CE5CA6.jpg (1200x1500, 309K)

>disabling HT is OpenBSD's only security mitigation
You're not even trying

Where did I say that? Although if that's an indicator on the way they think then it's safe to say that they can't be trusted when they say their code is secure, you can't have bugs if write no code after all, am I right?

ipsec(4): Started by John Ioannidis, Angelos D. Keromytis, Niels Provos, and Niklas Hallqvist, imported February 20, 1997. OpenBSD was the first free operating system to provide an IPSec stack.
inet6(4): First complete integration and adoption of IPv6 led by "Itojun" (Dr. Junichiro Hagino) [WIDE/KAME], Craig Metz [NRL], and Angelos D. Keromytis starting Jan 6, 1999. Almost fully operational Jun 6, 1999 during the first OpenBSD hackathon. OpenBSD 2.7.
Privilege separation: First implemented by Niels Provos and Markus Friedl in OpenSSH in March 2002, released with OpenBSD 3.2. The concept is now used in many OpenBSD programs, for example bgpd(8), dhclient(8), dhcpd(8), dvmrpd(8), eigrpd(8), file(1), httpd(8), iked(8), ldapd(8), ldpd(8), mountd(8), npppd(8), ntpd(8), ospfd(8), ospf6d(8), pflogd(8), radiusd(8), relayd(8), ripd(8), script(1), smtpd(8), syslogd(8), tcpdump(8), tmux(1), xconsole(1), xdm(1), Xserver(1), ypldap(8), pkg_add(1), etc.
Privilege revocation: Related to the work on privilege separation, some programs were refactored to drop privileges while holding onto a tricky resource such as a raw socket, reserved port, or modification-locked bpf(4) descriptor, for example ping(8), traceroute(8), etc.
Stack protector: Developed since 2001 as "propolice" by Hiroaki Etoh. Integrated, and implemented for additional hardware platforms, by Miod Vallat and Theo de Raadt. OpenBSD 3.3 was the first operating system to enable it systemwide by default.
W^X: First used for sparc, sparc64, alpha, and hppa in OpenBSD 3.3. Strictly enforced by default since OpenBSD 6.0: a program can only violate it if the executable is marked with PT_OPENBSD_WXNEEDED and it is located on a filesystem mounted with the wxallowed mount(8) option.

You implied it

GOT and PLT protection by ld.so: first done as part of the W^X work in OpenBSD 3.3, by Dale Rahn and Theo de Raadt. The GOT and PLT regions are read-only outside of ld.so itself. Extended to the .init/.fini sections (constructors and destructors) in OpenBSD 3.4.
ASLR: OpenBSD 3.4 was the first widely used operating system to provide it by default.
gcc-local(1) __attribute__((__bounded__)) static analysis annotation and checking mechanism: Started by Anil Madhavapeddy on June 26, 2003 and ported to GCC 4 by Nicholas Marriott. First released with OpenBSD 3.4.
malloc(3) randomization implemented by Thierry Deval. Guard pages and randomized (delayed) free added by Ted Unangst. Reimplemented by Otto Moerbeek for OpenBSD 4.4.
Position-independent executables (PIE): OpenBSD 5.3 was the first widely used operating system to enable it globally by default, on seven hardware platforms. Implemented in November 2008 by Kurt Miller and enabled by default by Pascal Stumpf in August 2012.
Random-data memory: the ability to specify that a variable should be initialized at load time with random byte values (placed into a new ELF .openbsd.randomdata section) was implemented in OpenBSD 5.3 by Matthew Dempsky.
Stack protector per shared object: using the random-data memory feature, each shared object was given its own stack protector cookie in OpenBSD 5.3 by Matthew Dempsky.
Static-PIE: Position-independent static binaries for /bin, /sbin and ramdisks. Implemented for OpenBSD 5.7 by Kurt Miller and Mark Kettenis.

SROP (sigreturn(2) oriented programming) mitigation: attacks researched by Eric Bosman and Herbert Bos in 2014, solution implemented by Theo de Raadt in May 2016, enabled by default since OpenBSD 6.0.
Library order randomization: In rc(8), re-link libc.so, libcrypto, and ld.so on startup, placing the objects in a random order. Theo de Raadt and Robert Peichaer, May 2016, enabled by default since OpenBSD 6.0 and 6.2.
Kernel-assisted lazy-binding for W^X safety in multi-threaded programs. A new syscall kbind(2) permits lazy-binding to be W^X safe in multi-threaded programs. Implemented for OpenBSD 5.9 by Philip Guenther in July 2015.
Process layouts in memory tightened to remove execute permission from all segmented, non-instruction data and to remove write permission from data that is only modified during loading and relocation. By combining the RELRO (Read-Only after Relocation) design from the GNU project with the original ASLR work from OpenBSD 3.3 and strict lazy-binding work from OpenBSD 5.9, this is applied to not just a subset of programs and libraries but rather to all programs and libraries. Implemented for OpenBSD 6.1 by Philip Guenther in August 2016.
Use of fork+exec in privilege separated programs. The strategy is to give each process a fresh & unique address space for ASLR, stack protector -- as protection against address space discovery attacks. Implemented first by Damien Miller (sshd(8) 2004), Claudio Jeker (bgpd(8), 2015), Eric Faurot (smtpd(8), 2016), Rafael Zalamena (various, 2016), and others.

trapsleds: Reduction of incidental NOP instructions/sequences in the instruction stream which could be useful potentially for ROP attack methods to innaccurately target gadgets. These NOP sequences are converted into trap sequences where possible. Todd Mortimer and Theo de Raadt, June 2017.
Kernel relinking at boot: the .o files of the kernel are relinked in random order from a link-kit, before every reboot. This provides substantial interior randomization in the kernel's text and data segments for layout and relative branches/calls. Basically a unique address space for each kernel boot, similar to the userland fork+exec model described above but for the kernel. Theo de Raadt, June 2017.
Rearranged i386/amd64 register allocator order in clang(1) to reduce polymorphic RET instructions: Todd Mortimer, November 20, 2017.
Reencoding of i386/amd64 instruction sequences to avoid embedded polymorphic RET instructions. Enhancements to clang(1) Todd Mortimer, April 28, 2018 and onwards.
MAP_STACK addition to mmap(2) allows opportunistic verification that the stack-register points at stack memory, therefore catching pivots to non-stack memory (sometimes used in ROP attacks). Theo de Raadt, April 12, 2018.
RETGUARD is a replacement for the stack-protector which uses a per-function random cookie (located in the read-only ELF .openbsd.randomdata section) to consistency-check the return address on the stack. Implemented for AMD64 and ARM64 by Todd Mortimer in OpenBSD 6.4.

Whatever you say.

To ensure that novice users of OpenBSD do not need to become security experts overnight (a viewpoint which other vendors seem to have), we ship the operating system in a Secure by Default mode. All non-essential services are disabled. As the user/administrator becomes more familiar with the system, he will discover that he has to enable daemons and other parts of the system. During the process of learning how to enable a new service, the novice is more likely to learn of security considerations.

This is in stark contrast to the increasing number of systems that ship with NFS, mountd, web servers, and various other services enabled by default, creating instantaneous security problems for their users within minutes after their first install.

>claims to be the most secure OS
>is written in an unsafe language
o i am laffin

>points finger at the moon

you can polish a turd to a high shine but at the end of the day it's still going to be a turd

>points finger at padded room language which also professes to be a systems language

>no return whatsoever.
An OS with unrestrictive license lol.

So you're saying that OpenBSD accepts code from those evil companies? Now that is a cause for concern.

No one wants to hack into teenage autists to steal their software that is already free, or their porn stash they got from torrent.
Diplomats, spies, etc. obviously don't use OpenBSD, which is why no one bothers attacking it.

Everybody wants to hack everybody.

based inappropriate contraction poster

Attached: Emily Rudd t1pt6XH.png (851x470, 643K)

> accepts code from those evil companies
Literally the opposite, evil corps pay them to make a secure OS under business friendly license.

lmao

Attached: 1522459498729.jpg (500x375, 47K)

"Secure" OS you say? Paid for by evil companies? Sure.

>HURR DURR EVIL CORPORATIONS CONTROL OPENBSD, IT'S NOT LIKE THE MAIN DEVELOPMENT OCCURS IN THEO'S BASEMENT
>LINUX ON THE OTHER HAND IS UNCOMPROMISED, LET ME SUCK YOUR DICK CANONICAL REDHAT IBM AND GOOGLE! MICROSOFT

Seething.

Attached: 1531678373490.png (600x536, 253K)

It's already past bedtime. Go to sleep or dad will use the belt again.

That came out of left field, do you want me to call the social service for you?

Is there any other actual reason to install this besides street cred on desktop threads?