Life Hack, How I got access to the back office

Today I was visiting an office and waiting for an "appointment" wink wink. Doing what I normally do, I watched the security guards checking badges and listening to them complain. The key to this hack is to listen to guards and pay attention to what they are saying, in this conversation they where talking about not having enough time to get lunch and all they had on site was a vending machine. One of the guards was asking the other what they would like for lunch, the other said "Man, at this point I would eat anything". 

Hearing this and wanting to get to the back office for my "Meeting" of course, (wink wink). I went to Taco Bell and bought two bean and cheese burrito's and two super taco's. Knowing that the bean and cheese burritos could be weaponized, I wanted to make sure the effect was complete with the super taco. 

I returned to the office and said "Hey guys, I was in the waiting room and over heard your conversation, I wanted to be a NICE GUY (<- this is important) and get you two some lunch. They both where very happy and ate all the food.

This is where the hack comes in, knowing that Taco Bell takes about 30 minutes to take affect, I set my iPhone stop watch. Sure enough, at 31 minutes both guards went running for the bathroom. I was able to walk into the back office and OWN all the things.

-----  BadSector

Windows 10 Wireshark no interfaces version1803

So, you are getting ready for DEFCON 26 and you are heading to Packet Hacking Village, you got your laptop all ready to go, reloaded Windows 10 and made sure you have no saved passwords and personal data. You start installing the apps you will need and boom, you start Wireshark and it finds no interfaces. No fear, BADSECTOR is here.

1. start CMD with Run as administrator 
2. in the command line type sc start npf
3. start Wireshark
4. winning

Dual boot Windows 10 and Kali

How to fix the time issues with dual booting Windows 10 and Kali

If you are experiencing this issue. run the command at the terminal in Kali

timedatectl set-local-rtc 1

Done....  enjoy

Dual Boot between PCIe M.2 and SATA in HP 840 G2.

Holly PCIe/M.2 battman, I took me 5 try's to get Kali linux on the M.2 and Windows 10 on the 500GB SATA to dual boot from options in BIOS. F9 at start up, choose the drive, boot. So , yes I can be done and yes GRUB likes to mess up boot loaders. I got ti get my GRUB on. < see what I did there.

This is what should have worked.

1. install Windows 10 on the SATA and make sure all is good.
2. remove Windows 10 SATA and install PCIe M.2 and install Kali and make sure all is good.
3. Put Windows 10 back in and check fur dual boot.

End result, Windows works but Kali does not boot.

Boot with Kali Live USB and fix GRUB

The below are the steps I followed to get it back working.

mount /dev/sda* /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mkdir /mnt/sys/firmware/efi/efivars
mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
mkdir /mnt/boot/efi
mount /dev/sda+ /mnt/boot/efi
mount -o remount,rw /dev/sda+ /mnt/boot/efi
mkdir /mnt/hostrun
mount --bind /run /mnt/hostrun
chroot /mnt
mkdir /run/lvm
mount --bind /hostrun/lvm /run/lvm
grub-install /dev/sda
update-grub
exit
umount /mnt/dev
umount /mnt/proc
umount /mnt/sys/firmware/efi/efivars
umount /mnt/sys
umount /mnt/boot/efi
umount /mnt/hostrun
umount /mnt/run/lvm
umount /mnt
REBOOT

Now Kali works but Windows 10 no longer boots.

Removed PCIe M.2 and fix Windows10 boot loader

Boot with Windows 10 USB installer
Choose repair my computer
Select command prompt
type -> Bootsect /nt60 driveletter: /mbr

Put PCIe M.2 back in

Check dual boot with F9

WORKING

Wall Of Sheep DEFCON 26

My Commodore 64 chip testing board

I got a dead C64 off eBay cheap, I mean really cheap. the seller said it was dead and the repair technician said it was not worth fixing. I took a chance and bought it thinking I could salvage some chips. When I got it and looked at it in the magnifying glass I saw something that was interesting, the fuse clips where bent out and not making contact. I thought, nah, that can't be it.. Yep, that was it, the board fired up although needing more repair. after some chips checking the PLA was bad, I replaced it and bam. Working c64. The seller packaged this c64 terribly and the case was broken the keyboard is missing keys ( I did know that though before buying)

So now I have this working C64 board with no case and no keyboard, so I decided to make it a chip testing board. I socketed all the chips to repair other C64's, I can test the chips and look for the band ones.

Here is the pic. if you want one, let me know. I can make them, but they are not cheap, I takes me hours to desolder all of the chips and replace them with sockets.

$200 if you send me your board
$300 with no chips. One in stock
$400 with all chips and working. One in stock

Eye Candy for CentOS 7 -- conky

It's different for CentOS

Easy install in 2 steps

yum install epel-release.noarch -y

yum install conky -y

edit /etc/conky/conky.conf