HN Simulatornew | past | comments | lists | submit | fguerraz's commentslogin

Uncle Lex seems quite the hero!

So that people don't just reach out for it thinking it's the standard best model I guess. Opus is still, IMHO, the best intelligence per dollar, token, and speed.

Give it 20 more years, it takes time for ecosystems to rebuild.

OpenBSD shows nothing. It’s insignificant and nobody is actively looking for flaws in it.


OpenBSD gave you OpenSSH and many interesting technologies. Hardly “insignificant “…


It did, yet almost no one uses the OS itself.


OpenBSD is a software distribution, that can be used as an operating system. To claim OpenBSD is “insignificant” is simply wrong.

OpenBSD components are widely used. OpenSSH is one example used by most of HN.

OpenBSDs libc is also used by Android as another example. Also widely used.


Specific parts of the system are significant. The system as a whole is insignificant. I have no hate for OpenBSD, but those significant parts would find a new home if it didn't exists.


Doubtful. They only EXIST because of the OpenBSD team.

Time and time again, we see how ports of OpenSSH has vulnerabilities not found in OpenBSDs version.

https://news.ycombinator.com/item?id=50377221


You might be technically correct about the OpenBSD project as a whole, but please remember the topic at hand which is exploit in kernels. OpenBSD's kernel truly is insignificant beyond being a source of pride for its very vocal circle jerk.

It is enough that it is good and that it has a community that uses it.

Not everything needs to be dominant to be successful. That's a pure USian way of thinking.

In fact, we are much better of with it existing. Think of it as a safeguard in case Linux gets overwhelmed or we need to migrate in a rush.


The point is that no one has spent 1.2M dollars worth of tokens finding bugs in it. If they did, I am sure they would find many bugs.


Given current AI trends, it would not surprise me one bit if they actually try exactly this scenario in the following weeks.

Then we can compare with actual data.


If it’s freed it can be reallocated, so then you have pointers to the same area of memory used for completely different data structures, and this can go very wrong


I get the principle - what I struggle to find is concrete examples of how it can practically be used.

How do you know which pointer (as I say, especially if it’s in the heap)? And I know it can go wrong - but how do you do more than just crash the kernel?

In OOB writes in a stack variable it’s completely clear to me. For other situations I’d love to find real and clearly explained exploits of past UAF or OOB vulnerabilities.


Getting the right thing allocated in the right place to exploit a UAF is usually very very tricky. For a defender we just need to know it's probably possible and therefore we patch the bug, but the attacker still has a difficult job to do even already knowing a UAF bug.

The simplest thing you could try to do is allocate several more of the same type of object and hope one of them lands at the same memory address. For example if you can UAF a web app's user session and keep it open for a long time period (not true in the TCP bug), you might try to wait until an admin happens to log in with their session at the same address, then use their admin session.

Or you can allocate a lot of something else objects and hope a certain field overlaps, like a function pointer if you can write to it. Like suppose you can get some kind of authentication callback pointer to overlap where your packet sequence number was, maybe you can send a certain number of packets to make it point to the return instruction and skip the authentication.


One technique is to just spam the heap full of a certain object you're hoping will overlap it. E.g. if you want to affect a connection object, you might try to open one million simultaneous connections, then touch the UAF object, then check each connection to see if it got messed up. This is called heap spraying and it's often seen in JavaScript vulnerabilities, a bit less in network vulnerabilities since it's easier to allocate a million Uint8Arrays than to open a million TCP connections.


A web search for "exploit chain uaf" found me a few real-world and a few tutorial examples, though I don't know which are good.

At a high level, though: once you've gotten a new object allocated where the old one was, you now have two different views of the same bit of memory. You use valid operations on one view to put the other one into a corrupted state. For example: in a unixlike kernel, maybe one view has a field containing a function pointer (for method dispatch, essentially). You read that field using the other view, use it to deduce something about the target's memory layout, write a new value to the pointer, then use the field via the first view to cause execution to jump to a location you control.


Maybe check https://github.com/sarabpal-dev/IonStack-S22U It has a full chain reproduction of the use-after-free vulnerability that grants you root on Samsung phones with a locked bootloader.


I don't think a UAF on its own allows control hijacking in an exploit. You will need further logic bugs or the ability to legitimately or illegitimately control memory, either via further requests / function calls, OOB writes and such. And it will always be extremely specific to the application vulnerable.

For example, I remember an exploit workshop around reuse of passwd entries. The vulnerable would validate a passwd entry for a non-root user, use it a bit, and later on free and zero it out for security purposes... except it then looked at the passwd entry again in some conditions. Suddenly, the uid was non-zero at first, and zero later on, so later decisions assumed the user was root.

In a more concurrent situation, a possible vulnerability was a shared cache of these passwd entries. It wouldn't zero them out anymore, but you could create a race condition of starting requests as user A, and then hammering requests as user B, so you'd end up mixing up the permission contexts of these users. Because the passwd entry that had been released back to the pool was overwritten, and then re-read with the value from another context.

The necessary line of thinking tends to be very different from thinking about program code regularly.


I highly recommend this episode of BBC In Our Time: https://www.bbc.co.uk/programmes/b080wbrq


I love this episode so much. Very informative and the slowly paced conversation is calming, with no ads or sudden outbursts to break the rythem.

Actually, I have this very episode downloaded on my phone and whenever sleep eludes me, I play it. I never lasted more than 30 minutes. I must've listened to it hundreds of time by now.


Can we kick SMB implementations out of the kernel please? If not, can we please get PHP mainlined in the kernel?


It is in a module, so it doesn't create risk for anyone that isn't loading that module. And most distros don't use it by default, you have to go out of you way to configure it.

I do wish distros would start moving more kernel modules into separate packages so it is obvious to security scanners and individual users whether a CVE impacts them or not. I'm sure I've rebooted my computer many times due to kernel packages updates when it probably wasn't needed. And put off security updates for a few days until I was able to reboot, when I could have installed them right away.


SMB was "imported" into the kernel as an optimization for the user-space version - heh


Like when graphics stack and drivers were "imported" into the WinNT kernel as an optimization for the user-space version. And thus began 30 years of "another week, another graphics subsystem crash/vuln".


Indeed. These are gigantic mistakes. The quest for performance is diametrically opposed to having a secure system. There will always be a price, sometimes a big one for having a system that enforces proper boundaries. In my opinion: if something can be a process then it should be a process.


Plan9 or HURD? Mach anyone?


The boat long ago sailed on Mach/Hurd; there are probably better options in microkernel-land. There's Zircon, but Google laid off a bunch of the Fuchsia folks and has been pretty quite lately. QNX is still a thing, but closed source yadda yadda. Best hope there is probably the L4 family (seL4, et. al).


I would not be surprised at all if we end up with radically different OS architectures than the 1970's model we have today.


I would. Things tend to congregate into an ossified mess over time. Case in point: our current model is from the 1970s.


But it works, and it is unclear if alternative architectures are viable in practice.


If the new model is incompatible with the old, no one will invest in it. It's like you show people a warp drive and they just stare at you not understanding any of it because all they want is a better car.


Their maintainers have always be among the most responsive to security reports, so at least for this reason I wouldn't encourage you to switch to an alternate solution. The component might have historical problems but they're methodically being eliminated by rigorous people. If more software was maintained like this, we'd progressively converge towards bug-free code.


On windows, no one should be running SMB either.

There are network mount options (also include ssh support)

https://rclone.org/install/

And SSH access and remote IFS NFS drive mount to host with winget:

# Run PowerShell as an Administrator.

Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*'

# Install the OpenSSH Client

Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0

# Install the OpenSSH Server

Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0

Start-Service sshd

Set-Service -Name sshd -StartupType 'Automatic'

# Only allow local or VPN host server access

New-NetFirewallRule -Name sshd -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22 -RemoteAddress 192.168.1.0/24

winget install frequency403.OpenSSHGUI

winget install -h -e --id "WinFsp.WinFsp"

winget install -h -e --id "SSHFS-Win.SSHFS-Win"

winget install -h -e evsar3.sshfs-win-manager

#As administrator in power shell run to manage ssh keys:

OpenSSH-GUI-win-x64

And free/paid apps for your phone to sync your files automatically over SFTP.

https://filezilla-project.org/download.php?show_all=1

https://play.google.com/store/apps/details?id=cz.bukacek.fil...

https://apps.apple.com/ca/app/photosync-transfer-photos/id41...

https://play.google.com/store/apps/details?id=com.touchbyte....

Stop using SMB, it was always broken on Windows and Linux. =3


I find it incredibly naive that they’d hope it would not leak after weeks/months of embargo.

Being given advance notice of an upcoming security fix is an immense privilege, organisations should turn around quickly when given such information, they shouldn’t be given more than a couple of days to update IMHO, it’s not like the rest of the world can wait.


Keep in mind that some of the organizations are presumably patching ancient versions of PHP like 5.6. I am sure this is a process which takes considerable time, especially as upstream PHP has washed their hands of such old versions and the downstreams are effectively on their own.

(It is often much cheaper for an enterprise to just get a long term support contract than to properly upgrade to a modern PHP stack.)


> (It is often much cheaper for an enterprise to just get a long term support contract than to properly upgrade to a modern PHP stack.)

I've experienced similar to this. I know I shouldn't be, but I still get amazed every time I hear that some small company is still using an old DOS machine running core software based on dBase that nobody has any clue on how works and the developer has since moved on to a higher plane. One person told me that they sweat every time the power goes out longer than the attached UPS can run holding their breath that the machine powers back up.


That... just makes it so their tech debt turns into entire world's security problems.

5.6 is unsupported. There should be not getting special treatment just because they have massive tech debt


Any legit use case for using SSH over Tor?


Administering your hidden service?


None, use an onion service for it.


privacy


In the end, it’s the same answer as to why humans do it: incentives.

Why do we commit financial fraud and destroy the planet? Because there is only one goal that counts: making more money. It’s the only measure of success for powerful people, they are powerful because of it.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: