| type term = | |
| | Lam of (term -> term) | |
| | Pi of term * (term -> term) | |
| | Appl of term * term | |
| | Ann of term * term | |
| | FreeVar of int | |
| | Star | |
| | Box | |
| let unfurl lvl f = f (FreeVar lvl) |
There are many, many resources, websites, mods, discord servers, and other links that people playing technical minecraft might find useful. This is an attempt at collecting and categorizing some of them.
Starring or bookmarking this gist may be useful :)
Contents:
| from hashlib import md5, sha1 | |
| from cryptography.hazmat.primitives.ciphers import Cipher, algorithms, modes | |
| from cryptography.hazmat.backends import default_backend | |
| from base64 import b64encode, b64decode | |
| import sys, time | |
| import requests | |
| DEFAULT_MASTERKEY=b'p1a2l3o4a5l6t7o8' | |
| class PanCrypt(): |
| # Attempts to demangle all mangled symbols in the current program using the Rust | |
| # mangling schemes, and replace the default symbol and function signature | |
| # (if applicable) with the demangled symbol. | |
| # | |
| # License: MIT OR Apache-2.0 | |
| #@author Jack Grigg <thestr4d@gmail.com> | |
| #@category Symbol | |
| import string |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
| # IDA (disassembler) and Hex-Rays (decompiler) plugin for Apple AMX | |
| # | |
| # WIP research. (This was edited to add more info after someone posted it to | |
| # Hacker News. Click "Revisions" to see full changes.) | |
| # | |
| # Copyright (c) 2020 dougallj | |
| # Based on Python port of VMX intrinsics plugin: | |
| # Copyright (c) 2019 w4kfu - Synacktiv |
| Readme: In the following pseudo code, [] indicates a subroutine. | |
| Sometimes I choose to write the subroutine inline under the [] in order to maintain context. | |
| One important fact about the way rollbacks are handled here is that we are storing state for every frame. | |
| In any real implementation you only need to store one game state at a time. Storing a game | |
| state for every frame allows us to only rollback to the first frame where the predicted inputs don't match the true ones. | |
| ==Constants== | |
| MAX_ROLLBACK_FRAMES := Any Positive Integer # Specifies the maximum number of frames that can be resimulated | |
| FRAME_ADVANTAGE_LIMIT := Any Positive Integer # Specifies the number of frames the local client can progress ahead of the remote client before time synchronizing. |
| PREFIX=/path/to/install | |
| FPGA_ROOT=/root/of/repos | |
| NUM_JOBS=4 | |
| # If non-zero, enable sscache optimizations. Need to set CC and CXX as well. | |
| SCCACHE=0 | |
| CC=gcc | |
| CXX=g++ | |
| # If non-zero, use chipdbs built on another machine. |
| /* | |
| * ------------------------------------------------------------ | |
| * "THE MONSTERWARE LICENSE" (Revision 01): | |
| * <author> wrote this code. As long as you retain this | |
| * notice, you can do whatever you want with this stuff. If we | |
| * meet someday, and you think this stuff is worth it, you can | |
| * buy me a Monster Energy® energy drink in return. | |
| * ------------------------------------------------------------ | |
| */ |
This brief tutorial will show you how to go about analyzing a raw binary firmware image in Ghidra.
I was recently interested in reversing some older Cisco IOS images. Those images come in the form of a single binary blob, without any sort of ELF, Mach-o, or PE header to describe the binary.
While I am using Cisco IOS Images in this example, the same process should apply to other Raw Binary Firmware Images.
