roblabla

17 ms·

181.
by roblabla 4y ago
> - Decompiler too stubborn sometimes, ignoring user input (e.g. manually specified types). This is the thing that sticks out the most IMO. IDA decompiler is quite a bit more flexible than Ghidra's. When you assert a type, it will u
182.
by roblabla 4y ago
If you don't abide, you get penalties, from fines to being banned from the market. It's up to each company whether they accept that risk or not.
183.
by roblabla 4y ago
As one random point: If you just hash the password, you're vulnerable to rainbow table attacks. So you want to salt the password, at the very least. But really, what you want to do is use a framework developed by domain experts that de
184.
by roblabla 4y ago
This is probably refering the SQLite Code of Ethics debacle. SQLite has a Code of Ethics, which is used for ticking a box when working with some of their clients (meaning: they probably don't take it very seriously). For this code of e
185.
by roblabla 4y ago
Microsoft has yet to totally lockdown their hardware. They usually provide a way to disable secureboot or to enroll your own keys (with a few specific exceptions). Apple's macs are also fairly open. You can install your own bootloader,
186.
by roblabla 4y ago
Modding comes to mind. By having an ssh connection, you can potentially do remote debugging of a mod, among other fun stuff.
187.
by roblabla 4y ago
> Has the Rust-portability situation been addressed? The rust portability story is in the process of being addressed, by two different projects: gcc-rs[0] adds a Rust frontend to GCC. rustc-codegen-gcc[1] adds a GCC backend to rustc. Bo
188.
by roblabla 4y ago
Oh, I don't know, maybe breaking literally all of their extension with the deprecation of XUL? I'm a happy firefox user, and I'm pretty sure it was the right choice IMO, as firefox is certainly much more stable and fast now t
189.
by roblabla 4y ago
Rust promised to not introduce breaking changes willy nilly since 1.0.0. If the change would break some previously working code, they need to go through a deprecation period. This is probably the issue here.
190.
by roblabla 4y ago
The problem is, you need to design for the worse case scenario here, because when the worse case does happen, the last thing you need is for your revocation system to not work because it doesn't scale. So, no, it's not common. But
191.
by roblabla 4y ago
Ah, I hadn't considered the whole sockaddr/sockaddr_storage/sockaddr_in/sockaddr_un... thing, yeah that's a mess. I guess a more modern API would either use opaque pointers or an union (though that has its own share
192.
by roblabla 4y ago
Huh, I can understand labeling all of those are messes, but what's wrong with Berkeley sockets? The API seems fairly straightforward, and has managed to withstand the test of time pretty well. I'm curious what grievances you have
193.
by roblabla 4y ago
The problem is with the publishing part. It's pretty unclear - to me at least - what the legal status of publishing 0days is around the world. In the USA, I'd expect it to be protected by free speech, but even then I wouldn't
194.
by roblabla 4y ago
> - Build pipeline. Maybe, but you can’t fully build a iOS app on Linux so it didn’t seem like a win. This is my use case (I implemented notarization API support in rcodesign). I build MacOS apps entirely from Linux using my own bespoke
195.
by roblabla 4y ago
This is actually a solved problem, using osxcross[0]. The experience is honestly very smooth, and we don't require any apple proprietary binaries. The only thing apple-proprietary is their SDK (containing the header files for compili
196.
by roblabla 4y ago
Yes. SSEs are just an infinite-length HTTP body formatted in a particular way. And like all HTTP bodies, they are guaranteed to arrive in the same order the bytes were sent.
197.
by roblabla 4y ago
So, Rust has this very awesome thing where all variables are move by default, but types may opt in to be copied by implementing the Copy trait (a trait being the Rust equivalent of a Swift protocol). This works exceedingly well . It esse
198.
by roblabla 4y ago
Then don't use this particular app? This already exists today: A lot of apps are android-only, or jailbreak-only. In the same sense, tomorrow we'll likely have amazon-store-only apps. In practice I doubt many apps will use a third
199.
by roblabla 4y ago
Huge disagree on this. Old code tend to be much more terrible because the tools were terrible. They gave little incentive and absolutely no help to write even passable code. We end up with a mess of poorly documented, sparingly commented sp
200.
by roblabla 4y ago
> your ID gets scanned, the scan hits a government server for verification. I mean, you're already assuming things work a certain way that is not necessarily true. The ID card could just have all the information stored and signed by
201.
by roblabla 4y ago
And what businesses are hoping for are users that are paying without actually using their service. Produce nothing, but get paid every month. Sounds like a crap deal for the users.
202.
by roblabla 4y ago
It's still too early for Rust in the embedded space. A lot of that space has various certification requirements that Rust doesn't meet yet, and the rest of the space tends to follow too and is very conservative. Ferrous Systems is
203.
by roblabla 4y ago
> I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. Yeah, no. Don't get me wrong, Jetbrains IDEs are great. But they're not as easy to extend, its p
204.
by roblabla 4y ago
Their API being freely accessible is irrelevant. If they decided to ban anyone using their API differently from their official client, they would be entirely within their rights. They probably won't though. It'd be a waste of time
205.
by roblabla 4y ago
The last I heard, BetterDiscord was actually against discord's TOS[0]. [0]: https://nitter.42l.fr/discord/status/908000828690182145
206.
by roblabla 4y ago
I'm skeptical, but optimistic. qemu user emulation with TCG is also a JIT compiler, is pretty decent, and doesn't have the "needs to be limited to a single core" when ran outside macos hardware, though it certainly has a
207.
by roblabla 4y ago
> I guess restricting the app to a single core might reduce that error frequency a bit Shouldn't it eliminate it entirely? I'm pretty sure ARM guarantees sequential consistency on a single core, so if the app is limited to a si
208.
by roblabla 4y ago
That's only true up to a certain point. ARM is a very weird target, because a lot of standardized stuff we take for granted in x86/PC land aren't standardized on ARM. In particular, take the Interrupt Controller: x86 has a st
209.
by roblabla 4y ago
GC and FFI do have a lot to do w/ each-other though, because FFI usually introduces unmanaged objects. When a lot of what you're doing is interacting with low-level platform APIs, you end up having a lot of those unmanaged objects
210.
by roblabla 4y ago
UTM[0] does this, which uses qemu under the hood. It's pretty slow, but for some non-GUI workloads, the performance is acceptable. [0]: https://mac.getutm.app/

More ›