Some notes, tools, and techniques for reverse engineering Golang binaries.
| #!/bin/bash | |
| gdb -p "$1" -batch -ex 'set {short}$rip = 0x050f' -ex 'set $rax=231' -ex 'set $rdi=0' -ex 'cont' |
| <html lang="en"><head> | |
| <meta charset="UTF-8"> | |
| <meta http-equiv="X-UA-Compatible" content="IE=edge"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Temporary Pastebin</title> | |
| </head> | |
| <body> | |
| <script src="https://cdnjs.cloudflare.com/ajax/libs/ipfs/0.54.4/index.min.js" integrity="sha512-6GHE5kFKM1y+tmjSWrTCF13qsIqV9hDYYwrZ9iu/7wnoY4qvq/u7qSVKN4iDk0xeI7pLv6h3nBRp64aIYya8KA==" crossorigin="anonymous" referrerpolicy="no-referrer"> | |
| </script> | |
| <script> |
This project is a tiny compiler for a very simple language consisting of boolean expression.
The language has two constants: 1 for true and 0 for false, and 4 logic gates:
! (not), & (and), | (or), and ^ (xor).
It can also use parentheses to manage priorities.
Here is its grammar in BNF format:
expr ::= "0" | "1"
This is inspired by https://fasterthanli.me/blog/2020/a-half-hour-to-learn-rust/
the command zig run my_code.zig will compile and immediately run your Zig
program. Each of these cells contains a zig program that you can try to run
(some of them contain compile-time errors that you can comment out to play
with)
| By default, EBPF programs will not run on WSL2 due to required kernel modules missing. The following example error is an | |
| indication of this problem: | |
| modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.19.84-microso | |
| ft-standard/modules.dep.bin' | |
| modprobe: FATAL: Module kheaders not found in directory /lib/modules/4.19.84-microsoft-standard | |
| chdir(/lib/modules/4.19.84-microsoft-standard/build): No such file or directory | |
| To fix this you need to rebuild the WSL2 kernel with the missing kernel modules. The below instructions are for Ubuntu 18.04 WSL2. | |
| 1. git clone https://github.com/microsoft/WSL2-Linux-Kernel.git |
| Demo Name | Source |
|---|---|
| VS2019 – Search Functionality | https://visualstudio.microsoft.com/downloads/ |
| VS2019 – New Project Experience | https://visualstudio.microsoft.com/downloads/ |
| VS2019 – Code cleanup/Refactor | https://github.com/mbcrump/CodeCleanup |
| VS2019 – Dev Command Prompt for PowerShell | Coming Soon! |
| .NET Core 3 - Greenshot | https://github.com/greenshot/greenshot/ |
| .NET Core 3 - - dotnet try demo | https://github.com/dotnet/try |
| SELECT LOWER(UserAtHost) AS UserAtHost, Status= | |
| CASE | |
| WHEN Availability BETWEEN 0 AND 2999 THEN Availability | |
| WHEN Availability BETWEEN 3000 AND 4499 THEN 'Available' | |
| WHEN Availability BETWEEN 4500 and 5999 THEN 'Available - Idle' | |
| WHEN Availability BETWEEN 6000 and 7499 THEN 'Busy' | |
| WHEN Availability BETWEEN 7500 and 8999 THEN 'Busy - Idle' | |
| WHEN Availability BETWEEN 9000 and 11999 THEN 'Do not Disturb' | |
| WHEN Availability BETWEEN 12000 and 14999 THEN 'Be right back' | |
| WHEN Availability BETWEEN 15000 and 17999 THEN 'Away' |
There are two types of markup in Liquid: Output and Tag.
- Output markup (which may resolve to text) is surrounded by
{{ matched pairs of curly brackets (ie, braces) }}- Tag markup (which cannot resolve to text) is surrounded by
A collection of articles by AngularJS veterans, sometimes even core committers, that explain in detail what's wrong with Angular 1.x, how Angular 2 isn't the future, and why you should avoid the entire thing at all costs unless you want to spend the next few years in hell.
Reason for this: I'm getting tired of having to explain to everyone, chief of which all the indiscriminate Google Kool-Aid™ drinkers, why I have never believed in Angular, why I think it'll publicly fail pretty soon now (a couple years), and why it's a dead end IMO. This gist serves as a quick target I can point people to in order not to have to parrot / compile the core of the articles below everytime. Their compounded reading pretty much captures 99% of my view on the topic.
This page is accessible through http://bit.ly/angular-just-say-no and http://bit.ly/angularjustsayno, btw.