- Ilfak's presentation at Recon 2018
- Microcode in pictures
- Hex-Rays Microcode API vs. Obfuscating Compiler
- Scripts vds10, vds11, vds12 and vds13 from Hex-Rays SDK
Discover gists
I am assuming you are here because like me, you installed a bazillion different python interpreters on mac and the whole thing is a spagetti. Today, I finally fixed my python installation. Whatever I install for python2 or python3 using pip JUST.WORKS.. My god! finally.
Here is what I had messed up, which you also probably did:
- I had too many different python interpreters
- Too many different symlinks which I lost track of
- almost no package I installed with pip worked without a headache
- any attempt to fix using online resources made it worse.
When Riot Games introduces the Vanguard anti-cheat to League of Legends, you should STOP playing and you should not install the anti-cheat when you get the pop-up. Vanguard is a kernel-level anticheat and these anticheats operate at a privilege level HIGHER THAN YOUR OWN. The anti-cheat can do things that even you can't do, without asking or letting you know. It's like Riot installing a camera in every room of your house and getting a copy of every key inside.
Here is just one example of what they can do: https://www.theregister.com/2013/11/20/esea_gaming_bitcoin_fine/
#!/usr/bin/python | |
import os | |
import sys | |
import math | |
import struct | |
# mame-approm-it.py APPROM_PATH OUT_PATH FLASH_SIZE | |
# Approm mod @ APPROM_PATH and output to OUT_PATH with specificed flash size | |
# mame-approm-it.py cool.o neat/ 0x400000 |
In some cases, only these lines will work
for product in IntelliJIdea WebStorm DataGrip PhpStorm CLion PyCharm GoLand RubyMine; do
rm -rf ~/.config/$product*/eval 2> /dev/null
rm -rf ~/.config/JetBrains/$product*/eval 2> /dev/null
done
But if not, try these
[keys.normal] | |
C-f = [":new", ":insert-output lf-pick", ":theme default", "select_all", "split_selection_on_newline", "goto_file", "goto_last_modified_file", ":buffer-close!", ":theme tokyonight_storm"] |
// when you're trying to use `position:sticky` on an element | |
// you'll have trouble if any parent/ancestor element has | |
// overflow set to anything other than "visible" (such as: auto,hidden,overlay,scroll) | |
// & turns out if a parent is `display:flex` it might need some love | |
// (to remedy this you can set the `align-self` of your sticky element) | |
// see here for how the display & align-self properties affect: http://bit.ly/2ZaRu4o | |
// so, to find those troublesome parents... | |
// copy & paste this into Chrome Inspector/Dev Tools console | |
// (and be sure to change the #stickyElement below, if needed) |
vSphere 6 Enterprise Plus: | |
1C20K-4Z214-H84U1-T92EP-92838 | |
1A2JU-DEH12-48460-CT956-AC84D | |
MC28R-4L006-484D1-VV8NK-C7R58 | |
5C6TK-4C39J-48E00-PH0XH-828Q4 | |
4A4X0-69HE3-M8548-6L1QK-1Y240 | |
vSphere with Operations Management 6 Enterprise: | |
4Y2NU-4Z301-085C8-M18EP-2K8M8 | |
1Y48R-0EJEK-084R0-GK9XM-23R52 |