Hacker Newsnew | past | comments | ask | show | jobs | submit | avadodin's commentslogin

> copy to clipboard

no, thank you. I already have hobbies to consume my life.


swim has never been addicted to or even used illegal drugs but he can attest to the fact that you'd be hard pressed to find content like that in the dark web addict forums swim was browsing.

The average user expectation is probably not that any random exe they download from the piratehub or whatever can actually run Linux shellcode on their system.

I think all syscalls should be landlocked by default(It might require a novel kernel-assisted mechanism to keep existing official Wine libraries working, not sure).

Some of these programs with Wine support will have to get grandfathered in, of course, but at least let the user add them to a white list with a confirmation popup.

"This program wants to run Linux h4x0r shellcode. Allow?"

And then of course provide a mechanism so that new Wine-aware applications can interact with Linux features in a safer way.


Users shouldn't be running random executables. Wine is not a sandbox!

Maybe change the name to Wins?

Wine is not a Sandbox but come on. Everyone has been using it as if it was.

Even Bottles was only a prefix-manager until a couple months ago.

I think it should be and also disallow Linux syscalls and Z: drive accesses by default from within the "sandbox" on top of that in order to reduce the attack surface.


> I think it should be and also disallow Linux syscalls and Z: drive accesses by default from within the "sandbox" on top of that in order to reduce the attack surface.

This is not even remotely sufficient. A malicious application could modify the memory pages of WINE code and execute direct syscalls anyway.

If you want sandboxing, use a Linux sandboxing solution on WINE. It's far too late to try to bolt on sandboxing now.


it would be hard to say whether a given program making a syscall is trying to do a native linux sys call or a "naked" windows syscall (something that some windows programs actually do).

but yeah, somehow intercepting syscalls is a prerequisite for either emulating these naked windows syscalls or notifying the user about the native linux ones.


Stock buy-backs can be part of an illegal scheme but, in general, they are one of the few mechanisms in corporate actions through which the regular joe shareholder doesn't get the short end of the stick.

How is owning a larger share of a company with proportionally less cash and a higher price per share than what you could have sold it for before bad.

Have you looked at precious metal charts as of late? Do 1/x and that's the value of the cash these companies are trading for a valuable business.


I'll leave the analysis to op's ai.

I've had enough Elsa/Spiderman/Hitler today.


I once "fixed" a port of a program to Linux.

It was generating the wrong output — that is: not the same as on Windows.

My fix initialized a thitherto uninitialized array with the VisualC++(ca. 5.0) debug build default value.


> especially its insidious, forced MIT rewrites of popular GPL software

Is this some sort of movement?

I was aware that some Rust software had been released under permissive licenses but I didn't know it was activism besides the obvious C-is-obsolete angle.


It’s not deliberate activism. It’s two things:

Monomorphizarion makes the GPL weird.

Rust is dual licensed under Apache/MIT, and so most people choose the same as a default if they don’t feel strongly about licensing.


> there's some legal debate if that is even something that you can do proactively

Public Domain in the US is the only factor that truly matters on the Internet today, but people who care do both.

Release into the Public Domain and provide a 0-type license.


that is a legitimate post by itself

> It's CDE-conformant, I know this!

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

Search: