vient

RE was arguably the first* task category to become completely solvable by LLMs on cybersecurity CTFs. This is exactly about obfuscated code, LLMs seem to have no problems with it now. The only probabilistic defense is to include tons of red herring so agent goes the wrong path and ends up in some tarpit like bruteforcing unrelated un-bruteforceable hashes.

* Cryptography category also went down fast but I think LLMs solved RE a bit faster. RE and crypto have in common that the task is completely local, but in classic RE tasks it is also usually ~obvious what you are supposed to do, you just need to do it - which agents do really well.

By "SSH key files" do you mean private keys? Or only public keys?

Interesting, saw reCAPTCHA infinite loop for the first time in a long time just yesterday, on Firefox, and it was when I tried to access an article on PMC. Disabling uBlock and Enhanced Tracking Protection did not help. It looked like several automatic reloads, then one real reCAPTCHA showed, and infinite reload loop after I solved it.

Does not reproduce today though, and I never had issues with PMC/NIH before that.

I got an impression from the text that pilots were not sure the fuel levelling line does not have a leak itself. Maybe they were afraid the line can leak fuel into fuselage somehow?

This may just be too much. I settled up on 0.2mg dosage - you can find 0.1mg tablets, easy to try different dosages with them. Also seems to work better if you take it 2-3 hours before sleep.

Important detail here is that the problem disappers if you use PRIVATE dependencies — but you can't do that with a heavily templated C++ codebase. Templates (and complexity they bring) are there for good reasons (primarily performance at all costs) so we did not manage to find a path forward with CMake.

Not only is CMake single threaded but the generation step time scales almost quadratically* with the number of targets in some cases. Probably not what happens here but this is what forced us to move from CMake — generation times were surpassing 5 minutes, and this is not counting configuring step.

* Because in CMake there are several target properties that may be affected by the "parent" (another target which added this target as dependency), meaning that these properties need to be re-evaluated in the context of each root target dependent on this one. If I remember correctly, exact mechanism is that some properties can have generator expressions, and these expressions can reference "parent" target. Now we imagine an app which has some std lib with 1k targets, and 100 top-level executables dependent on this std lib - suddenly we have 100k target evaluations in generation step.

Author mentions trying incognito mode without success.

I also tried their strictly mathematical problem description and got filtered 5/5 times.

Interesting, I thought that it can't be right, Fable can't refuse to answer a strictly mathematical problem — well, 5/5 attempts did switch to Opus. Amusingly, one attempt spent almost 10 minutes thinking how to prove NP-hardness only to abruptly switch.