News for hackers. Stuff that matters.
Re:Safely Reviving Shared Memory by Santosh83 on Tuesday July 21, 2020 @01:09PM (#23908652)
So how will these headers work for shared hosting sites where you normally cannot modify the hosting provider's HTTP server?
Re:Safely Reviving Shared Memory by zelly on Tuesday July 21, 2020 @11:13PM (#23913560)
You only need this if you're doing multithreaded WebAssembly. The typical applications that need that (e.g. games) also require a huge amount of infrastructure, let alone a web server config.
Re:Safely Reviving Shared Memory by pjmlp on Wednesday July 22, 2020 @12:45AM (#23914013)
Flash games don't need a huge amount of infrastructure.
Re:Safely Reviving Shared Memory by Multicomp on Wednesday July 22, 2020 @07:23AM (#23915844)
Yep, but like rolling an XML web service or posting html forms, that would (be far too boring) || (come with its own set of trade offs).

If we could get an open-source flash player that was not so insecure and/or make an open source equivalent to Adobe air that spits out web standard code, we would not lose the flexibility that adobe flash gave us.

we really don't have an answer to losing Adobe flash, similarly to when we lost the spaghetti code enabling yet so pragmatically useful visual basic 6.

Re:Safely Reviving Shared Memory by pjmlp on Wednesday July 22, 2020 @07:33AM (#23915882)
Here is the 2011 version of WebAssembly for Flash.

https://adobe-flash.github.io/crossbridge/

And here is Unreal Engine 3 using it,

https://www.youtube.com/watch?v=UQiUP2Hd60Y

WebAssembly has delayed progress for 10 years, politcs that is all, and for what?

"Everything Old is New Again: Binary Security of WebAssembly" - USENIX 2020

http://www.software-lab.org/publications/usenixSec2020-WebAs...

Re:Safely Reviving Shared Memory by simlevesque on Tuesday July 21, 2020 @01:18PM (#23908747)
You can set headers with .htaccess.
Re:Safely Reviving Shared Memory by danudey on Tuesday July 21, 2020 @02:21PM (#23909354)
Only in specific situations, where the site is using Apache and has .htaccess files enabled. I would argue that using Apache in the first place is non-optimal, but enabling arbitrary .htaccess files for clients is also a potential disaster.

Then again, I suppose there are enough people out there who just want to FTP up their wordpress code and call it a day, so... ugh.

Re:Safely Reviving Shared Memory by duskwuff on Tuesday July 21, 2020 @06:10PM (#23911523)
WordPress expects a working .htaccess for its URL structure, as do most modern PHP applications. So virtually all shared hosts will support .htaccess.

> I would argue that using Apache in the first place is non-optimal

What would you prefer? nginx is not suited to shared environments at all.

Re:Safely Reviving Shared Memory by john-shaffer on Tuesday July 21, 2020 @07:04PM (#23911873)
> WordPress expects a working .htaccess for its URL structure

I haven't heard this. I'm running WordPress via NGINX with no issues.

Re:Safely Reviving Shared Memory by the8472 on Tuesday July 21, 2020 @03:54PM (#23910303)
If you're only uploading some stuff to wordpress do you need shared array buffers?
Re:Safely Reviving Shared Memory by birdyrooster on Tuesday July 21, 2020 @02:02PM (#23909180)
And boy do they, I used to be a shared hosting administrator and sometimes people would do stupid things like create 10MB .htaccess files with the subnets of all of the countries they wanted to block and then would call to complain that their site was loading slow. (Probably not a great idea to parse a config file for every request but at least it exists)