| // Material Palenight Color Scheme for Blink Shell | |
| // by Greg Gamel (https://github.com/ggamel) (https://greg.is) | |
| black = '#292d3e'; | |
| red = '#f07178'; // red | |
| green = '#c3e88d'; // green | |
| yellow = '#ffcb6b'; // yellow | |
| blue = '#82aaff'; // blue | |
| magenta = '#c792ea'; // pink | |
| cyan = '#89ddff'; // cyan |
| /* | |
| * NOTE 1: This works on VC++ but might need a little extra syntax to work on GCC. | |
| * NOTE 2: It breaks when calling set_interval on the minimum key (std::numeric_limits<K>::lowest()) and maybe on the maximum key too. | |
| * | |
| * OPERATIONS: | |
| * | |
| * N = number of unique intervals. (Neighboring intervals with the same value are joined.) | |
| * Iterators run in key-sorted order. (Or reverse, if you like - they're bidirectional.) | |
| * | |
| * get_min(): O(1) |
You might want to read this to get an introduction to armel vs armhf.
If the below is too much, you can try Ubuntu-ARMv7-Qemu but note it contains non-free blobs.
First, cross-compile user programs with GCC-ARM toolchain. Then install qemu-arm-static so that you can run ARM executables directly on linux
If there's no qemu-arm-static in the package list, install qemu-user-static instead
| #!/usr/bin/python3 | |
| import re | |
| import subprocess | |
| import tkinter as tk | |
| from Xlib import display | |
| def lambda_factory(index): | |
| global labels | |
| global buttons |
08/16/17 by Sergey Grebenshchikov
This is a quick tutorial on how to test code using the GoMock mocking library and the standard library testing package testing.
GoMock is a mock framework for Go. It enjoys a somewhat official status as part of the github.com/golang organization, integrates well with the built-in testing package, and provides a flexible expectation API.
In this write-up I will discuss how I managed to solve the challenge "babystack" from 0ctf with a technique called return to dl-resolve. I did not know this kind of return-to attack before the contest. In the following sections a detailed explanation of the entire exploit will be presented.
I downloaded the provided binary babystack and quickly fired up binaryninja alongside with gdb to analyze it. I quickly realized a buffer overflow vulnerability is present within sub_804843b.
My first approach was to solve this challenge using a return-to-libc attack by leaking the base address of the library and call system in order to get a shell.
This technique is contingent on:
- Leaking libc base address
- Knowing the version of libc to get the offset of
system.
However, the version of libc on the remote server was unknown and the ELF did not provide any function that can be us
| @echo off | |
| @reg copy HKLM\HARDWARE\ACPI\DSDT\VBOX__ HKLM\HARDWARE\ACPI\DSDT\NOBOX__ /s /f | |
| @reg delete HKLM\HARDWARE\ACPI\DSDT\VBOX__ /f | |
| @reg add HKLM\HARDWARE\DESCRIPTION\System /v SystemBiosVersion /t REG_MULTI_SZ /d "NOBOX - 1" /f | |
| @reg add HKLM\HARDWARE\DESCRIPTION\System /v VideoBiosVersion /t REG_MULTI_SZ /d "NOBOX - 1" /f | |
| @taskkill /f /im VBoxTray.exe | |
| @exit |