Earlier quoted context omitted.
Books I've read would disagree. Are you the emdash police?
[flagged]
Actively exploited sandbox RCE in all Chromium versions
201–210 of 528 posts
Re: Actively exploited sandbox RCE in all Chromium versions
#202Earlier quoted context omitted.
They pay in plain old money, too. On the market your counterparty will be a criminal who is trying to scam you every step of the way.
Not so much, the grey market is pretty well structured.
Sound very interesting!
Re: Actively exploited sandbox RCE in all Chromium versions
#203[flagged]
It’s not. Same as credible threats are also seen as nothing to do with free speech. It just isn’t what free speech is. It’s a separate thing.
Speaking more generally, don't let your ideals bias your judgment. Just because you support policy X and also view ideal Y as good that doesn't mean that X isn't detrimental to Y. It's important to be objective about these things.
Re: Actively exploited sandbox RCE in all Chromium versions
#204Sounds wild. (Posted from memory safe WebKit; i.e. WebKit compiled with filcc and all of WebKit's dependencies compiled with filcc.)
Wait, you have that working? What's the lowest friction to run it? Like, VM or docker container or...
Then build WebKit using do_cmake_yolo_simpler.sh in projects/webkitgtk-2.44.3
It's still pretty rough, but works more than well enough to post on HN. My regression test is to post on X. That works too
Re: Actively exploited sandbox RCE in all Chromium versions
#205Earlier quoted context omitted.
Yeah
It sounds technically possible to build a JIT where a verifier checks that the JIT-generated code is correctly pizlonated before allowing it to become executable. :)
I have a new tech called SaRCAsm, which is a memory-safe assembler. So the next step is a "Sarcastic JIT" :-)
Re: Actively exploited sandbox RCE in all Chromium versions
#206I’m so tired. I think I’m just going to get a job as a garbage man and cancel my internet.
Re: Actively exploited sandbox RCE in all Chromium versions
#207{
int msgType;
union {
char *name;
int nameID;
};
};That finally convinced me getting data using functions (accessors, getters, setters) is a good thing, even in C :) Just all that unnecesary if's are so annoing and killing performance...
Re: Actively exploited sandbox RCE in all Chromium versions
#208Earlier quoted context omitted.
Wait, you have that working? What's the lowest friction to run it? Like, VM or docker container or...
VM https://fil-c.org/pizlix Then build WebKit using do_cmake_yolo_simpler.sh in projects/webkitgtk-2.44.3 It's still pretty rough, but works more than well enough to post on HN. My regression test is to post on X. That works too
Re: Actively exploited sandbox RCE in all Chromium versions
#209Re: Actively exploited sandbox RCE in all Chromium versions
#210Earlier quoted context omitted.
VM https://fil-c.org/pizlix Then build WebKit using do_cmake_yolo_simpler.sh in projects/webkitgtk-2.44.3 It's still pretty rough, but works more than well enough to post on HN. My regression test is to post on X. That works too
Sweet, thanks. I guess running in a VM is also a bonus protective layer:)
Pls file bugs if you encounter issues.
Also, fair warning, it's hella slow right now on JS-heavy websites (like X). It barely works.
But we can fix that with some effort, I think