- https://www.vx-underground.org/archive.html
- https://www.vx-underground.org/windows.html
- https://doxygen.reactos.org/index.html
- https://modexp.wordpress.com/
- https://klezvirus.github.io/
- https://zerosum0x0.blogspot.com/
- https://www.binarly.io/posts/index.html
- https://0xdarkvortex.dev/blogs/
- https://cocomelonc.github.io/
| [ | |
| { | |
| "context": "Editor && (vim_mode == normal || vim_mode == visual) && !VimWaiting && !menu", | |
| "bindings": { | |
| // put key-bindings here if you want them to work in normal & visual mode | |
| // Git | |
| "space g h d": "editor::ToggleSelectedDiffHunks", | |
| "space g h r": "git::Restore", | |
| // Toggle inlay hints |
I want you to act as a Senior full stack Typescript developer. Once I provide the TypeScript code, your task is to develop a comprehensive suite of unit tests for a provided TypeScript codebase. Follow these guidelines for an effective testing process:
-
Understand the Codebase: Analyze the TypeScript code thoroughly, step by step. Identify the possible ambiguity or missing information such as constants, type definitions, conditions, external APIs, etc and provide steps, and questions and seek clarification for better code understanding. Only proceed to the next step once you have analyzed the codebase fully.
-
Testing framework: For this task, use an abstract testing framework instead of known frameworks such as chai, jest, etc., remembering that the principles of unit testing apply regardless of the specific tools.
-
Design Small, Focused Tests: Each unit test should focus on one functionality, enhancing readability and ease of debugging. Ensure each test is isolated and does not depe
Windows 2012 R2 Essentials: http://download.microsoft.com/download/8/F/7/8F7024D2-AB2A-4BE2-8406-1E3AC49C5C1F/9600.16384.WINBLUE_RTM.130821-1623_X64FRE_SERVER_SOLUTION_EN-US-IRM_SSSO_X64FRE_EN-US_DV5.ISO
Windows 2016: https://software-download.microsoft.com/download/pr/Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO
Windows 2019 Essentials: https://software-download.microsoft.com/download/pr/17763.737.190906-2324.rs5_release_svc_refresh_SERVERESSENTIALS_OEM_x64FRE_en-us_1.iso
- Assembly programming guide: Intro level guide on x86 assembly.
- computer systems a programmer's perspective: Chapter 3 covers x86 assembly programming.
- x86-64Machine-Level Programming: A detailed guide on x86_64 assembly programming by prof. Bryant and Hallaron.
- x86-64 Assembly Language Programming with Ubuntu: Book on x86_64 assembly programming.
- [This document gives a brief summary of the x86-64 architecture and instruction set](https://web.archive.org/web/20200502094406/https://www.lri.fr/~filliatr/ens/compil/x86-6
| { | |
| "Back" : "Escape; Back; Ctrl+[; Meta+O", | |
| "Forward" : "Forward; Ctrl+[; Meta+I", | |
| "Change Type..." : "Shift+Y; ", | |
| "Close Window" : "Ctrl+W; X", | |
| "Command Palette" : "Ctrl+P; Space", | |
| "Copy" : "Ctrl+C; Y", | |
| "Disassembly Graph" : "G, L", | |
| "Display as\\Binary" : "D", | |
| "Display as\\Default" : "D", |
| <# | |
| .SYNOPSIS | |
| This script can bypass User Access Control (UAC) via fodhelper.exe | |
| It creates a new registry structure in: "HKCU:\Software\Classes\ms-settings\" to perform UAC bypass and starts | |
| an elevated command prompt. | |
| .NOTES | |
| Function : FodhelperUACBypass | |
| File Name : FodhelperUACBypass.ps1 |
- Use
curlto get the JSON response for the latest release - Use
grepto find the line containing file URL - Use
cutandtrto extract the URL - Use
wgetto download it
curl -s https://api.github.com/repos/jgm/pandoc/releases/latest \
| grep "browser_download_url.*deb" \
| cut -d : -f 2,3 \
| tr -d \" \Magic numbers are the first bits of a file which uniquely identify the type of file. This makes programming easier because complicated file structures need not be searched in order to identify the file type.
For example, a jpeg file starts with ffd8 ffe0 0010 4a46 4946 0001 0101 0047 ......JFIF.....G ffd8 shows that it's a JPEG file, and ffe0 identify a JFIF type structure. There is an ascii encoding of "JFIF" which comes after a length code, but that is not necessary in order to identify the file. The first 4 bytes do that uniquely.
This gives an ongoing list of file-type magic numbers.
