jonpalmisc

Resources exist, but are only so helpful IMO.

One can't necessarily build an airplane after watching a documentary on it.

Even if there was some "bible" on it, reverse engineering is one of those things that you have to put the reps in for to get good at it and actually develop understanding.

The "bible" is tackling reverse-engineering related projects independently over the course of months/years and picking up knowledge along the way.

Starting with something like cracking software (and making increasingly-advanced cracks) is always my advice for beginners.

Don’t forget http://binary.ninja :)

Didn’t watch this specific video (already knew how), but this one is definitely a skill worth learning—so either this video or another one is worth watching for sure.

> Obfuscating C code shouldn't have any bearing on the decompilability of the output.

This is the entire point of obfuscation and it absolutely does affect how easy the code is to reverse engineer. If it didn’t, there wouldn’t be a market for obfuscators.

I find it to be the perfect size actually. Easily in a backpack and is light, and can use it on the couch, etc. comfortably. I’d never buy a 16” laptop.

Also curious about this.

The other commenter mentioning Firebloom is correct that some firmware (iBoot family) has been using C w/ Firebloom extensions for a while. Parts of SEPOS also use Swift, which would make more sense as a non-C language than Rust, from Apple's perspective at least.

Firebloom is more of a custom compiler/toolchain than a dialect of C—apart from annotations to relate pointer+length parameters, etc., it is still just C.

Firebloom == `-fbounds-safety`

> Does this mean an AU crashing in theory won’t take down your DAW?

Yes, this has been my experience with AUs in Logic Pro, at least. You simply get a message saying a plugin failed and that you can try reloading it if you'd like.

For starters, AUs are "easier" to run under Roestta than VSTs since AUs run out-of-process by default. This means you can use a x86_64 AU without running the entire DAW under Rosetta on Apple Silicon.

Sublime Text and Sublime Merge actually ship with these CLI utilities by default, which have some additional features:

    $ fd 's(merge|ubl)$' /Applications/Sublime*                                          
    /Applications/Sublime Merge.app/Contents/SharedSupport/bin/smerge
    /Applications/Sublime Text.app/Contents/SharedSupport/bin/subl

I haven’t looked at this in detail in a while either, but I don’t think the claims here are correct.

It is true that Apple employs some efforts to prevent/discourage you from using those services illegitimately, but using iMessage and FaceTime from a Hackintosh has been possible for years, largely without jumping through any hoops.

It’s the executable file format for macOS/iOS/*OS, analogous to ELF or PE.

https://en.m.wikipedia.org/wiki/Mach-O

This is the first large piece of (GUI) desktop software I've seen written in Haxe. Not that I've seen all software ever of course, just thought it was interesting.

Source: https://github.com/armory3d/armortools

Have linked this on this site before, but if you find this theme of techniques interesting, you might like some of Mordechai Guri’s work as well: https://cyber.bgu.ac.il/advanced-cyber/airgap

For how long?

Where on OVH’s site are you seeing servers that cheap? I can’t seem to find anything like that, but I’m also on mobile right now.

No email form: https://d1yx3ys82bpsa0.cloudfront.net/source/lisa-source.zip...

IIRC, it is /some/ (not /all/) of the code on the SEP is now Swift. SEPOS's microkernel, etc. is still C.

If you find this interesting, you may also like some of Mordechai Guri’s work: https://cyber.bgu.ac.il/advanced-cyber/airgap

yes, please! Very minor issue indeed, but this kind of cruft adds up and I'd love to see it fixed.

I also keep one on my keyring and I get poked in the finger/thigh by it all the time; it’s super annoying! Still keep it though since I regularly have to pop my SIM in and out..

So… a build of CMake from within the last 8 years? Seems like a reasonable requirement.

Any examples of pain points with CMake? I use it every day and rarely have issues, yet I seem to see complaints online rather often.

Meta-answer: I like to pick a project I wouldn't mind doing a 2–3 times in that language. It's hard to learn all the best practices, idioms, etc. of a language in one sweep. Having a project that you can repeatedly do in X language—making it more "X-like" each time—is a good way to learn how to refactor things and structure things "natively" in language X.

PDF also cannot change from underneath you, unlike a web page. Better to have a copy of what the license was at the time you agreed to it, imo.

Source code for the curious: https://github.com/0intro/plan9/tree/main/sys/src/cmd/mk

KeePass is awesome. Open spec. Works offline. Plenty of good clients for every platform. Self-managed syncing via your service of choice (Dropbox, OneDrive, <other>, etc.). Can't recommend it enough.

I agree. Seeing the next generation of terminal apps that often seem to use "pretty" and "fancy" output formatting (read: "non-parseable" and "overly-decorated") makes me sad. Plain, simple, human-readable, and machine-parseable output can't be beat in my mind.