0x0

24 ms·

241.
by 0x0 5y ago
This actually happened for real with Dropbox about 10 years ago: https://techcrunch.com/2011/06/20/dropbox-security-bug-made-...
242.
by 0x0 5y ago
In the EU, Tesla cars (even cars built and shipped from the US) and Tesla superchargers use CCS.
243.
by 0x0 5y ago
How do you "use tokens" to prevent prying in its address space?
244.
by 0x0 5y ago
To the people arguing it's "fair use" to use this for training an ML network. Where do you draw the line? What if you train an "ML network" with one or two inputs... so that they almost always "generate" e
245.
by 0x0 5y ago
It's a shame the fork doesn't use better commit messages than they do. For example, "Fixes" is the entire commit message for https://github.com/temporary-audacity/audacity/commit/d9f30b...
246.
by 0x0 5y ago
The RealWOW server appears to run an ancient windows php distribution that is probably rooted to high heavens: https://twitter.com/angelxwind/status/1410742393914023937?s=...
247.
by 0x0 5y ago
Any chance Copilot could be made to cough up the DVDCSS or BluRay AACS DRM secrets?
248.
by 0x0 5y ago
So is there any reason at all to use the original ARM64 ABI? Adding another ABI seems like a huge undertaking. Isn't the original ARM64 windows ABI a fairly recent invention, too? Too bad they didn't make it "ARM64EC" fr
249.
by 0x0 5y ago
Security seems to have taken a backseat, by the looks of the attitude towards outdated openssl versions displayed here. https://github.com/mumble-voip/mumble/issues/4001
250.
by 0x0 5y ago
The newtonsoft json dlls (and other) distribution contains different dlls in different folders called "net45", "netstandard2.0", "portable-net40+sl5" etc. So it is obviously more than just a specification, si
251.
by 0x0 5y ago
The new UI changes were introduced in tech preview 126, but that one is only available for macOS 12. The download page at https://developer.apple.com/safari/download/ says "macOS 11 - coming soon". I hav
252.
by 0x0 5y ago
This exactly! The branding and versioning of .NET is a complete disaster. There's .NET Framework (where even simply getting the current runtime version requires several convoluted hoops, since System.Environment.Version has gone the wa
253.
by 0x0 5y ago
maps.me was sold and the app went downhill pushing some crypto wallet stuff and a ton of tracking/affiliate/ads stuff. I briefly looked over the github commits earlier when this fork started and there seemed to be dozens if not hu
254.
by 0x0 5y ago
If and when browsers start requiring pre-certificate transparency logging, anything like this should no longer be possible to pull off, since none of the fake certificates would be able to contain a stapled pre-certificate "signoff&quo
255.
by 0x0 5y ago
I did something similar to bring a legacy cable-only printer online for wifi clients where there were no cabled uplink. Worked well. Tried to add airprint with cups as well but that was hit&miss. parprouted & dhcp-helper are secret
256.
by 0x0 5y ago
> "only gives them the utility of the land itself" "only"? I'd say the "utility of the land" IS the only value of "having" land.
257.
by 0x0 5y ago
"Our apologies. An error seems to have occurred. We’ve logged this error. Contact us if this issue persists." ...
258.
by 0x0 5y ago
I think what many of us want and expect is a bullet proof permission system for the app store that doesn't contain surprises, gotchas, and magic entitlements that are ripe for exploitation (see for example PsychicPaper)
259.
by 0x0 5y ago
The "Clips" app is not as first party as the built-in camera app is. I mean, it still comes from Apple, but it is ONLY distributed as an additional download in the app store. You know, via the same app store we're supposed to
260.
by 0x0 5y ago
Because the mere fact that an entitlement for bypassing permission prompts exists, means that non-apple apps could try to exploit it (see for example the PsychicPaper exploit). Designing in such a huge hole in the permission system just mak
261.
by 0x0 5y ago
Another weird example is how Apple's own "Clips" app has a special private entitlement that bypasses the permission prompt for camera access. Would it hurt them so much to prompt for camera access the first time the app is st
262.
by 0x0 5y ago
I remember putting together a sloppy http range implementation that initially only supported single ranges, it had quite the explosive effect on adobe reader when it didn't get the expected response to its multi-range requests :)
263.
by 0x0 5y ago
No, you can do it blindly. For example, if you have a web page that has an <img> tag pointing to a specific domain, then you can assume the client will perform a DNS lookup, so you can send fake replies blindly, hoping it will match a
264.
by 0x0 5y ago
The random mixed-case patterns are used to reduce the probability that someone evil could send spoofed DNS replies to your queries and have your DNS resolver trust those fake replies.
265.
by 0x0 5y ago
If you share $HOME with your VM (which is apparently the default in Parallels), you're not gaining much in terms of security. https://zerodayengineering.com/blog/dont-share-your-home.htm...
266.
by 0x0 5y ago
If this was just one patch and it was caught early, it could be excused as a rogue solo stunt. But papers have been published. IRB board granted exemptions. A whole team worked on it. Too many people conspiring on pissing in the pool and wa
267.
by 0x0 5y ago
I think you underestimate the shade this puts on the UMN name. I've never even heard of UMN before, but I doubt I'll ever forget hearing about this university fraudulently trying to sabotage the Linux project, and will probably tr
268.
by 0x0 5y ago
It should be supported by most programs that use the c library to resolve hostnames, I believe.
269.
by 0x0 6y ago
I wouldn't say it's obvious. There's some careful decisions in the design that might not be obvious at first sight, such as having upper and lowercase characters be the same save for a single bit.
270.
by 0x0 6y ago
I don't think so? Aren't UCS surrogate pairs at most 16bit each by their very purpose? Also, >16bit unicode code points came much later, I believe, in Unicode 2.0 in 1996 according to Wikipedia (vs UTF-8 which is from around 19

More ›