quarta-feira, fevereiro 19, 2020

apt error The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5XXX

This can be mostly often solved by running the following:


apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys MISSING_KEY

Error usually is like follow:

GPG error: http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 531EE72F4C9D234C
E: The repository 'http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu focal InRelease' is not signed.
E: Failed to download some files
W: Failed to fetch http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/dists/focal/InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 531EE72F4C9D234C
E: Some index files failed to download. They have been ignored, or old ones used instead.


quinta-feira, janeiro 23, 2020

linux ping and traceroute examples #Speedup

https://www.cyberciti.biz/faq/unix-linux-bsd-appleosx-speedup-ping-traceroute-command-probs/

traceroute -i eth0 199.7.83.42
traceroute -i eth2 199.7.83.42

-s means your public ip address

traceroute -w 3 -q 1 -s 200.204.0.10 199.7.83.42
traceroute -w 3 -q 1 -s 200.204.0.138 199.7.83.42


ping -S 200.204.0.138 192.5.5.241

ping -c 5 -n -i 0.2 -W1 192.5.5.241

ping  -c 5 -n -i 0.2 -W1 192.168.0.1

quinta-feira, novembro 28, 2019

PXE Boot Live Kali Linux | Kali Linux Live Network Booting | Booting Kali Linux Live over HTTP


Need to read first

In short therms you only need to grab live files from ISO and configure menu as follow

label Kali^Live
        menu label Kali^Live
        kernel vmlinuz
        append vga=788 initrd=initrd.img append boot=live components fetch=http://192.168.1.1/filesystem.squashfs

-------

Download Kali PXE Netboot Images


Now, we need to create a directory to hold the Kali Netboot image and download the image we wish to serve from the Kali repos.

mkdir -p /tftpboot 
cd /tftpboot 
 # for 64 bit systems:  
wget http://repo.kali.org/kali/dists/kali/main/installer-amd64/current/images/netboot/netboot.tar.gz 
 # for 32 bit systems:  
wget http://repo.kali.org/kali/dists/kali/main/installer-i386/current/images/netboot/netboot.tar.gz 
tar zxpf netboot.tar.gz 
 rm netboot.tar.gz



Configure Target to Boot From Network


With everything configured, you can now boot your target system and configure it to boot from the network. It should get an IP address from your PXE server and begin booting Kali.



Booting Over HTTP ?

In this example, we will obtain the kernel, initrd, and squashfs filesystem we need from a full Kali Linux release ISO from within the “live” directory. We copy the initrd and kernel into the TFTP root folder, while the squashfs file goes into the web root:

mkdir /mnt/iso 
 mount -o loop kali-linux-1.1.0a-amd64.iso /mnt/iso/  
cp /mnt/iso/live/{initrd.img,vmlinuz} /tftpboot/ 
cp /mnt/iso/live/filesystem.squashfs /var/www/ 
 apachectl start



In this example, we’ll obtain the kernel, initrd, and squashfs filesystem from a full Kali Linux release ISO (in the “live” directory) and then proceed to boot the kernel and initrd over PXE. Once the boot screen appears, we need to alter a few boot parameters as shown in the screenshot below:


Or menu, can look like this

label Kali^Live
        menu label Kali^Live
        kernel vmlinuz
        append vga=788 initrd=initrd.img append boot=live components fetch=http://192.168.1.1/filesystem.squashfs


As the squashfs filesystem loads to RAM, the filesystem itself can’t be larger than the amount of RAM available on the computer – meaning that for booting a standard Kali ISO as shown above, we’d need at least 4 GB of RAM. Of course, this can be remedied by making smaller, custom Kali ISO images, perhaps with different toolsets and uses.