withzombies

ARM64 is what Intel would design if they learned from the lessons of x86 and got a chance to restart.

ARM64 (aka AArch64) is the best version of x86 yet.

It's clean, very little warts, they learned from their mistakes with ARMv7/Thumb2 (specifically the IT instruction).

It helps that Apple controls the whole ecosystem and could seamlessly move to ARM64. The Android transition has been making progress also.

Maybe someday we'll drop 32bit and 16bit support in x86 systems (and also in "modern" programming languages!).

You don't need to modify the kernel or iBoot on disk to inject a patched OS (or malware). redsn0w didn't, it would boot over dfu every time.

It's totally possible to rootkit a phone and have it reboot just fine (with the rootkit removed).

Algo can be used to configure WireGuard also: https://github.com/trailofbits/algo

It automatically handles server provisioning, creating users, and can also generate QR codes.

A software QA engineer walks into a bar. He orders a beer. Orders 0 beers. Orders 99999999999 beers. Orders a lizard. Orders -1 beers.

First real customer walks in and asks where the bathroom is. The bar bursts into flames, killing everyone.

Using symbolic execution to simultaneously test all edge cases is a really powerful idea. DeepState is especially powerful since it'll generate test cases you can use to fix bugs and then use them in your traditional CI tests.

I've made a lifetime total of $2500 on bug bounties. I find them pretty interesting as a distraction from my main job but I don't see how they can compete.

Most platforms seem to run these private invite-only hackathons where the top performers get a first crack at each new campaign. I was invited to one of those and it was pretty fun hanging out with the other participants, but application security pentesters can easily make $80k+/year in the US and none of them were coming close to this. Additionally, a real pentest comes with remediation advice and the consultants are incentivized to help you fix the flaws correctly. On the flipside, a bug bounty participant is incentivized to help to fix the most narrow version as possible -- so they can further probe the area for more bounties.

Now no one will be perfect!

I wonder if they'll calibrate the scores against past 10.0 performances

NSA's Rob Joyce is presenting GHIDRA, a reverse-engineering tool developed by the NSA. They're apparently making it free to the public.

I wonder if it'll be open source. It should be public domain software but if the NSA used contractors for development, that muddies the waters a bit.

Describing Weird Machines to non-practitioners is almost as hard of a problem as actually finding them. I think Sophia did a good job explaining them and laying out a path to automatically identify them.

I've been thinking about this problem for a few weeks now and I'm not certain you can safely upgrade any deployed contract.

I know a lot of dApp developers want to be more agile with their deployments but you shouldn't be changing the contract terms after the fact.

Have you checked out DeepState (https://github.com/trailofbits/deepstate), it's a symbolic unit testing framework that has an interface similar to google test.

It's true, but there's a few tools out there to help now, such as tis-interpreter (https://github.com/TrustInSoft/tis-interpreter)

Webkit's Web Template Framework https://github.com/WebKit/webkit/tree/master/Source/WTF/wtf

Yes, most airports print the gates on the boarding passes. A handful (mostly ATL) just give up, because they can't reliably predict the gate until 30 minutes before boarding.

For this year's DEFCON CTF, the organizers decided to break all existing tooling by making a custom architecture with 9-bit bytes, 27-bit words, and middle-endian integers.

I was able to make a [Binary Ninja](https://binary.ninja) architecture plugin on the flight to Vegas, but unfortunately I had to expand everything to 16-bit bytes to be able to handle addressing. This made control flow graph recovery possible, but I had to choose between accurate data references or accurate immediates. I ended up going with accurate immediates and letting my data references fall into the middle of functions (because instruction addresses were all 2x).

The 27-bit words and middle-endianness wasn't a huge issue, but the 9-bit bytes really really sucked. We had IO buffering issues on every exploit we wrote and analyzing PCAPs was a huge pain.

I trust Digital Ocean much more than I trust PrivateInternetAccess. I also don't want to be associated with the other traffic going through PIA or similar VPNs.

I don't understand why everyone is up in arms about the ESC key getting replaced. It's still there (by holding the Fn key), but even better: now your vim session can have a custom touchbar interface that makes some of the more obscure vim shortcuts easier.

The blog post by the team that did the port (Trail of Bits), mentions that it uses wmi and shims the data into osquery.

https://blog.trailofbits.com/2016/09/27/windows-network-secu...

Email, slack, or the "Questions or Comments?" popup are all acceptable

He probably went to Stanford and took it in person.

I like Coursera, but I've been waiting on a class to happen for the past two years and they keep rescheduling it. I really wish they'd address it by either canceling the listing or actually making it happen.

The class is Dan Boneh's Crypto 2 course.