[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1777894260848.jpg (2.66 MB, 5184x2916)
2.66 MB JPG
It is not vulnerable to the copy-fail exploit. Just saying.
>>
File: obsd.png (237 KB, 1201x896)
237 KB PNG
>>108750909
>It is not vulnerable to the copy-fail exploit. Just saying.
also OpenBSD
also - microkernels. this is the real long term solution imo
>>
>>108750916
The Hurd soon.
>>
It's funny how much more of an OSX this is than any existing linux distro, really I can barely tell the difference between this and mavericks with an icon pack
>>
File: 1752765931171882.png (701 KB, 1920x1080)
701 KB PNG
>>108750909
crApple can't touch Windows, let alone Qubes OS, it's such shit!
>>
File: locqubes.jpg (200 KB, 1206x857)
200 KB JPG
>>108750916
>also - microkernels. this is the real long term solution imo
the real long term solution is to use virtualization for everything. shit will always be vulnerable, but a 150k loc codebase cand be audited constantly by multiple people and AIs and will never fail. even if you run vulnerable shit on top, only that specific container gets compromised.

just containerize every app like qubes with appvms
>>
>>108751360
This is the endgame of Software killing all of the progress of hardware. We might have slow computers even when we reach the physical limits of silicon if this is the final solution.
>>
>>108751430
what do you suggest man?
there has to be some form of containerization somewhere if you want protection against infection.

you can have a perfect unexploitable kernel written in rust, but if user also runs his ~memory safe~ malware.exe, it doesn't matter really.
>>
How did they get KDE 3 to look like that? Even Trinity gets more incoherent the more you deviate from the base XP-like theme.
>>
>>108750961
Guess it's time to install Gentoo GNU/Hurd
>>
>>108750961
The Hurd is already here. It just needs more GPU support besides Qemu.
>>
A second ram chip flew straight into my hard drive!
>>
>>108752619
sweet. and a billion more drivers.
>>
>>108750916
>Still no TRIM support
No thanks I don't still use 4800 RPM spinning rust
>>
>>108751430
>>108751360
no, virtualization alone is NOT the solution.

Microkernels are most important - so we stop heaving all the damn kernel exploits.

Next, virtualize/lock/isolate the programs.
For example NOVA is microkernel with very good virtualization (afaik)
>>
File: ios_market_share.png (64 KB, 951x1037)
64 KB PNG
>>108750975
The few people in Best Korea who have tech seem to like Apple.
>>
>>108751360
no, containerization is for retards (making slop runnable everywhere) or for bypassing forward compatibility limits. if you want security, resist the bloat and certain models.

you dont solve the incorrect code with containers. its not a solution, its a crunch.
>>
>>108752863
microkernel is not about security, even the author got dragged into security retardation, security may be one for byproducts. microkernels are about separation of concerns into processes, a process model.
>>
>>108750909
kek
>>
can someone hurry up and leak the next version?

https://en.wikipedia.org/wiki/Red_Star_OS#Version_4.0
>>
>>108750909
Why does the UI look like early GNOME 3?
>>
>>108754594
>microkernels are about separation of concerns into processes, a process model.
which is the proper way to make system secure - as it easily isolates all parts of kernel, instead of the most tiny micro part (that one thing you audit really strongly).



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.